Keep Jira issues and a Notion database aligned without manual updates. Great for product, operations, and project teams that plan in Notion but execute work in Jira. New issues create pages, changes update fields, and deletions archive pages for clean reporting.

An app event from Jira starts the flow on every create, update, or delete. An IF check routes new issues to create a Notion database page with the summary, issue key, and issue ID. For updates and deletes, a code step builds a Notion JSON filter, then a Notion search finds the matching page. A Switch step sends updates to a Notion update and sends deletions to archive. A lookup table maps Jira status to a Notion select value so status names stay consistent across tools.

You need a Notion database with Title, Status, Issue Key, and Issue ID fields, plus connected Jira and Notion credentials in n8n Cloud. Expect less double entry, fewer status errors, and faster reporting. This setup is ideal when engineers live in Jira and stakeholders track progress in Notion. Update the status mapping to match your Jira workflow and paste your Notion database ID into the Notion nodes.

• Jira app event trigger listens for issue created, updated, and deleted events
• IF node routes new issues to create a Notion database page
• Code node builds a Notion JSON filter to find the matching page for updates and deletes
• Notion get all with JSON filter locates the exact page by issue key or ID
• Switch node sends updated issues to a Notion update and deleted issues to archive
• Lookup table maps Jira status to a Notion select option for clean status names
• Notion create, update, and archive actions keep the database in sync without losing history

• Reduce manual updates from hours each week to a few minutes by syncing changes automatically
• Eliminate double data entry between Jira and Notion for issue status and titles
• Improve data accuracy by removing copy and paste mistakes on key fields
• Connect Jira and Notion in real time so teams see the same status everywhere
• Handle hundreds of issues per week without extra work as volume grows

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 Jira Software Cloud and Notion. See the Tools Required section above for links to create accounts with these services.
3. Open the Jira trigger node and create a new credential. In the 'Credential to connect with' dropdown, click 'Create new credential' and follow the on screen instructions to connect your Jira site and allow issue events.
4. Open any Notion node and create a Notion credential. In the 'Credential to connect with' dropdown, click 'Create new credential' and follow the on screen steps. Make sure the Notion integration is shared with your target database.
5. In Notion, prepare a database with properties: Title as a title field, Status as a select field, Issue Key as rich text, and Issue ID as number. Copy the database ID from the Notion URL.
6. Paste the Notion database ID into the Create, Find, and Update Notion nodes so all actions point to the same database.
7. Edit the Lookup table code node. Map your Jira status IDs or names to the exact Notion Status options used in your database.
8. Open the Create custom Notion filters code node. Confirm the property names in the filter match your Notion fields for Issue Key or Issue ID. Adjust if your field names are different.
9. Activate the workflow in n8n so the Jira app event webhook registers and starts listening.
10. Test create: make a new issue in Jira. Check that a new Notion page appears with the correct summary, key, and ID.
11. Test update: change the issue status or title in Jira. Confirm the Notion page updates the Title and Status fields.
12. Test delete: delete or archive the Jira issue. Verify the matching Notion page is archived, not removed, so history stays intact.
13. Troubleshoot: if pages are not found, verify the Notion database ID and property names. If status does not update, check the lookup mapping and that the Notion select option exists. Review the n8n execution log for any node errors.