Monitor GitHub repo access and push events with GitHub and Slack alerts

by RamS ✓ · 124 views · created 2025-12-31 · SecOps

What this workflow does

This workflow has 12 nodes and runs on a schedule (every hour). Along the way it connects Slack. It also calls api.github.com over HTTP.

How it runs

Trigger: On a schedule (every hour).

1. Github Events (HTTP) (HTTP Request): calls api.github.com
2. Filter Member Events (Code): runs custom JavaScript code
3. Check Whitelist (Data table): get
4. Switch: routes items into 3 branches
5. MemberEvent (If): checks a condition and branches into true / false
6. PublicEvent (If): checks a condition and branches into true / false
7. PushEvent (If): checks a condition and branches into true / false
8. Member Event Alert (Slack): uses Slack
9. Public Event Alert (Slack): uses Slack
10. Push Event Alert (Slack): uses Slack

Services it uses

Slack

HTTP calls to: api.github.com

Before you upgrade to n8n 3.0

Nodes used (8)

• Schedule Triggern8n-nodes-base.scheduleTrigger
• Coden8n-nodes-base.code
• Data tablen8n-nodes-base.dataTable
• HTTP Requestn8n-nodes-base.httpRequest
• Switchn8n-nodes-base.switch
• Ifn8n-nodes-base.if
• Slackn8n-nodes-base.slack
• No Operation, do nothingn8n-nodes-base.noOp

From the author

Monitor GitHub Repositories for Unauthorized Actions How it works: This workflow monitors GitHub for high-risk activities to ensure that only authorized users can modify the repository. It periodically polls GitHub for events such as PushEvent, MemberEvent,…

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