No-Code (n8n, Zapier, Make)
The no-code integrations exist for the people who run their AI governance workflow inside n8n, Zapier, or Make — the non-developer Compliance Officer wiring "when a trace gets flagged, post to Slack and create a Jira ticket" without writing code. All three packages share the same surface: one Action (send a trace into Adjudon) and one Trigger (fire a workflow when a review item lands). Anything beyond those two verbs goes through the Traces API directly.
All three packages are at v0.1.0 — the marketplace
listings (n8n Community Nodes, Zapier Public Apps, Make Custom
Apps) are in the publication pipeline. Until they show up in the
public catalogues, install the packages directly from GitHub or
contact [email protected] for a private invite link. The
runtime code is shipping; the marketplace approval queue is not
yet drained.
n8n
npm install n8n-nodes-adjudon
For n8n Cloud, request the integration via the Community Nodes panel once the listing is approved.
| Verb | Action | Configuration |
|---|---|---|
| Action | Send Decision Trace | Workspace API key + Agent ID + JSON body for inputContext and outputDecision |
| Trigger | New Review Item | Polls /api/v1/review-queue every N minutes; emits one workflow run per new item |
The Trigger uses standard n8n credentials — an
AdjudonApi credential type stores the API key encrypted at
rest in the n8n database. The credential is reusable across
multiple workflows.
Zapier
| Verb | Type | Configuration |
|---|---|---|
| Action | sendTrace (Create) | Workspace API key + Agent ID + Input Context + Output Decision |
| Trigger | newReview (Polling) | Fires on every new flagged or escalated review item |
Authentication is the standard Zapier custom-app pattern: the
user pastes an adj_live_* key into the connection form on
first use; Zapier stores it encrypted and forwards it as
Authorization: Bearer ... on every request.
Make.com
| Verb | Type | Configuration |
|---|---|---|
| Action | Send Trace module | API-Key connection + scenario-bound payload mapping |
| Trigger | Watch Reviews poll | Polls every N minutes; emits one bundle per review item |
| Webhook | Review Decision | Inbound webhook a customer's other tooling can hit to forward review verdicts |
The Make custom-app spec lives in
packages/integrations/make/. Validation runs against the spec
(make/scripts/validate.js) on every release to enforce the
no-API-key-in-logs rule — the Authorization header is
sanitised by the validator before approval.
What this is NOT
- Not a full SDK. The no-code integrations expose two verbs. Policy management, hash-chain verification, FRIA wizard, incident clocks, and SCIM all stay on the developer-facing surfaces. If you need more than send-trace + receive-review, the SDKs (Python, Node) are the path.
- Not a workflow engine. Adjudon does not orchestrate the workflow; n8n / Zapier / Make do. Adjudon is the data source ("here's a new flagged review") and the data sink ("here's one more decision"). The conditional logic, branching, and fan-out live in the no-code platform.
- Not the only integration path. A team using Slack-based
workflows can subscribe a webhook to
alert.triggeredand post directly to a Slack incoming webhook URL without any of these packages — see Webhooks.
Resources
- Quickstart — first trace via the SDK path
- Traces API — the underlying HTTP surface every Action calls
- Reviews API — the resource the Triggers poll
- Webhooks — the alternative push-based integration path
- GitHub:
github.com/adjudon/adjudon-integrations(source for all three packages and the marketplace-publication tracker)