agentgovern

Ask AgentGovern before your workflow acts: allowed, blocked, or waiting for your approval.

Package Information

Released: this month
Downloads: 0 weekly / 0 monthly
Latest Version: 0.1.0
Author: Kero Group

Available Nodes

Documentation generating…

AgentGovern icon
AgentGovern
Ask AgentGovern before acting: allowed, blocked, or waiting for your approval

Documentation

n8n-nodes-agentgovern

Ask AgentGovern before your workflow acts. The node checks the
step against your agent's rules and sends the item out one of three outputs:

Output Meaning
Allowed Go ahead — connect your real step here.
Blocked Your rules say no (or it's over the monthly cap). Nothing happens.
Needs Approval AgentGovern pinged your dashboard. Turn on Wait for Approval to hold the run until you decide.

Install

n8n → Settings → Community Nodes → Install → n8n-nodes-agentgovern.

Use

  1. Add the AgentGovern node right before the step it should govern.
  2. Create an AgentGovern API credential and paste your agent's gr_live_… key. That's the
    only thing you paste. The credential test checks the key without logging anything.
  3. Type the Action in plain words — send email, read a doc, issue a refund.
    AgentGovern matches it to your rules. (Optional: Resource takes an exact rule name like
    email.send.)
  4. Connect Allowed to your real step.

Or import templates/govern-a-step.json for a ready-made
"Govern a step" workflow.

Output fields

Every item gets decision (allowed · blocked · pending_approval), allowed, reason,
audit_log_id, policy_id and resource (the rule it matched), added to the incoming fields
(turn off Keep Input Data to get only these).

The node fails closed: with Continue On Fail on, an unreachable AgentGovern routes the item to
Blocked; otherwise the workflow stops.

It also works as a tool for n8n's AI Agent node.

Develop

npm install
npm test        # builds, then runs the unit tests
npm pack        # tarball you can install into ~/.n8n/nodes for a local n8n

Discussion