1. Connect
Add Decionis to a Zap and authorize with your Decionis browser session. The app provisions a scoped credential automatically.
API documentation
Zapier, Make, and n8n connectors
Put a Decionis policy gate in front of any automation while keeping the workflow portable across commerce, ERP, CRM, ITSM, and agent systems.
Zapier
The deployed Decionis OAuth app exposes a Create Decision Dossier action.
2. Map
Map the upstream payload, a stable action type, actor reference, mode, and the source event ID as the idempotency key.
3. Branch
Use outcome, status, reason codes, dossier URL, and dossier JSON in later Zap steps. Start in Shadow Mode.
| Zapier field | Recommended value |
|---|---|
| Payload | The complete mapped upstream object as JSON |
| Operational Action Type | A stable verb such as APPROVE_INVOICE |
| Actor ID | The workflow or upstream actor identifier |
| Evaluation Mode | SHADOW for first deployment |
| Idempotency Key | The upstream event, request, or transaction ID |
Public setup guide
Use the dedicated Zapier guide for the public listing, OAuth connection, complete smoke test, field and output reference, template ideas, data safety, and support paths.
Published on Zapier on August 4, 2026. Each route opens the reviewed template directly.
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.
Published on ZapierAug 4, 2026
HubSpot
Create Decionis decision dossiers for new HubSpot deals
Every new HubSpot deal gets a signed policy decision.
For Deal governance, revenue operations, and CRM-controlled handoffs.
Published on ZapierAug 4, 2026
Shopify
Create Decionis decision dossiers for new paid Shopify orders
Every paid Shopify order produces verifiable decision evidence.
For Commerce operations, margin controls, refunds, and order governance.
Make
Use Make HTTP V4 with the Decionis API key stored in Make's encrypted keychain.
Method: POST
URL: https://api.decionis.com/v1/protocol/evaluate-decision
Authentication: API key credentials
Header name: Authorization
Header value: Bearer <DECIONIS_API_KEY>
Header: Idempotency-Key = {{source_event_id}}
Body type: application/json
{
"org_id": "{{DECIONIS_ORG_ID}}",
"decision_type": "AUTOMATION_ACTION",
"amount": {{amount}},
"mode": "SHADOW",
"workflow_key": "automation_action",
"context": {
"source_system": "make",
"source_event_id": "{{source_event_id}}",
"payload": {{source_payload}}
}
}Credential handling
Store the API key as a Make HTTP V4 API-key credential. Do not place it in the scenario body, query string, notes, or exported screenshots.
n8n
Every automation step asks permission before it executes. Add the HTTP Request recipe below in front of the protected step.
HTTP Request recipe
Works on any n8n version, self-hosted or cloud. Add an HTTP Request node before the protected step, store the API key as a Header Auth credential, and branch on the returned outcome. The four example workflows below use this recipe, with built-in nodes only.
Node: HTTP Request
Method: POST
URL: https://api.decionis.com/v1/protocol/evaluate-decision
Authentication: Generic Credential Type → Header Auth
Header name: Authorization
Header value: Bearer <DECIONIS_API_KEY>
Header: Idempotency-Key = {{ $json.event_id }}
Body Content Type: JSON
{
"org_id": "<DECIONIS_ORG_ID>",
"decision_type": "AUTOMATION_ACTION",
"amount": {{ $json.amount }},
"mode": "SHADOW",
"workflow_key": "automation_action",
"context": {
"source_system": "n8n",
"source_event_id": "{{ $json.event_id }}",
"payload": {{ JSON.stringify($json) }}
}
}Credential handling
Store the API key as an n8n Header Auth credential. Do not place it in the node body, query string, sticky notes, or an exported workflow JSON that leaves your instance.
| Step | n8n node | Behaviour |
|---|---|---|
| 1. Trigger | Any trigger node | The upstream event that would otherwise execute directly |
| 2. Gate | HTTP Request | POST the mapped payload and receive outcome, status, reason codes, and dossier references |
| 3. Branch | IF on {{ $json.outcome }} | True branch proceeds with the protected action; false branch escalates |
| 4. Prove | Any downstream node | Carry dossier_id and the dossier URL into the ticket, message, or record you write |
IF node condition
Left value: {{ $json.outcome }}
Operator: String → is equal to
Right value: APPROVE
true → run the protected action
false → escalate (REJECT, REVIEW, and ESCALATE all land here)Example workflows
Download a file and use Import from File in the n8n editor. Each workflow ships with example input data pinned on the sample node, runs in SHADOW mode, and expects you to replace the org ID placeholder and attach your own credential before switching to enforcement.
Require approval over $500
A purchase request is evaluated before the order is submitted. Anything the policy does not approve is routed to a finance approver instead of executing.
Block unknown domains before invoices
An inbound invoice is evaluated against the known vendor domain and banking details before it is queued for payment.
Refunds within policy
A refund request is evaluated against amount, elapsed days, and prior refund history before the refund is issued.
Pause on risk score change
A scheduled risk-signal check evaluates a score movement and pauses the downstream automation instead of letting it continue unattended.
Avoid platform lock-in
Decionis is the decision layer, not the source-system owner.
| Layer | Portable contract |
|---|---|
| Source | Shopify, ERP, CRM, ITSM, agent, webhook, or another Zap, Make module, or n8n node |
| Gate | The same Decionis evaluation contract and policy version |
| Result | APPROVE, REJECT, ESCALATE, or REVIEW plus reason codes |
| Proof | Signed Decision Dossier URL and integrity metadata |
Retries
Safe retries require a stable idempotency key.
Transient failures
The Zapier action retries one transient HTTP failure immediately and then asks Zapier to replay after 30 seconds. Make scenarios and n8n HTTP Request nodes should retry 408, 425, 429, and 5xx responses while preserving the same Idempotency-Key value.