1. Connect
Add Decionis to a Zap and authorize with your Decionis browser session. The app provisions a scoped credential automatically.
Loading…
API documentation
Zapier and Make 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 |
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.
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 |
| 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 should retry 408, 425, 429, and 5xx responses while preserving the same Idempotency-Key value.