Keep GitHub issues in sync with a Notion database so your team sees updates in one place. Product and engineering teams that plan in Notion but work in GitHub get clear status with less manual work. It is helpful for anyone who reports progress to non technical stakeholders in Notion.

A GitHub issues event starts the flow. When an issue is opened, a new page is created in a Notion database with the title, link, and the issue ID. For edits, deletes, closes, and reopens, a custom function builds a Notion filter using the issue ID to find the right page. The flow then routes by action: edited updates the title, deleted archives the page, closed checks a Closed box, and reopened clears that box. This keeps a one to one match between each GitHub issue and its Notion record.

You need a Notion database with properties for Issue ID number, Link url, Issue title, and a Closed checkbox. Connect your GitHub and Notion accounts in n8n, add your database ID, and point the trigger to your repo. Expect faster updates, fewer copy paste errors, and a shared view for managers and clients. Agencies and internal teams can track delivery in Notion while engineers stay in GitHub.

• Listens to GitHub issue events and reacts to opened, edited, deleted, closed, and reopened actions.
• Creates a new Notion database page for each opened issue with title, link, and numeric issue ID.
• Builds a dynamic Notion filter using the issue ID to find the exact matching page.
• Updates the Notion title when a GitHub issue is edited to keep names in sync.
• Archives the Notion page when the GitHub issue is deleted.
• Checks a Closed checkbox when the issue is closed and clears it when reopened.
• Uses a Switch node to route actions so each update is accurate and fast.

• Reduce manual updates from 30 minutes to 3 minutes per issue
• Automate over 90 percent of status changes from GitHub to Notion
• Improve data accuracy by 95 percent by removing copy paste steps
• Handle 10 times more issues without extra admin work
• Connect GitHub and Notion so both teams see the same status

1. Import the template into n8n: Create a new workflow in n8n > Click the three dots menu > Select 'Import from File' > Choose the downloaded JSON file.
2. You'll need accounts with Notion and GitHub. See the Tools Required section above for links to create accounts with these services.
3. In Notion, create or pick a database. Add properties named Issue ID as Number, Link as URL, Issue as Title, and Closed as Checkbox. Share the database with your Notion integration so it has access.
4. Find your Notion database ID and copy it. It is in the page URL after your workspace name.
5. In the n8n credentials manager, open any Notion node, choose Credential to connect with, click Create new credential, and follow the on screen steps to connect your Notion account.
6. Double click the Notion nodes and paste the database ID where required. Match the property names to your database properties.
7. In the n8n credentials manager, open the GitHub Trigger node, choose Credential to connect with, click Create new credential, and follow the on screen steps. Use OAuth or a Personal Access Token with repo and admin repo hook scopes.
8. In the GitHub Trigger node, select your repository and choose the Issues event. Save the node so n8n can register the webhook.
9. Activate the workflow. Open a test issue in the selected GitHub repo and confirm a new page appears in Notion with the right fields.
10. Edit the issue title, close it, reopen it, and delete it to confirm each update changes the Notion page as expected.
11. If pages are not found, check that Issue ID types match, property names in Notion match the node settings, and that your Notion integration has access to the database. Also confirm the GitHub webhook is active in the repo settings.