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.
Execution pattern
Procurement approval
Check delegated authority before the purchase order posts.
- Category
- ApprovalsCommon in Manufacturing · Healthcare · Public sector · Hospitality & travel
- Works through
- sap · servicenow · slack · workday +1 more
- Proof
- Signed Decision DossierVerifiable against our published JWKS.
- Deploy
- Shadow Mode firstMeasure on your own traffic before anything is stopped.
What executes
A purchase order, vendor onboarding, or supplier change is submitted for release.
What normally goes wrong
Authority is expressed in a delegation matrix nobody reads at the moment of release. Segregation of duties is assumed rather than checked, so the same person can raise and approve.
The decision
The signals available at the moment of the action, and the rule that judges them.
Signals
- Amount against the requester's delegated limit
- Whether requester and approver are distinct
- Vendor risk and onboarding status
- Budget remaining on the cost centre
The gate
Refuse release above the requester's delegated limit, and refuse any release where requester and approver are the same person.
ALLOW
The order posts, and the dossier records the authority it posted under.
ESCALATE
The order routes to whoever holds the limit it exceeded.
BLOCK
The order does not post — for example when duties are not separated.
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.
The policy packs that decide this pattern
The bundles the Decionis evaluator ships, with every rule in the order it is tried.
SAP Execution Authority
Dual-gate governance for SAP ERP actions — state admission (completeness, budget, vendor, cost center) and execution authority (role, segregation of duties, regional holds, payment thresholds) before they execute.
sap · sap-procurement-v2 · 13 rules
Ops Spend Control
Dual-gate governance for back-office spend — spend admission (completeness, valid amount, verified vendor, expense/refund/credit limits) and disbursement authority (authorized role, segregation of duties, dual authorization, duplicate-payment detection) before money moves.
ops · ops-spend-v1 · 12 rules
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.
AI Approval
How do I require human approval before an AI agent acts?
Execution Governance
How do I govern execution across systems without rebuilding controls in each?
Independent Execution Authority
What decides whether a high-stakes action is allowed to happen?
Approval Bypass
Why did this payment go out without passing the approval chain?
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.