connexum

n8n community node: Connexum Govern puts any n8n workflow step under My-CC governance. Each item passes data readiness (the source's access for the agent's passport) and the runtime gate (the governance server's check-action) before the next node runs; it

Package Information

Released: this month
Downloads: 0 weekly / 0 monthly
Latest Version: 0.1.0-beta.1

Documentation

@connexum/n8n-nodes-connexum

n8n community node: Connexum Govern. Put it in front of any step that acts (a database write, an HTTP request, an
email). Each item is checked by My-CC before the next node runs:

  1. Data readiness: the source the step reads or writes must give this agent's passport access, from the
    organization's sealed scans. No access blocks; read-only blocks a writing step; an unscanned source blocks.
  2. Runtime gate: the governance server's check-action decides whether the action may run.

Items that may proceed leave on Allowed. The rest leave on Blocked with
connexum: { decision, layer, action, reason } (and parkId / approvalId when a person must approve), so the
workflow can notify someone instead of acting.

Setup

  • Install the package as a community node (Settings, Community nodes) on a self-hosted n8n.
  • Credential Connexum (My-CC) Agent: governance server URL, the agent's own service token, agent id, passport id.
  • Node parameters: Action Name (as My-CC knows it, for example orders.update), Writes Data, Data Source ID.

Built on @connexum/govern. Tests: tests/package-shape.test.mts (every CI run) and tests/n8n-workflow.test.mts
(a real n8n 2.44.5 on Node 24 executing a workflow against a running governance server; set N8N_BIN and NODE24_BIN).

Discussion