Decionis access
You need a Decionis workspace membership that can create Decision Dossiers. The Zapier connection provisions a scoped credential through the Decionis OAuth flow.
API documentation
Decionis for Zapier
Add a governed decision to any Zap. The public Decionis integration evaluates mapped operational context and returns an audit-ready Decision Dossier that later steps can route, notify on, or archive.
Before you start
Use representative test data and start in Shadow Mode so the first run observes the workflow without becoming an enforcement dependency.
A source app
Choose the event that should be evaluated, such as a new spreadsheet row, CRM deal, order, ticket, or agent-request record.
Safe sample data
Prepare a non-production example that contains only the business context required by policy. Exclude secrets and sensitive personal data.
Open the public Decionis integration
The Decionis app is available to all Zapier users and no invite code is required.
Connect Decionis
The connection uses OAuth. You do not copy a Decionis API key into Zapier.
| Step | What to do |
|---|---|
| 1 | Add Decionis to a Zap and select Create Decision Dossier. |
| 2 | Choose Connect a new account. |
| 3 | Sign in to Decionis if prompted, choose the intended workspace, and approve the scoped Zapier connection. |
| 4 | Return to Zapier and confirm the connected workspace is selected. |
Use the intended workspace
A Decision Dossier belongs to the Decionis workspace selected during connection. If a test lands in the wrong workspace, reconnect Decionis and choose the correct one before turning on the Zap.
Build and test your first Zap
This smoke test proves public discovery, OAuth, action execution, output mapping, and Decision Dossier verification.
| Step | Configuration |
|---|---|
| Trigger | Choose a source event and test it with one non-production record. |
| Action | Choose Decionis → Create Decision Dossier. |
| Map | Map Payload, Operational action type, Actor Reference, Evaluation Mode, and Idempotency Key. |
| Test | Run the action and confirm dossier_id, decision_id, status, outcome, dossier_url, and audit_ready are returned. |
| Verify | Open dossier_url and confirm the Decision Dossier matches the source record. |
| Publish | Keep Evaluation Mode set to Shadow, then turn on the Zap. |
Example Payload
{
"id": "zapier-smoke-001",
"amount": 1250,
"currency": "USD",
"vendor_id": "vendor-42",
"source": "zapier-public-beta"
}
Operational action type: APPROVE_INVOICE
Actor Reference: zapier-smoke-test
Actor Type: AUTOMATION
Resource: invoice
Evaluation Mode: SHADOW
Idempotency Key: zapier-smoke-001
Correlation Reference: zapier-smoke-001Field reference
Stable identifiers make retries safe and make the resulting dossier easier to find later.
| Field | Required | How to map it |
|---|---|---|
| Payload | Yes | JSON or plain text containing only the operational context policy needs. |
| Operational action type | Yes | A stable uppercase verb such as APPROVE_INVOICE, UPDATE_CUSTOMER, or EXECUTE_REFUND. |
| Actor Reference | Yes | The source user, service, agent, or workflow identifier. |
| Actor Type | Yes | AUTOMATION, HUMAN, AI_AGENT, or SERVICE. |
| Resource | No | The object or system affected, such as invoice, order, deal, or ticket. |
| Evaluation Mode | Yes | Start with SHADOW. Use PARALLEL or ENFORCEMENT only after validation. |
| Workflow Key | No | The Decionis workflow or vertical-pack key when your policy uses one. |
| Policy References | No | Comma-separated policy versions or a JSON string array. |
| Idempotency Key | Recommended | Map the source event, transaction, row, order, deal, or request ID. |
| Correlation Reference | No | A trace ID shared with downstream systems and support logs. |
Use the result
Later Zap steps can branch on the protocol result and carry audit evidence into the destination system.
| Output | Use |
|---|---|
| dossier_id | Stable ID for the audit-ready Decision Dossier. |
| decision_id | Stable ID for the underlying governed decision. |
| status | Decionis status such as ALLOW, BLOCK, ESCALATE, or REVIEW_REQUIRED. |
| outcome | Protocol outcome such as APPROVE, REJECT, ESCALATE, or REVIEW. |
| dossier_url | Link to retrieve or verify the resulting Decision Dossier. |
| policy_version | Policy version used for the evaluation. |
| payload_sha256 | Hash that binds the submitted payload to the dossier. |
| idempotent_replay | Whether this response replayed an earlier result for the same key. |
| audit_ready | Whether the returned artifact is ready for audit use. |
| dossier_json | Serialized dossier data for an archive or downstream record. |
Observe first
In Shadow Mode, record the outcome and dossier while the existing workflow continues. Compare the result with current controls before enabling enforcement.
Branch deliberately
When you later enforce, allow only the approved path to reach the protected action. Route reject, escalate, and review outcomes to an owner or queue.
Template ideas
These two-step workflows are good starting points. Each user connects their own accounts and chooses which source fields belong in the Payload.
Google Sheets → Decionis
Create a Decionis Decision Dossier for each new Google Sheets row. Map the row ID as the idempotency key and start in Shadow Mode.
HubSpot → Decionis
Create a Decionis Decision Dossier for each new HubSpot deal. Map the deal ID and only the non-sensitive commercial context needed by policy.
Shopify → Decionis
Create a Decionis Decision Dossier for each new paid Shopify order. Map the order ID and operational totals, not payment credentials or customer secrets.
Data safety
Decionis stores the governed context as part of the resulting Decision Dossier, so send only the minimum operational context policy needs.
Appropriate context
Event or transaction references, amounts and currencies, resource type, proposed action, workflow state, and non-sensitive policy evidence.
Do not submit
Health information, government-issued identifiers, payment-card or bank credentials, passwords, authentication tokens, secrets, or other sensitive personal data.
Troubleshooting
Check the connection, source mapping, and stable IDs before rebuilding the Zap.
| Symptom | Check |
|---|---|
| Decionis is not listed | Open the public Decionis app-directory page, then add the action from a new Zap step. |
| Connection fails | Sign in to Decionis in the authorization window, confirm workspace access, and reconnect the account. |
| Payload is rejected | Send valid JSON or plain text and remove secrets or unsupported sensitive data. |
| A retry creates an unexpected result | Map the original source event ID as the Idempotency Key and keep it stable across retries. |
| Dossier is in the wrong workspace | Reconnect Decionis and select the intended workspace before testing again. |
| A later step cannot find a field | Retest the Decionis action so Zapier refreshes the sample output, then remap the downstream step. |
Get support
Use Zapier Support for Zap editor, task, connection, or workflow-run issues. Include the identifiers below so Zapier and Decionis can trace the same run.
Zap URL or Zap ID: <redact private values>
Zap run or task ID: <id>
Decionis connection workspace: <workspace name>
Action: Create Decision Dossier
Decision ID: <decision_id if returned>
Dossier ID: <dossier_id if returned>
Correlation Reference: <source trace id>
Observed result: <status and outcome>
Expected result: <short description>
Never include passwords, bearer tokens, API keys, or an unredacted sensitive payload.Zapier workflow support
Zapier Support receives the workflow context needed to diagnose Zap runs and can escalate integration bugs to the Decionis app team.
Decionis product support
For workspace access, policy behavior, or Decision Dossier questions, use the Decionis help paths.