New GitHub issues in Slack
Every new issue in your repo is posted to your team's Slack channel.
How it works
Trigger: GitHub — issue opened
- Receive the new issue event from GitHub.
- Post the title, author, labels and link to #dev in Slack.
Diagram
Trigger App Logic
Build it
Pick your tool — same automation, step by step.
Copy and paste straight into an n8n canvas (Ctrl+V), or download and use Import from File. Then connect your own credentials and replace every YOUR_… placeholder.
Show code (131 lines)
{
"name": "New GitHub issues in Slack (Flowngn)",
"nodes": [
{
"parameters": {
"content": "## New GitHub issues in Slack\nEvery new issue in your repo is posted to your team's Slack channel.\n\n**Setup**\n1. Open each node and connect your own credentials.\n2. Replace every YOUR_… placeholder.\n3. Test once, then activate.\n\nFree template from Flowngn",
"height": 260,
"width": 340
},
"id": "26067c04-e776-42a7-a37a-b6a76afcba64",
"name": "Setup notes",
"type": "n8n-nodes-base.stickyNote",
"typeVersion": 1,
"position": [
-420,
-60
]
},
{
"parameters": {
"owner": {
"__rl": true,
"value": "YOUR_GITHUB_USER",
"mode": "name"
},
"repository": {
"__rl": true,
"value": "YOUR_REPO",
"mode": "name"
},
"events": [
"issues"
],
"options": {}
},
"id": "26067c04-e776-42a7-a37a-b6a76afcba64",
"name": "Issue event",
"type": "n8n-nodes-base.githubTrigger",
"typeVersion": 1,
"position": [
0,
0
],
"webhookId": "26067c04-e776-42a7-a37a-b6a76afcba64"
},
{
"parameters": {
"conditions": {
"options": {
"caseSensitive": true,
"leftValue": "",
"typeValidation": "loose"
},
"conditions": [
{
"id": "c1",
"leftValue": "={{ $json.body.action }}",
"rightValue": "opened",
"operator": {
"type": "string",
"operation": "equals"
}
}
],
"combinator": "and"
},
"options": {}
},
"id": "26067c04-e776-42a7-a37a-b6a76afcba64",
"name": "Newly opened?",
"type": "n8n-nodes-base.if",
"typeVersion": 2.2,
"position": [
300,
0
]
},
{
"parameters": {
"select": "channel",
"channelId": {
"__rl": true,
"value": "#dev",
"mode": "name"
},
"text": "=🐛 New issue #{{ $json.body.issue.number }}: {{ $json.body.issue.title }}\nby {{ $json.body.issue.user.login }} · {{ $json.body.issue.labels.map(l => l.name).join(', ') }}\n{{ $json.body.issue.html_url }}",
"otherOptions": {}
},
"id": "26067c04-e776-42a7-a37a-b6a76afcba64",
"name": "Post to #dev",
"type": "n8n-nodes-base.slack",
"typeVersion": 2.2,
"position": [
600,
0
]
}
],
"connections": {
"Issue event": {
"main": [
[
{
"node": "Newly opened?",
"type": "main",
"index": 0
}
]
]
},
"Newly opened?": {
"main": [
[
{
"node": "Post to #dev",
"type": "main",
"index": 0
}
]
]
}
},
"pinData": {},
"settings": {
"executionOrder": "v1"
},
"meta": {
"templateCredsSetupCompleted": false
},
"tags": []
}In Make, create a new scenario and add these modules in order:
- GitHub › Watch Events (issues)
- Filter on the next route: “Newly opened?”
- If yesSlack › Create a Message
- Every module run uses Make operations — the free plan includes a monthly quota.
- Module and step names can differ slightly as Make and Zapier update their apps.
In Zapier, create a new Zap and add these steps in order:
- GitHub — New Issue
- Filter by Zapier: “Newly opened?”
- If yesSlack — Send Channel Message
- Zaps with more than two steps need a paid Zapier plan.
- Webhooks, Filters/Paths and Code by Zapier are premium features on some Zapier plans.
- Module and step names can differ slightly as Make and Zapier update their apps.
Tips
- Filter by label (e.g. "bug") to keep the channel quiet.
Related flows
Developer & ITEasy
Announce GitHub releases in Slack
When you publish a release, your team or community sees the notes instantly.
GitHub → Slack1h/mo
Developer & ITEasy
Remind the team about pull requests waiting for review
Every workday, post pull requests that have waited 2+ days for review to your dev channel.
GitHub → Slack2h/mo
Developer & ITMedium
Changelog from merged pull requests
Each merged pull request is added to a Notion changelog automatically.
GitHub → Notion2h/mo