Loading…
Execution pattern
Third-party data sharing
Decide what reaches an external system before the request is made.
What executes
A workflow posts customer or business data to a webhook, an external API, or a vendor integration.
What normally goes wrong
Integrations are added for a narrow purpose and then reused for broader ones. The destination stays approved while the payload quietly widens, so the disclosure is a change in data rather than a change in configuration.
The decision
The signals available at the moment of the action, and the rule that judges them.
Signals
- Destination and its approved purpose
- Fields present in the payload
- Data classification and residency constraints
- Whether the recipient has a current agreement
The gate
Permit only the fields the destination was approved to receive, and refuse payloads carrying classifications the agreement does not cover.
ALLOW
The request proceeds with the approved payload.
ESCALATE
A widened payload waits on the data owner.
BLOCK
The request does not leave; the dossier records the fields withheld.
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.
6 policies implement this pattern
Fork one and change the thresholds. Available today on 6 platforms.
LangChain Regulated-Data RAG Gate
Gates retrieval and external API calls that touch regulated records — restricted subjects never leave the boundary.
langchain
AWS Agent Egress & Spend Gate
Opens sandbox egress only for the exact target the grant covers, and stops a run that would blow the account budget.
aws
Make Scenario Execution Gate
Evaluate any Make scenario before its protected module runs, using the HTTP V4 request recipe and the bearer key in Make's keychain.
make
n8n HTTP-Node Execution Gate
Call the evaluate endpoint from an HTTP Request node and branch the workflow on the verdict before the write step runs.
n8n
Salesforce Regulated-Account Action Gate
Holds account changes on regulated or restricted customers until the right reviewer signs the record.
salesforce
Webhook Execution Receipt
Gate an inbound webhook before it mutates state — replay protection, signature checks, and a dossier per delivery.
sdk
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.