Integration · Automation
AI agents for Power Automate
See and manage Microsoft Power Automate flows stored in a Dataverse environment.
- Actions
- 7
- Read
- 4
- Write
- 3
Actions
What your agents can do in Power Automate
See and manage Microsoft Power Automate flows stored in a Dataverse environment: list cloud and desktop flows, turn flows on or off, read cloud flow run history, and start, follow or cancel desktop flow runs, as the person who signs in. Covers flows inside solutions (Microsoft's API does not reach My flows).
Read 4
Look things up. Nothing changes.
List flows
Lists the environment's cloud flows (automated, instant and scheduled) or desktop flows, optionally only those on or off, or whose name contains some text.
Get a flow
Reads one flow by its workflowid: name, description, state (0 off, 1 on, 2 suspended), category, owner, when it was created and changed, and whether it came from a managed solution.
List cloud flow runs
Lists cloud flow runs from the environment's run history (kept 28 days by default; solution flows only), optionally for one flow, with one status (Success, Failed, Cancelled) or started after a time.
Get a desktop flow run
Reads a desktop flow run (a flow session) by the ID run_desktop_flow returned.
Write 3
Create, change or send.
Turn a flow on or off, or rename it
Turns a flow on or off, and can change its name or description.
Run a desktop flow
Starts a desktop flow on a machine or machine group, attended or unattended, through a desktop flow connection, with optional inputs.
Cancel a desktop flow runDeletes data
Cancels a queued or running desktop flow run by its flow session ID.
A person can approve first
Any write action can be set to wait for a person's approval before it runs, so an agent asks before it changes anything. Actions that delete data ask first by default.
Connection
How it connects
Connect it once in the console, then give it to the agents and workflows that need it.
Sign in with Microsoft and approve access (OAuth).
Settings
- Environment URL
Kept safe
- Credentials are stored encrypted with your organization's own keys.
- They are opened only by the process that makes the call, at the moment it runs, and never go into a prompt or the browser.
- Calls go only to the tool's own servers.
Ideas
Ideas to start with
Starting points made only from the actions above. Mix them with any other tool your agents can use.
- 01
Ask about your Power Automate data
Ask a question in plain words. The agent can list flows, get a flow or list cloud flow runs in Power Automate, then answers with what it found.
- 02
Let an agent update Power Automate
Have the agent turn a flow on or off, or rename it or run a desktop flow in Power Automate as part of a larger task. Turn on approval and a person signs off on each change first.
- 03
Share what it finds in Slack
Give one agent Power Automate and Slack: it can list flows in Power Automate and post a summary to a Slack channel in the same run.
FAQ
Power Automate and MyDeepAgents
Can MyDeepAgents connect to Power Automate?
Yes. The Power Automate connector has 7 actions: 4 read and 3 make changes. Your agents can call them as tools, and your workflows can run them as steps.
How do I connect Power Automate?
Sign in with Microsoft and approve access (OAuth). The connection also asks for: Environment URL. Credentials are stored encrypted with your organization's own keys and are opened only at the moment of a call.
Can an agent change data in Power Automate without asking?
Only if you let it. Each of the 3 actions that change data can be set to wait for a person's approval before it runs, and the one that deletes data asks first by default.
Can I use Power Automate in workflows as well as agents?
Yes. Every Power Automate action also works as a step in a workflow, and the same connection serves your agents and your workflows.
Early access
Put Power Automate to work
Connect it in a few minutes, give an agent the actions it needs, and decide which changes wait for a person.