n8n
Drive AxioRank from an n8n workflow with the community node. Trigger a workflow on a governance event, and act back to approve a held call, quarantine an agent, or respond to an incident.
The n8n-nodes-axiorank community node brings AxioRank into n8n. A workflow can
start from an AxioRank governance event and act back on the control plane: approve
or deny a held call, quarantine an agent, update an alert, or respond to an incident.
It is the self-hosted, open-source complement to the
Zapier integration, backed by the same automation API.
Install
- In n8n, open Settings, Community nodes, Install and add
n8n-nodes-axiorank. On a self-hosted instance you can also install it from npm into your n8n data directory. - In AxioRank, open Settings, API keys and create a workspace key with the
automationscope. It acts for the whole workspace, unlike a per-agent gateway key. - Add an AxioRank credential in n8n: the base URL (
https://app.axiorank.com) and the workspace key. The credential test callsGET /api/v1/automation/meto confirm the key and read back your workspace.
Nodes
- AxioRank Trigger: starts a workflow when AxioRank emits an event. It registers
a subscription against the signed webhook pipeline, so delivery
is the same as any other subscriber. Pick the event types to listen for, for
example
tool_call.held,approval.pending,kill_chain.detected, oragent.quarantined(the full set is listed under Zapier triggers). - AxioRank: acts back on the control plane. Resolve an approval (approve or deny a held call with a reason), quarantine or release an agent, update an alert, or run a structured incident response. Id fields load from live dropdowns so you select a pending hold or a live agent instead of pasting an id. Every write is attributed to the credential's key in the audit log.
Example workflow
Trigger on approval.pending, branch on the tool and risk in the payload, and for
a low-risk match auto-approve the hold while routing everything else to a human in
chat. Or trigger on kill_chain.detected and quarantine the implicated agent, then
open a ticket.
How it connects
The node talks to the platform-neutral automation surface at
/api/v1/automation/*, the same workspace-key API the Zapier app uses (it aliases
onto the same handlers). Reads and writes are rate-limited per workspace, and a
missing scope or an insufficient role returns a clear 401 or 403.
Next steps
- Zapier: the same automation surface, as a Zapier app.
- Webhooks: the signed event pipeline the trigger subscribes to.
- Response engine: AxioRank's own rule-driven automation, which can also POST to an n8n webhook.