Block 1 - Start Governance Scan
- Type / Role
- n8n-nodes-base.manualTrigger - manualTrigger
- Config choices
- Version 1
How It Works This workflow automates end to end code repository governance scanning using a multi agent AI orchestration system. Designed for engineering leads, DevSecOps teams, and CTOs, it replac...
n8n-nodes-base.manualtrigger, n8n-nodes-base.ssh, @n8n/n8n-nodes-langchain.agent, @n8n/n8n-nodes-langchain.lmchatopenai, @n8n/n8n-nodes-langchain.agenttool, @n8n/n8n-nodes-langchain.outputparserstructured, n8n-nodes-base.set, n8n-nodes-base.if
This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Cheng Siong Chin.
Original n8n.io sourceThis workflow automates end-to-end code repository governance scanning using a multi-agent AI orchestration system. Designed for engineering leads, DevSecOps teams, and CTOs, it replaces manual code audits with a structured, AI-driven compliance and security analysis pipeline. The workflow begins by extracting repository metadata, which is passed to a Governance Orchestrator Agent coordinating four specialised sub-agents: Static Code Analysis, Architectural Compliance, CTO Report Generation, and Security Vulnerability Analysis. Outputs are consolidated into a Structured Governance Output, formatted as a final report, then routed by severity level. Critical findings trigger escalation alerts and are aggregated separately, while medium findings are handled independently. All paths converge to merge analysis results, enrich the final output, and deliver a board-ready governance report with full audit traceability.
Extract Repository Metadata with your Git provider or repository API credentials.Check Critical Issues Threshold node to match your governance policy.Prepare Escalation Alert with your notification channel.This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.
Showing the first 24 of 30 workflow blocks. Download the JSON for the full node graph.
| Workflow | Scan code repositories for governance issues with GPT-4o and severity-based reports |
|---|---|
| Complexity | advanced |
| Nodes | 30 |
| Categories | DevOps, AI Summarization |
| Author | Cheng Siong Chin |
| Published | 05 Mar 2026 |
Use the JSON export at /data/workflows/13900/13900.json as the source template for this automation.
Open n8n, import the downloaded JSON, and review each node before activating the workflow.
Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.
Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.
Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.
Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.
Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.
How It Works This workflow automates end to end code repository governance scanning using a multi agent AI orchestration system. Designed for engineering leads, DevSecOps teams, and CTOs, it replac...
Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.
Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your DevOps, AI Summarization use case.