Automation flow from Notion to GitHub with email notifications

Created by

Fady Bekkar

Last update

Last update 20 hours ago

🔹 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