Skip to content

Migrating from Power Automate approvals to DueReason

Power Automate's Start and wait for an approval action waits for a yes or no, then trusts it. See what changes moving the same check to DueReason.

Updated · 10 min read

In short

  • Start and wait for an approval is the single most common way an organization already gates a flow before it keeps running - it ships inside Microsoft 365, with Premium at $15/user/month and a per-automation Process plan at $150/bot/month.
  • It has five approval types and posts to email, the approvals center, the Power Automate app, or the Teams Approvals app, but none of them hand the next step a signed, verifiable record of the decision - the flow just continues.
  • DueReason's console request form is the direct, no-code replacement for a non-engineer who only ever opened the approval card in their inbox or in Teams; the SDK's requestApproval() and waitForApproval() are the direct replacement for the action inside a flow.
  • What changes is what happens after someone clicks Approve: a signed, single-use grant bound to the exact payload, verified before anything acts on it, recorded on a hash-chained ledger.

If your organization's approval step lives inside a Power Automate flow, it almost certainly uses the Start and wait for an approval action - built into any cloud flow, free with the Microsoft 365 licence most teams already pay for, which is exactly why it is the approval step a prospect is most likely to already have before they ever look at a dedicated approvals product. This walks through what that action does today, and what moving the same check to @duereason/sdk changes.

What "Start and wait for an approval" does today

Add the action to any cloud flow and it pauses the run until the people you assign respond, using one of five approval types:

Approval typeBehavior
Approve/Reject - Everyone must approveEvery assigned approver must respond; the flow continues once all have approved, or as soon as one rejects.
Approve/Reject - First to respondAny one assigned approver's answer completes the request.
Custom Responses - Wait for all responsesYou define the response options; every approver must answer.
Custom Responses - Wait for one responseYou define the response options; any one answer completes it.
Sequential approvalApprovers are asked one at a time, in order; each must respond before the next is asked.

Approvers answer from their email inbox, the approvals center at make.powerautomate.com, the Power Automate mobile app, or the Approvals app in Microsoft Teams. Using approvals at all requires a Microsoft Dataverse database in your environment - it is listed as a prerequisite before you can add the action for the first time - and that is also where the request's own record lives, inside your tenant.

What happens after someone clicks Approve

Microsoft's own documentation describes the action pausing, then resuming the flow with the approvers' responses available as tokens for whatever runs next - an email, a status update, a row written to SharePoint or Dataverse. It does not describe a signed or otherwise independently verifiable object the next step checks before it acts: whoever built the flow is trusted to have wired the right action after the approval step, and the approval and the action that follows it share the same trust boundary. That is the same shape HumanLayer's now-deprecated require_approval decorator had, and the HumanLayer migration guide walks through the same gap in more detail if that is the comparison you came in with.

The same flow in DueReason, starting from the console

Power Automate users are frequently not developers, so start where they would actually look: Settings → Templates installs one of DueReason's ready-made action and approver-group sets, and Approvals → New request is the console's own request form - pick the action, write a reason, and the people in its approver group see it waiting for them, in the console or over whatever notification channel the organization turned on. Nothing here needs an API key or a flow to build; the getting-started guide covers the whole console path from a new account to a decided request.

Keeping the engineering path: requestApproval and waitForApproval

Inside a script, job, or an existing automation, @duereason/sdk's requestApproval() and waitForApproval() are the closest line-for-line match to one blocking action:

```js import { createClient } from "@duereason/sdk";

const duereason = createClient({ apiKey: proces..._KEY });

// Equivalent of adding the action to a flow: create the request. const request = await duereason.requestApproval({ action: "payment", title: "Pay invoice INV-2026-118", reason: "Supplier invoice due 10 October, matches PO-77.", payload: { amount: 1200, currency: "EUR", payee: "ACME sp. z o.o." }, });

// Equivalent of the flow waiting on the card: block until it is decided. const decided = await duereason.waitForApproval(request.id, { timeoutMs: 60 * 60 * 1000 });

if (decided.status === "approved") { // decided.grant is verified against this exact payload before you act on it. } ```

requestApproval() is the equivalent of adding the action and filling in its card; waitForApproval() is the equivalent of the flow pausing on it, with a timeoutMs in place of choosing when the request expires. If you would rather wrap a whole function once and reuse it everywhere, `withApproval()` does the same two calls around a function body instead of a flow step.

