Description

n8n-nodes-navige

Navige is AI agent governance infrastructure — a real-time checkpoint that sits between an agent (or, here, an n8n workflow) and the action it’s about to take. Every call is checked against your no-code policy rules — deterministic code, not a model — and logged to a tamper-evident audit trail.

This community node lets an n8n workflow ask Navige for a decision before it performs a real action, and pause for human approval when your policies require it.

Operations

| Operation | Description |
|—|—|
| Check Governance Decision | Ask Navige whether an action is allowed, denied, or needs human approval, before your workflow performs it. |
| Check Approval Status | Poll the result of a decision that came back pending (used together with Wait For Decision off). |

That’s it — two operations, both backed by the same /enforce endpoint every other Navige integration uses (MCP, the Python/Node SDKs, the Salesforce package). Earlier versions of this node also had operations for fetching audit logs, usage stats, and the kill switch. Those were removed in v3.0.0: in the current Navige architecture they’re session-authenticated dashboard features, not something reachable with an API key — exposing them to a workflow’s API key would mean a single leaked credential could also read your full audit log or trigger your kill switch, not just check a decision. If you need those, use the Navige dashboard directly.

Installation

In your n8n instance, go to Settings → Community Nodes → Install and enter:

n8n-nodes-navige

Credentials

Get a virtual key from your Navige dashboard: Agents → + New agent. It’s shown once, starts with nv_, and is scoped to that one agent.

Set up the Navige API credential in n8n with that key.

Example: govern a workflow step

1. Add a Navige node to your workflow, right before the step you want governed
2. Select operation Check Governance Decision
3. Set Tool Name to describe the action (e.g. send_invoice)
4. Set System to your workflow’s name, so it’s easy to find in your Navige registry
5. Leave Wait for Decision on if your workflow can tolerate waiting up to 5 minutes for a human approval; turn it off and use Check Approval Status afterward if it can’t
6. Leave Stop Workflow If Not Allowed on — the node throws and halts the workflow on deny/rejected/expired

The node outputs the real decision object: { decision: "allow" | "deny" | "approved" | "rejected" | "expired" | "pending", reason?, approvalId?, expiresAt? }.

Links

• Website: navige.ai
• Setup guide: navige.ai/setup.html
• Technical reference: navige.ai/technical.html
• Dashboard: app.navige.ai