Actions10
- Guardrail Actions
- Workflow Actions
- Agent Passport Actions
Agent Passport → Revoke Passport
AI-generatedSummary
Revoke an Agent Passport using a Session ID, a Passport ID, or both. The operation uses the selected detection engine and can attach an optional audit reason and metadata to the revocation request.
Inputs
- Detection Engine — Choose Auto (Cloud), Cloud Only, or Local Simulation. Auto and Cloud use server-side passport state; Auto has no local fallback for unavailable cloud state according to the setting description. Local Simulation is for testing and keeps state in this n8n process.
- Session ID — Session associated with the passport; if left empty, the node can read it from the incoming item. Revoke accepts this or Passport ID.
- Passport ID — Passport to revoke. Optional when a Session ID is provided.
- Revocation Reason — Audit-safe reason for revocation.
- Options — Optional settings include audit metadata JSON, an overriding Project ID, per-call timeout, batch concurrency, deduplication of identical items, and whether to include the recursively sanitized raw API response. Metadata is redacted before sending. Identical items reuse a call by default; output order is preserved when processing items in parallel.
Output shape
A list of n8n items containing the revocation result for each input item.
A successful revocation is described by the UI notice as returning PASSPORT_REVOKED on Safe. The provided source pack is truncated and does not expose the revoke handler's response mapping, so the exact item fields and error shape cannot be determined.