Skip to main content

Automation flow from Notion to GitHub with email notifications

Workflow preview

Workflow preview
100%
Automation flow from Notion to GitHub with email notifications preview
Open on n8n.io

Important notice

This workflow is provided as-is. Please review and test before using in production.

1. Workflow Overview

This automation allows you to track feature requests in Notion, create GitHub issues automatically, and notify your team via email based on issue status. It's ideal for technical and functional tea...

Best for

  • Project Management automation workflows
  • intermediate n8n builders looking for reusable templates

Tools used

n8n-nodes-base.notion, n8n-nodes-base.github, n8n-nodes-base.set, n8n-nodes-base.scheduletrigger, n8n-nodes-base.switch, n8n-nodes-base.gmail, n8n-nodes-base.aggregate, n8n-nodes-base.stickynote

Source and attribution

This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Fady Bekkar.

Original n8n.io source

1.1 Workflow description

Title
Automation flow from Notion to GitHub with email notifications
Workflow name
Automation flow from Notion to GitHub with email notifications

This automation allows you to track feature requests in Notion, create GitHub issues automatically, and notify your team via email based on issue status. It's ideal for technical and functional teams who collaborate on project delivery using Notion and GitHub.

๐Ÿ”น SECTION 1: Detect and Sort Issues from Notion

Combining: Schedule Trigger + Notion Database + Field Mapping + Status Routing

โฐ 1. Schedule Trigger

๐Ÿ”ง Node Type: Schedule Trigger (you can use a webhook trigger if you are on Notion paid plan)

๐Ÿ’ฌ Description: Triggers the workflow every X minutes to check for new or updated Notion database pages.

๐Ÿ“‘ 2. Get Many Database Pages (Notion)

๐Ÿ”ง Node Type: Notion โ†’ Get All Database Pages

๐Ÿ“‹ What it does: Fetches all rows (pages) from a Notion database that represents tasks or feature requests.

โœ๏ธ 3. Sort Issues Fields ๐Ÿ”ง Node Type: Set

๐Ÿ“‹ Goal: Restructures or cleans data fields such as Title, Status, Labels, and Repository.

๐Ÿ”€ 4. Switch: Issue Status Decision

๐Ÿ”ง Node Type: Switch

๐ŸŽฏ What it does: Separates logic based on the Status of the Notion item:

If status is "To develop" โ†’ proceed to create issue

Else โ†’ send notification to the team

๐Ÿ”น SECTION 2: GitHub Issue Creation (IF "To develop")

Combining: GitHub Node + Notion Update

๐Ÿ™ 5. Create an Issue (GitHub)

๐Ÿ”ง Node Type: GitHub โ†’ Create Issue

โš™๏ธ What it does: Creates a new issue on the GitHub repo defined in the Notion row.

๐Ÿ“ฅ Inputs: Uses dynamic fields: Title, Description, Labels, Repository.

๐Ÿงฉ 6. Set Status and Issue URL (Notion Update)

๐Ÿ”ง Node Type: Notion โ†’ Update Database Page

๐Ÿง  Role: Updates the status of the issue in Notion to In progress and stores the created GitHub Issue URL.

๐Ÿ”น SECTION 3: Notify Team on Already In-Progress Items (IF NOT "To develop")

Combining: Notion Users + Filtering + Email Grouping + Gmail

๐Ÿ‘ฅ 7. Get Many Users (Notion Users)

๐Ÿ”ง Node Type: Notion โ†’ Get All Users

๐Ÿ“ฅ What it does: Retrieves the list of team members (to be notified).

๐Ÿง  8. Map Notion Users

๐Ÿ”ง Node Type: Set

๐Ÿ“‹ Role: Maps and formats data for each user (e.g., Name, Email, Role).

๐Ÿงน 9. Exclude Bot

๐Ÿ”ง Node Type: Switch

๐Ÿšซ What it does: Excludes automation/bot users (e.g., notifications@noreply).

๐Ÿงฎ 10. Group Recipients

๐Ÿ”ง Node Type: Aggregate

๐ŸŽฏ Goal: Collects all user emails into a single array to send one email to all recipients.

๐Ÿ“ฌ 11. Send a Message (Gmail)

๐Ÿ”ง Node Type: Gmail โ†’ Send Email

1.2 Logical Blocks

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.

2. Block-by-Block Analysis

Block 1 - Get many database pages

Type / Role
n8n-nodes-base.notion - notion
Config choices
Version 2.2

Block 2 - Create an issue

Type / Role
n8n-nodes-base.github - github
Config choices
Version 1.1

Block 3 - Sort Issues Fields

Type / Role
n8n-nodes-base.set - set
Config choices
Version 3.4

Block 4 - Schedule Trigger

Type / Role
n8n-nodes-base.scheduleTrigger - scheduleTrigger
Config choices
Version 1.2

Block 5 - Get many users

Type / Role
n8n-nodes-base.notion - notion
Config choices
Version 2.2

Block 6 - Map Notion Users

Type / Role
n8n-nodes-base.set - set
Config choices
Version 3.4

Block 7 - Set Status and Issue URL

Type / Role
n8n-nodes-base.notion - notion
Config choices
Version 2.2

Block 8 - Switch

Type / Role
n8n-nodes-base.switch - switch
Config choices
Version 3.2

Block 9 - Exclude Bot

Type / Role
n8n-nodes-base.switch - switch
Config choices
Version 3.2

Block 10 - Send a message

Type / Role
n8n-nodes-base.gmail - gmail
Config choices
Version 2.1

Block 11 - Group Recipients

Type / Role
n8n-nodes-base.aggregate - aggregate
Config choices
Version 1

Block 12 - Sticky Note1

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 13 - Sticky Note2

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 14 - Sticky Note3

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

3. Summary Table

Workflow Automation flow from Notion to GitHub with email notifications
Complexity intermediate
Nodes 14
Categories Project Management
Author Fady Bekkar
Published 11 Jul 2025

4. Reproducing the Workflow from Scratch

  1. 1. Download the workflow JSON

    Use the JSON export at /data/workflows/5889/5889.json as the source template for this automation.

  2. 2. Import the template into n8n

    Open n8n, import the downloaded JSON, and review each node before activating the workflow.

  3. 3. Configure credentials and variables

    Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.

  4. 4. Test with sample data

    Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.

  5. 5. Activate and monitor

    Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.

5. General Notes & Resources

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.

Frequently asked questions

What does Automation flow from Notion to GitHub with email notifications do?

This automation allows you to track feature requests in Notion, create GitHub issues automatically, and notify your team via email based on issue status. It's ideal for technical and functional tea...

What do I need before importing this workflow?

Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.

Can I customize this workflow?

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 Project Management use case.