Route IAM events with GPT-4o-mini, forgeLLM, Slack, email, and audit logs
Ready for 3.0Ready for 3.0. This template uses no nodes that n8n 3.0 removes. No removed nodes, versions or helpers found. Static check, last run 2026-10-19.
Nodes used (14)
- Webhook
n8n-nodes-base.webhook - AI Agent
@n8n/n8n-nodes-langchain.agent - OpenAI Chat Model
@n8n/n8n-nodes-langchain.lmChatOpenAi - Simple Memory
@n8n/n8n-nodes-langchain.memoryBufferWindow - AI Agent Tool
@n8n/n8n-nodes-langchain.agentTool - Structured Output Parser
@n8n/n8n-nodes-langchain.outputParserStructured - Http Request Tool
n8n-nodes-base.httpRequestTool - Slack Tool
n8n-nodes-base.slackTool - Gmail Tool
n8n-nodes-base.gmailTool - Data Table Tool
n8n-nodes-base.dataTableTool - Switch
n8n-nodes-base.switch - Data table
n8n-nodes-base.dataTable - Respond to Webhook
n8n-nodes-base.respondToWebhook - Edit Fields (Set)
n8n-nodes-base.set
What it does
How It Works This workflow automates Identity and Access Management (IAM) event governance using an AI agent, targeting security operations teams, compliance officers, and IT governance teams managing cloud or enterprise IAM systems. The core problem it solves is the manual, error-prone review of IAM events, such as permission grants, role changes, and access revocations, which are high-risk and require rapid, consistent decision-making at scale. When an IAM event is received via webhook (POST), a Governance Agent powered by an LLM evaluates it using contextual memory, an Access Signal Agent, and a forgeLLM API. It cross-references compliance rules via a Compliance Query Tool and logs findings through an Audit Log Tool. Notifications are dispatched via Email and Slack. Based on the agent's decision, a Rules-based Router directs the event into one of three branches, namely: Approved, Revoked, or Escalated, where event data is prepared and stored accordingly. A unified response is then returned to the caller, ensuring every IAM event is audited, classified, and actioned without human bottlenecks. Setup Steps 1. Configure the Webhook node with your IAM event source endpoint. 2. Add LLM credentials to the forgeLLM API Tool node. 3. Set up Governance Model with your policy prompt and connect Conversation Memory. 4. Configure Access Signal Agent with your access data source credentials. 5. Connect Compliance Query Tool to your compliance database or API. 6. Add Gmail/SMTP credentials to the Email Notification Tool. 7. Add Slack Bot token to the Slack Notification Tool. Prerequisites - forgeLLM or compatible LLM API key - Slack Bot token - Gmail/SMTP credentials Use Cases - Automatically approve or revoke IAM role assignments based on policy. Customization - Swap forgeLLM for OpenAI or Anthropic models. Benefits - Eliminates manual IAM review bottlenecks.