Published on ZapierAug 4, 2026
Google Sheets
Create Decionis decision dossiers for new Google Sheets rows
Turn spreadsheet rows into governed actions—not blind automation.
For Approvals, finance operations, and spreadsheet-driven imports.
Loading…
Execution pattern
Treasury payment release
Stop the payment that clears sanctions on paper but not in fact.
- Category
- MoneyCommon in Fintech & payments · Manufacturing · Public sector
- Works through
- langchain · sap · sdk · shopify +2 more
- Proof
- Signed Decision DossierVerifiable against our published JWKS.
- Deploy
- Shadow Mode firstMeasure on your own traffic before anything is stopped.
What executes
A vendor payment, payout batch, or cross-border transfer is released.
What normally goes wrong
The controls run in sequence and the release runs in parallel. A payment can clear a stale sanctions check, or leave via a beneficiary changed after approval.
The decision
The signals available at the moment of the action, and the rule that judges them.
Signals
- Amount and destination account
- Whether beneficiary details changed since approval
- Sanctions and watchlist screening freshness
- Velocity against normal pattern for this counterparty
The gate
Refuse release when beneficiary details changed after approval, or when screening is stale at the moment of release rather than at the moment of review.
ALLOW
The payment releases against a fresh check.
ESCALATE
An unusual amount or counterparty waits on treasury.
BLOCK
The payment does not release; the dossier names the control that failed.
Four stages left to right. Input signals — user or agent identity, context and data, tools and resources, spend and budget, policies, history and reputation, and environment — enter the Decionis Protocol. Inside, the protocol normalizes context and intent, evaluates policies and rules, runs a deterministic risk and policy engine, and explains the reason and evidence. It emits a verdict: ALLOW (authorized), ESCALATE (needs approval or more info), or BLOCK (high risk or out of policy). The verdict drives an enforcement action: allow, block, require approval, or throttle and limit. Every decision is recorded for audit, learning, and continuous improvement.
7 policies implement this pattern
Fork one and change the thresholds. Available today on 6 platforms.
Fintech Starter Pack
Velocity, sanctions, and treasury movement controls — automated proof of every KYC, AML, payout, and limit decision.
sdk
SAP Vendor Payment Release Gate
Holds a vendor payment run until the bank details, sanctions evidence, and dual approval all check out.
sap
LangChain Money-Moving Tool Gate
Wrap `send_refund`, `issue_payout`, or any tool that moves money — the inner tool only fires on an approve verdict.
langchain
Slack Discretionary-Spend Gate
Every spend approval ping above $5k carries the policy snapshot, the requester's authority, and a public verify URL.
slack
Slack Refund-Approval Dossier
Turns the refund approval that happens in a Slack thread into a signed verdict carrying the policy version and reviewer authority.
slack
SOC 2 Shopify Checkout Limits
Velocity, discount, and market-eligibility gates for Shopify checkout, B2B, and POS — with audit evidence for every exception.
shopify
Zapier Spend-Approval Gate ($500+)
Require a named approver before any Zap releases spend over $500 — the approval becomes a signed verdict, not a thumbs-up.
zapier
Govern this pattern with a published Zap
Start from the workflow already running in your source system. Decionis adds the policy decision and returns signed evidence without turning Zapier into the authority.
Prove it, then deploy it
A verdict you cannot check is an opinion, and a gate you cannot measure first is a risk of its own.
View the signed proof
Every verdict on this pattern produces a Decision Dossier: the signals it saw, the policy version that judged them, and an Ed25519 signature anyone can check against our published JWKS — without an account, and without trusting us.
Deploy in Shadow Mode
Run this gate against your own traffic while it stops nothing. You get the verdicts it would have returned and the actions it would have held, so the decision to enforce is made on your numbers rather than ours.
Related patterns
Teams that hit this one usually hit these next.
Related concepts
This pattern is one answer to each of these.
What to do next
The same five steps for every pattern in the library.
- Simulate this recipe
Run the policy against a realistic action in the browser. Push it past what the rules allow and watch the verdict come back. No account.
- View the signed Decision Dossier
See exactly what was decided and why: the rule that fired, the evidence it read, the policy version in force, and an Ed25519 signature you can verify yourself.
- Deploy in shadow mode
Measure what the policy would have caught on your own traffic without touching the live path. Every recipe defaults to shadow, so the first deployment carries no execution risk.
- Connect a real workflow
Point the same policy at the system where the action actually originates — a checkout, an ERP posting, a Zap, an agent's tool call.
- Share the verified result
Publish the proof: a public verification link, an embeddable badge, a PR comment, or an anonymized shadow-mode finding. This is how the next person discovers Decionis.