Loading…
Open-Policy Exchange
~4 min to deploy
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.
For: Ops and finance teams running spend workflows in Zapier
SOC 2 CC8.1ISO 27001 A.5.15Spend approval evidence
What it enforces
Approval threshold
Escalates any spend release at or above $500 to the named approver.
Approver authority check
Blocks a release when the approver's authority limit is below the amount.
Self-approval block
Blocks a release where the requester and the approver are the same person.
zapier-approval-over-500.yaml
# Zapier Spend-Approval Gate ($500+)
# Fork: drop the "Create Decision Dossier" action ahead of the protected step
# in your Zap and map amount / requester / approver.
apiVersion: decionis.dev/v1
kind: PolicyPack
metadata:
name: zapier-approval-over-500
surface: zapier
workflow_key: discretionary_spend_release
standards: [SOC2-CC8.1, ISO27001-A.5.15]
defaults:
mode: shadow
emit_dossier: true
rules:
- name: approval_threshold
when: "action == 'spend.release'"
decision: |
ALLOW IF amount_usd < 500
ESCALATE OTHERWISE
reason_code: spend_over_approval_threshold
- name: approver_authority_check
when: "action == 'spend.release'"
decision: |
BLOCK IF approver.authority_limit_usd < amount_usd
ALLOW OTHERWISE
reason_code: approver_authority_insufficient
- name: self_approval_block
when: "action == 'spend.release'"
decision: |
BLOCK IF approver.email == requester.email
ALLOW OTHERWISE
reason_code: self_approval_not_permitted
Fork it, change the thresholds to match your environment, and deploy in shadow mode first — it defaults to listen-only so nothing in your live pipeline changes.
How to install it
Follow the install path for this surface, then paste the forked YAML as your policy config.
What to do next
This recipe is one step in a path. The same five steps apply to every recipe in the exchange.
- 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.