Skip to content

Use Onplana in Power Automate

All plansAny member (the trigger needs an Owner or Admin)

The Onplana connector lets a flow in Power Automate, an app in Power Apps or an agent in Copilot Studio work on your Onplana workspace: create and change tasks, projects and issues, log and approve time, and start a flow when work changes in Onplana.

One trigger:

  • When an event happens in Onplana: starts the flow when a task is created, updated or changes status, a project is created or updated, or a comment is added. Pick the events when you add the trigger. The flow receives the event name, the time and the ids of what changed; add a Get a task or Get a project step to read the rest.

19 actions:

Area Actions
Tasks List my tasks, List the tasks in a project, Get a task, Create a task, Update a task, List the comments on a task, Add a comment to a task
Projects Get a project, Update a project, Create a project from a template
Issues List issues, Get an issue, Create an issue, Update an issue, Resolve an issue
Timesheets List timesheet entries, Log time on a task, Submit my timesheet week, Approve a submitted timesheet week

The definition file holds 23 operations: these 19 actions, the trigger, and three that work behind the scenes (the project and template lists that fill the pickers, and the step that removes the trigger’s subscription when you delete a flow).

What Plan Who
Task, project and issue actions Every plan Anyone whose role allows the change
Create a project from a template Professional and above Anyone who can create projects
Timesheet actions Professional and above (time tracking) Your own time; approvers approve
The trigger Business and above (webhooks) An Owner or Admin

On a plan without webhooks, Onplana refuses the trigger’s subscription with HTTP 402 and the flow cannot be saved. Nothing else in the workspace changes.

The connector signs in with a personal access token, the same kind of token the API uses.

  1. In Onplana, open Settings, then Developer, then API tokens.

  2. Choose New token and name it for the flows that will use it.

  3. Tick the scopes your flows need: Read tasks and Write tasks, Read projects and Write projects, Read timesheets and Write timesheets, and Manage webhooks for the trigger.

  4. Copy the token. It starts with pat_ and is shown once. If it is lost, revoke it and create another.

A token without a scope still connects; only the operations that need that scope are refused (HTTP 403). The token acts as you: a flow can see and change only what you can.

While certification is pending, add Onplana as a custom connector. This needs an environment where you may create custom connectors; your Power Platform administrator can tell you which one.

  1. Download the connector definition: onplana-connector.swagger.json.

  2. Sign in to make.powerautomate.com, pick the environment, and open Custom connectors (under More, then Discover all, if it is not in the left menu).

  3. Choose New custom connector, then Import an OpenAPI file. Name it Onplana, select the file you downloaded, and choose Continue.

  4. The wizard fills in the host (api.onplana.com), the security (an API key sent in the Authorization header) and every operation from the file. Change nothing, and choose Create connector.

The same custom connector is then available in Power Apps and Copilot Studio in that environment.

  1. In a new flow, search for Onplana and pick an action or the trigger.

  2. When asked for a connection, enter Bearer , a space, and then your token, for example Bearer pat_....

  3. For a first test, build an instant flow with Create a task, pick a project, run it, and check the task in Onplana.

Two flows to start from:

  • Post to Teams when a task is done. Trigger When an event happens in Onplana with the event task.status_changed, then Get a task, a condition on its status, and a Teams post.
  • Submit the week’s timesheet on Friday. A scheduled flow on Friday afternoon that runs Submit my timesheet week for the current week.
  • Event payloads carry ids (and a task’s title when it is created), not the whole record.
  • Creating a risk is not offered: risk changes are not open to tokens.
  • There is no event yet for a submitted timesheet or an approval request, so those cannot start a flow.
  • The connector talks to Onplana’s hosted service at api.onplana.com. An Enterprise+ dedicated deployment needs a custom connector pointed at its own host.

Why does saving a flow with the trigger fail with 402? The trigger uses Onplana webhooks, which are on the Business plan and above.

Why does an action fail with 403? The token lacks the scope for that operation, or your role in the workspace does not allow the change.

Will I have to rebuild my flows when the certified connector appears? No rebuild of the logic is needed: the file you import here is the definition submitted for certification, so the operations are the same. Add a connection to it, point each step at it, and delete the custom connector when nothing uses it.

Is this the same as the webhooks page? The trigger creates an ordinary Onplana webhook named “Power Automate flow”, which you can see in Apps and integrations, Webhooks. Deleting the flow removes it. See Send webhooks for the events and delivery history.