n8n-nodes-guardian

Official n8n community node for Guardian Safety Gate — the policy decision layer for AI agents, workflows, and backends.

Guardian decides whether an action is allowed before it runs. It does not perform the action itself. Use it to require human approval for high-risk operations, block forbidden actions, or log everything for compliance.

What it does

Place a Guardian node in your workflow between the decision point and any sensitive action (payments, deletions, emails, AI tool calls, etc.). The node checks the action against your policies and routes your workflow to one of three outputs:

| Output | Meaning | What your workflow does next | |---|---|---| | ✅ Allowed | Action passed all policies | Continue and execute the action yourself | | ❌ Denied | Action was blocked by a policy rule | Stop, log, or handle the block | | ⏳ Needs Approval | A human must approve first | Pause and wait for the approval webhook |

Guardian evaluates; your workflow executes. The payment, email, deletion, or API call is still performed by your own n8n nodes.

Operations

Evaluate & Confirm (recommended)

Check the action with Guardian and, if allowed, record the decision. Use this for most workflows. After the "Allowed" branch, connect your own execution node (HTTP Request, Send Email, Delete Row, etc.).

Evaluate Only

Get the decision without recording it. Use when you want to inspect the decision or route the workflow manually before confirming.

Confirm Execution

Tell Guardian that an already-approved intent was executed by your workflow. This completes the audit trail.

Check Status

Poll for the current status of a pending approval.

Requirements

• Self-hosted or local n8n only. Community nodes are not supported on n8n Cloud.
• You need a Guardian API key from your Guardian dashboard.

Setup

1. Install the node

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

n8n-nodes-guardian

Or install via terminal from your n8n directory:

npm install n8n-nodes-guardian

2. Create credentials

• Go to Credentials → New → Guardian API
• Paste your API Key (found in Guardian → Settings → API Keys)
• Set your Base URL (your Guardian instance URL, e.g. https://guardian-backend-orc1.onrender.com)

3. Add to workflow

Drop the Guardian Safety Gate node before any sensitive action node. The "Allowed" branch should connect to your execution node; the "Denied" and "Needs Approval" branches handle the guard cases.

Example Workflow

[Trigger] → [Guardian: Evaluate & Confirm]
                 ↓ Allowed              ↓ Denied              ↓ Needs Approval
        [n8n: Send Payment]    [n8n: Stop + Log]    [n8n: Wait for approval]
                                                                     ↓
                                                            [Guardian approves]
                                                                     ↓
                                                     [n8n: Send Payment]

Notice: Guardian only makes the decision. The actual payment is sent by your own n8n nodes after the "Allowed" branch.

Payload Tips

The payload field should be a JSON object matching your policy rules. Example:

{
  "amount": 4500,
  "currency": "USD",
  "recipient": "vendor-acme",
  "category": "marketing"
}

Your Guardian policy rules match against these fields (e.g. "block if amount > 5000").

Support

• Docs: https://guardiansafetygate.com/docs
• Issues: Open a GitHub issue on this repo