Review GitHub PR security with DeepSeek and Gmail alerts

by Divyanshu Gupta ✓ · 46 views · created 2026-08-07 · SecOps, AI Summarization

What this workflow does

This AI workflow has 16 nodes and runs on Github events (pull request). Along the way it connects GitHub, DeepSeek Chat Model and Gmail.

How it runs

Trigger: On Github events (pull request).

1. 2. Filter: Opened/Synchronize Only (If): checks a condition and branches into true / false
2. 3. Fetch PR Diff (GitHub): get diff (pull request)
3. 4. Format Diff for AI (Code): runs custom JavaScript code
4. 5. AI Security Code Review (AI Agent): runs an AI agent, with model: AI Model (DeepSeek); output parser: Output Schema (Verdict, Issues, Summary)
5. 6. Post Commit Status Check (HTTP Request): calls an HTTP API (POST)
6. 7. Post Summary Comment on PR (GitHub): create comment
7. 8. Check: Any Issues Found (If): checks a condition and branches into true / false
8. 9. Map Issues to Diff Positions (Code): runs custom JavaScript code
9. 11. Route by Verdict (Switch): routes items into 3 branches
10. 10. Post Inline Comments on Flagged Lines (HTTP Request): calls an HTTP API (POST)

…plus 3 more steps. See the full node list below.

Services it uses

GitHubDeepSeek Chat ModelGmail

Before you upgrade to n8n 3.0

Nodes used (10)

• Github Triggern8n-nodes-base.githubTrigger
• Ifn8n-nodes-base.if
• GitHubn8n-nodes-base.github
• AI Agent@n8n/n8n-nodes-langchain.agent
• DeepSeek Chat Model@n8n/n8n-nodes-langchain.lmChatDeepSeek
• Structured Output Parser@n8n/n8n-nodes-langchain.outputParserStructured
• Switchn8n-nodes-base.switch
• Gmailn8n-nodes-base.gmail
• HTTP Requestn8n-nodes-base.httpRequest
• Coden8n-nodes-base.code

From the author

Quick overview Most teams don't have a security reviewer on every PR. This workflow gives you one: it reads the diff, catches hardcoded secrets and risky code, posts a real GitHub status check, comments inline on the exact flagged line, and emails the…

View the original on n8n.io → Check your own copy