Power Automate

Connect a Microsoft Power Platform environment by saving your Azure AD App Registration credentials (tenant_id, client_id, client_secret) and your Dataverse environment_url/environment_id, after checking they actually work together. You'll need: an Azure AD App Registration (Azure Portal > Microsoft Entra ID > App registrations), a client secret created under Certificates & secrets, and that app registered as an Application User in your Power Platform environment with a security role granting workflow privileges. Note: this only manages Solution-aware cloud flows -- personal unattached "My Flows" are not supported by Microsoft's own Web API and are out of scope here.

List the Power Platform environments currently connected.

Disconnect one Power Platform environment: deletes its saved Azure AD credentials. Existing flows and their runs in that environment are not affected -- only Webbee's access to them is removed.

List cloud flows (Solution-aware) in a connected Power Platform environment, via the Dataverse Web API. Personal unattached "My Flows" are not returned -- Microsoft's Web API does not expose them.

Read one cloud flow in full from the Dataverse Web API.

Create a new Solution-aware cloud flow in the Dataverse `workflow` table. clientdata must be valid Power Automate flow definition JSON (the format Power Automate itself exports/imports) -- this connector does not validate its internal shape, only that it is well-formed JSON. New flows are created in Draft state; call set_flow_state to activate.

Update selected fields of an existing cloud flow (name, description, and/or its clientdata definition) without touching omitted fields.

Permanently delete a cloud flow from Dataverse. Cannot be undone.

Turn a cloud flow on (activated) or off (suspended/draft) by setting its Dataverse statecode/statuscode.

List recent runs of a cloud flow, via the Power Platform REST API (a separate, newer surface from the Dataverse Web API used for the flow definition itself).

Get details of one flow run by id, via the Power Platform REST API.

Cancel a currently running flow run.

Resubmit (re-run) a flow run with the same trigger inputs it originally received.

Turn multiple cloud flows on/off in one call -- a value-add convenience this connector adds on top of Microsoft's API, which has no native bulk-state endpoint. Applies set_flow_state to each workflow_id in turn and reports success/failure per item.

Permanently delete multiple cloud flows in one call -- a value-add convenience this connector adds on top of Microsoft's API, which has no native bulk-delete endpoint. Deletes each workflow_id in turn and reports success/failure per item. This cannot be undone.