What changes, not just what moves

  • A grant, not just a flow resuming. Once approved, DueReason issues a signed, single-use token bound to a hash of the exact payload. Whatever reads decided.grant (your code, or a no-code tool following the webhook recipe) verifies it before acting, and a changed amount or target is refused rather than trusted the way a flow's next step would be.
  • A hash-chained ledger, not a connector's own activity log. Every step of a request - created, each answer, the execution report - is recorded as a ledger event from the start, not an audit trail bolted onto a general-purpose flow log.
  • One record that travels with the decision. A decided request's signed receipt can be checked at /verify or with the SDK by anyone, without a DueReason account or access to your Dataverse database - useful once an auditor, a counterparty or a new teammate needs to confirm what was approved and why, without being given access to the tenant that ran the flow.
  • EU hosting, if you need it. DueReason's hosted product is EU-hosted, and self-hosting is a one-image Docker Compose deployment if you would rather keep the data in your own infrastructure entirely - neither replaces a Microsoft 365 tenant, but it is a different answer to where a decision's record lives.

Moving one approval step over

  1. Pick the action your Power Automate flow already gates - payment, deployment, access, content - and recreate it as a DueReason action, either from a template in Settings or matching one your flow already models in a SharePoint list or Dataverse table.
  2. Recreate who can approve it as an approver group, in place of the people or Teams channel the action was assigned to.
  3. Replace the Start and wait for an approval step with requestApproval() immediately followed by waitForApproval() (or withApproval() around the whole function if you are wrapping one), passing the same information you put in the approval card as title, reason and payload.
  4. Replace whatever the flow did with the approvers' outcome (an If branch on Approve/Reject) with a check of decided.status, and read decided.grant before the step that used to run unconditionally after approval.
  5. If the rest of the flow stays in Power Automate, Zapier, Make or n8n and only the approval step moves, the webhook recipe covers triggering off approval.approved and reporting back once your flow has acted, so the rest of a no-code automation does not have to be rebuilt.

What has no direct equivalent

DueReason has no SharePoint- or Dataverse-table integration of its own, and no visual flow canvas - it answers one question (is this specific action approved, by whom, with what evidence) rather than orchestrating a multi-step process end to end. If your flow's real job is moving data between SharePoint, Dataverse and a dozen connectors and the approval is one step among many, keep Power Automate for the orchestration and call DueReason for the decision itself, the way the worked examples in the webhook recipe call out to Okta, DocuSign or Xero only after a request is approved. The Pipefy migration guide covers the same trade-off for a Kanban-style process builder, if that is the comparison you are also making.

Questions

Does Power Automate's approval action really have no verification step?
Microsoft's own documentation describes the action pausing a flow until approvers respond and then resuming it with their answers as tokens for the next action - it does not describe a signed or independently verifiable decision object the next step checks before it runs. Whoever built the flow is trusted to have wired the right thing after the approval step.
Can I keep my existing Power Automate flow and only replace the approval step?
Yes. Call requestApproval() from an HTTP action (or a short Azure Function) in place of Start and wait for an approval, and either poll the request or use the no-code webhook recipe to resume your flow once approval.approved fires, so everything upstream and downstream in Power Automate stays as it is.
Where does my approval data live today, and where does it live with DueReason?
Power Automate's built-in approvals require a Microsoft Dataverse database in your environment as a prerequisite, and the request lives there (or in a SharePoint list, for a custom approval loop built on one), inside your tenant. DueReason keeps the request, its payload and its signed receipt with your organization in the hosted product's EU region, or entirely on your own infrastructure if you self-host.
What does this cost during the beta?
DueReason is free today for one organization with up to five members, with all core features available; a yearly license key lifts those limits, verified entirely offline with no phone-home and applied in Settings > License. Power Automate's own published pricing is $15/user/month (Premium, paid yearly) or $150/bot/month (Process, for a shared automation used by many people) as of this guide's last review.
Do I have to rebuild my whole flow to move the approval step?
No. DueReason answers one question - is this action approved, and with what evidence - rather than orchestrating a process end to end, so a flow that does other things in SharePoint, Dataverse or a dozen connectors can keep doing them; only the Start and wait for an approval step and whatever reads its outcome need to change.

Move your approval step to DueReason

Create an account and install a template, or point requestApproval() and waitForApproval() at the action you already gate in Power Automate.

Create your account

Sources

This guide explains the regulation as we read it; it is not legal advice. Check the official text and your national law, which may add obligations.

Start with DueReason

Create a free account, try it live, or talk to us about your workflow.

Get product updates