Loading…
Open-Policy Exchange
~4 min to deploy
Zapier Risk-Score Change Pause
Pauses a Zap the moment a customer's risk score crosses the line, instead of letting the automation keep firing.
For: Risk and ops teams whose Zaps act on customer records
SOC 2 CC7.2ISO 27001 A.5.7Risk decision evidence
What it enforces
Elevated-risk escalation
Escalates an action on a customer whose risk score crossed the elevated band.
Restricted-customer block
Blocks any automated action on a customer flagged restricted.
Score-jump restraint
Restrains the workflow when a risk score moves more than the allowed delta in one step.
zapier-risk-score-change-pause.yaml
# Zapier Risk-Score Change Pause
# Fork: thresholds mirror the "Regulated customer actions" template.
apiVersion: decionis.dev/v1
kind: PolicyPack
metadata:
name: zapier-risk-score-change-pause
surface: zapier
workflow_key: regulated_customer_action
standards: [SOC2-CC7.2, ISO27001-A.5.7]
defaults:
mode: shadow
emit_dossier: true
rules:
- name: elevated_risk_escalation
when: "action == 'customer.act'"
decision: |
ALLOW IF risk_score < 60
ESCALATE IF risk_score < 85
BLOCK OTHERWISE
reason_code: risk_score_over_threshold
- name: restricted_customer_block
when: "action == 'customer.act'"
decision: |
BLOCK IF restricted == true
ALLOW OTHERWISE
reason_code: restricted_customer
- name: score_jump_restraint
when: "event == 'risk_score.changed'"
decision: |
RESTRAIN IF abs(risk_score - previous_risk_score) > 20
ALLOW OTHERWISE
reason_code: risk_score_jump_needs_review
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.