Zapier

Connect AxioRank to Zapier so a governance event can trigger a Zap, and a Zap can approve a held call, quarantine an agent, or respond to an incident. No code.

The AxioRank Zapier integration puts your governance events and one-click responses into Zapier's automation graph. A held approval or a detected kill chain can trigger a Zap into any of Zapier's thousands of apps, and a Zap can act back on AxioRank: approve or deny a held call, quarantine an agent, update an alert, or respond to an incident. It is the no-code path to wiring AxioRank into the tools your team already runs.

Connect

In AxioRank, open Settings, API keys and create a workspace key with the automation scope. Unlike a gateway key (which binds to a single agent), a workspace key acts for the whole workspace, the way an admin session does.
Add the AxioRank app in Zapier and paste the key when it asks you to connect. Zapier calls GET /api/v1/automation/me to confirm the key and label the connection with your workspace name.

The key's role ceiling bounds what the connection can do: reading events and resource lists needs viewer, while the write actions (approve, quarantine, respond) need member or higher.

Triggers

A trigger fires a Zap when AxioRank emits an event. It uses Zapier's REST hooks (instant delivery through the same signed, retried webhook pipeline that backs every subscriber), with a recent-events poll as the fallback sample. The public event types are:

Event	Fires when
`tool_call.evaluated`	A governed tool call gets a verdict.
`tool_call.held`	A call is held for approval.
`approval.pending`	A hold is waiting on a human.
`approval.escalated`	A hold has sat past its escalation window.
`approval.resolved`	A hold is approved or denied.
`kill_chain.detected`	Correlated calls look like an attack.
`inbound.evaluated`	An inbound agent request is verified.
`ml.assessed`	The ML lane returns a threat class.
`card.verified`	An external MCP server or agent card is preflighted.
`agent.quarantined`	An agent is quarantined.
`key.created`, `key.revoked`	An API key is minted or revoked.
`checkpoint.sealed`	The audit ledger seals a checkpoint.

Actions

An action lets a Zap act back on AxioRank. Where an action targets a specific record, Zapier fills the id field from a live dropdown (pending holds, active agents, recent alerts and incidents) so you pick a target instead of pasting a raw id. Actions are attributed to the connection's key in the audit log.

Action	What it does
Resolve approval	Approve or deny a held tool call, with an optional reason.
Quarantine agent	Quarantine or release an agent (a reversible kill switch).
Update alert	Re-triage an alert (acknowledge or resolve).
Respond to incident	Run a structured response on an incident.

Example Zaps

Post every kill_chain.detected event to a Slack channel and open a Jira ticket. When an approval.pending event lands, message the on-call approver, and let their reply resolve the hold. When an incident opens, page the team and quarantine the implicated agent in one step.

One API, many tools

The connection talks to the workspace-key automation surface, exposed at the platform-neutral base path /api/v1/automation/* (an alias onto the same handlers). The n8n community node uses the same surface, so any automation tool that can send a bearer token and JSON can drive AxioRank the same way. Reads and writes are rate-limited per workspace.

Next steps

Webhooks: the signed event pipeline the triggers ride on.
n8n: the same automation surface from an n8n workflow.
Approvals: the hold model a Zap can resolve.