n8n Webhook to EEP Validation Envelope with Webhook Response

Turn n8n Webhook Events into an EEP Validation Evidence Envelope (with Response)

Use this n8n workflow to convert any incoming webhook event into a structured EEP (Evidence/Execution Policy) Validation Envelope for Aegis-EGE—including action, authority, policy, redaction, consequence, and sensitive-path context—then return the envelope to the consumer via the webhook response.

What this workflow does

• Receives a POST event through an n8n Webhook node.
• Combines the request with workflow and execution metadata.
• Builds an explicit EEP envelope that includes: the proposed action and target, an authority reference, a policy reference, a consequence class, required controls and approvals, a redaction profile, and sensitive paths.
• Returns the envelope to Aegis-EGE, where it can be compiled into evidence, bound to a signed permit, and evaluated before the downstream side effect is allowed.
• Enables state verification after execution so Aegis-EGE can record outcome evidence.

Setup

• Import the workflow and open the EEP Live Webhook node.
• Configure Header Auth: use an Authorization: Bearer token and keep the token outside the workflow JSON.
• In the Code node, set your declared agent identity plus EEP fields (target, authority, policy, redaction profile, consequence class, controls, approvals, sensitive paths).
• Publish the workflow and use the production webhook URL as the EEP event source for Aegis-EGE.
• Validate using synthetic or non-sensitive data first.

Use cases

• Automation engineers needing policy-backed authorization before triggering downstream side effects.
• SaaS operators routing sensitive operations through Aegis-EGE with explicit redaction and sensitive-path context.
• Teams integrating n8n to produce verifiable evidence artifacts for execution governance.

Technical details

• n8n Webhook (POST receiver)
• Code (constructs the EEP validation envelope)
• Respond to Webhook (returns the envelope to the consumer)
• Sticky Note (workflow documentation)

Requirements: n8n Cloud or self-hosted n8n. Compatible with Aegis-EGE / EEP consumers.