n8n
Integrate Intutic governance with n8n — the workflow automation platform.
How it works
n8n is governed at two levels. The sync-daemon automatically handles detection and config generation:
- Detection: The sync-daemon checks for active
n8nprocesses running locally. - Blocking gate (workflow-level): It writes an n8n external hook module to
~/.intutic/hooks/n8n-governance-hook.js. Loaded viaEXTERNAL_HOOK_FILES(see below), itsworkflow.preExecutehook runs before every workflow execution, evaluates each node's type and parameters against the compiled protection floor and your policy snapshot, and throws on a block-severity match — aborting the execution with an error naming the offending node and rule. - Workflow Generation: It builds and writes a pre-configured, importable n8n 1.x workflow JSON to
~/.intutic/n8n/governance-workflow.json(event forwarding — telemetry, not enforcement). - Environment Setup: It generates a
.intutic/env/n8n.envfile within the workspace, plus~/.intutic/n8n/INSTALL.mdwith the gate's installation steps.
The blocking gate
Manual, deployment-side installation
EXTERNAL_HOOK_FILES is read by the n8n server process at startup — the Intutic daemon cannot set another process's environment. Until you set it and restart n8n, the gate does not run:
export EXTERNAL_HOOK_FILES=~/.intutic/hooks/n8n-governance-hook.jsGranularity is honest here: n8n's hook surface is per workflow execution, not per tool call. The gate maps the shared rule model onto it — a node's type stands in for the tool name (subject: tool rules match it), and the node's serialized parameters are what command/path rules and WHERE (argPattern) rules match. One offending node aborts the whole execution.
Config Details
| Property | Value |
|---|---|
| Harness type | n8n |
| Config file | ~/.intutic/n8n/governance-workflow.json |
| Status | ✅ Fully Supported (Phase 3) |
| Format | n8n 1.x Workflow JSON |
Setup & Activation
1. Detect & Generate
Run the Intutic init command to detect and configure active harnesses:
intutic initIf an active n8n instance is running, the sync-daemon will register it and write the importable workflow JSON to ~/.intutic/n8n/governance-workflow.json.
2. Import into n8n
- Open your local or self-hosted n8n instance.
- Go to Settings > Import Workflow and select the generated file at
~/.intutic/n8n/governance-workflow.json. - Activate the imported workflow.
3. Add API Key
Add your INTUTIC_API_KEY to your environment or configure it in the n8n Credentials UI as a header token. The webhook router will intercept and forward workflow execution trace audits to the Intutic control plane.