Loading…
Decionis · Power Automate reviewer guide
Sample Power Automate gate payloads
These three JSON files are ready-to-use request bodies for the Decionis “Evaluate a governed decision before execution” action (POST /v1/power-automate/policy-check). They mirror the three finance actions Microsoft reviewers asked about.
Decionis does not build or replace your workflow. You keep initiating refunds, vendor payments, and discount exceptions from the Power Automate flows you already run. Decionis is the gate those actions pass through, and the surface where the gated action and its signed Decision Dossier appear.
The payloads
Refund approval
A customer refund above the sample policy threshold — typically returns escalate.
Vendor payment release
A vendor payment with an unmatched vendor record — typically returns escalate or block.
Discount exception
A small in-policy discount — typically returns allow with continue_flow: true.
What you need
- Your Decionis Org ID — replace
<YOUR_DECIONIS_ORG_ID>in each file. Installing Decionis in Microsoft Teams provisions the workspace automatically from your Microsoft Entra ID sign-in; the Org ID is shown (with a copy button) when you enable Power Automate in the Decionis tab → Settings. - A Decionis API key with the
decision:writescope — provisioned and shown once when you toggle Enable Power Automate in the Decionis tab → Settings (or rotate it in the workspace console).
Path A — verify the gate in 60 seconds (no flow build)
curl -sS -X POST https://api.decionis.com/v1/power-automate/policy-check \
-H "Authorization: Bearer $DECIONIS_API_KEY" \
-H "Content-Type: application/json" \
-d @refund-approval.json | jq '{verdict, continue_flow, risk, reason, dossier_id, verification_url}'You get back a verdict (allow / block / escalate / delay), the boolean continue_flow your flow branches on, a dossier_id, and a public verification_url. The verdict reflects your org’s policy, not the payload — a small in-policy discount typically returns allow; a large refund or an unmatched vendor payment typically returns escalate or block.
Path B — import the connector and run a real flow
- In Power Automate: Data → Custom connectors → New custom connector → Import an OpenAPI from URL, and paste: https://decionis.com/marketplace/microsoft/power-automate/decionis-power-automate-openapi.json
- Create a connection using your Decionis API key.
- Build a flow with three steps: a trigger (Manually trigger a flow, or your existing refund/payment trigger), the Decionis → Evaluate a governed decision before execution action with the contents of one sample file pasted into the inputs, and a condition on
continue_flowequal totrue— on No, stop or route to approval; on Yes, continue your existing automation. - Run the flow.
Then: see it surface in Microsoft Teams
Open the Decionis app in Teams → Dossiers tab. The action you just gated appears with its verdict, risk, and a link to the signed Decision Dossier. Actions your policy escalates also post an interactive Approve/Reject card into the connected team channel. That is the full loop: your Power Automate flow initiated the action, Decionis gated it, and the result is surfaced in Teams.