Power Automate
Workflow automationRoadmap
A custom connector for Microsoft Power Automate flows.
In plain English
LoopQuest is a place where a person quickly checks the work an AI or automation has done. Connecting Power Automate means that whenever Power Automate produces something that should be looked at by a human, it sends that item to LoopQuest. Someone on your team reviews it in a few seconds, and their decision is sent straight back to Power Automate so the rest of your process can carry on, with a real person accountable for the call.
A one-click Power Automate connector is on our roadmap. In the meantime the steps below show how to wire it up today using our open API, and it works exactly the same.
When you'd use it
Add human sign-off to a Power Automate flow over Microsoft 365 data.
What you'll need
- A free LoopQuest account. Sign up if you don't have one.
- A project and its API key — find it under Workspaces → your project → API keys. The key is how Power Automate proves it's allowed to send you work.
- An account on Power Automate itself, with the workflow or agent you want to add a human check to.
How to set it up
- 1Import the OpenAPI spec as a custom connector and add an HTTP webhook for verdicts.
Recipes: gate or monitor
Two ways to put a human in the loop with Power Automate. A gate blocks until someone approves; a monitor reviews in the background without slowing anything down.
Gate — block until approved
Power Automate can pause a run and resume it when the verdict arrives, which makes it a clean blocking gate.
- 1In your Power Automate flow, send the output to LoopQuest with the mode set to "gate", plus a callback so it can be resumed.
- 2Power Automate pauses at that step (a Wait node or resume URL) instead of carrying on.
- 3A reviewer approves or flags it; LoopQuest calls back and the run picks up exactly where it left off.
- 4Branch on the verdict, and set a timeout so a missing decision never blocks the flow forever.
Monitor — review without blocking
Monitor mode never holds Power Automate up. The flow proceeds immediately and LoopQuest reviews a copy for quality.
- 1Send the output with a mode of "monitor" and don't wait on the result.
- 2Power Automate carries straight on, nothing is blocked.
- 3Verdicts are logged and scored over time. Sample a fraction for QA, or review every item.
What happens after a review
The moment a reviewer decides, LoopQuest sends the result back to the web address you gave it (your callback_url). The message says what was decided, whether it was approved, flagged, which option was picked, or the corrected values, so your automation can act on it automatically.
For developers: each callback is signed with an X-LoopQuest-Signature HMAC header. Verify it before trusting the payload. Full details are in the API reference.
Pairs well with
The review games that best fit the kind of output Power Automate tends to produce.