Sync Jira issues with subsequent comments to Notion database

Sync Jira issues and their comments to a Notion database, ensuring real-time updates and streamlined project management. This automated workflow captures issue creation, updates, and deletions, enhancing collaboration and organization by keeping all relevant information in one place.

7/8/2025
10 nodes
Complex
24manualcomplexnotionsticky notejiratriggerlogicroutingconditional
Categories:
Complex WorkflowManual Triggered
Integrations:
NotionSticky NoteJiraTrigger

Target Audience

This workflow is ideal for:
- Project Managers who need to keep track of Jira issues and their statuses in Notion.
- Software Developers who want to automate the synchronization of issue updates between Jira and Notion.
- Team Leads looking for a streamlined way to manage project tasks and updates without manual entry.
- Product Owners who require real-time updates on issue progress and status changes for better decision-making.

Problem Solved

This workflow addresses the challenge of manually tracking Jira issues and their comments in Notion. It automates the process of creating, updating, and deleting issues in Notion based on changes in Jira, ensuring that all relevant information is consistently up-to-date in the Notion database. This reduces the risk of human error and saves valuable time for teams managing multiple projects.

Workflow Steps

  • Trigger Event: The workflow starts when an issue is created, updated, or deleted in Jira via the Jira Trigger node.
    2. Lookup Table: It uses a Lookup Table to map Jira issue statuses to their corresponding values for Notion.
    3. Conditional Logic: An IF node checks if the event is an issue creation. If true, it creates a new page in the Notion database.
    4. Custom Filters: If the event is an update or deletion, the workflow generates custom filters to locate the corresponding Notion page.
    5. Find Database Page: The Find Database Page node retrieves the relevant Notion page based on the filters created.
    6. Switch Node: The Switch node determines the next action based on whether the issue was updated or deleted.
    7. Update Issue: If the issue was updated, the workflow updates the existing Notion page with the new details.
    8. Delete Issue: If the issue was deleted, the workflow archives the corresponding Notion page to maintain organization.

    • Customization Guide

    Users can customize this workflow by:
    - Modifying the Lookup Table: Adjust the status mappings in the Lookup Table to match their specific Jira statuses and Notion requirements.
    - Changing the Notion Database ID: Update the databaseId in the Create Database Page and Find Database Page nodes to point to a different Notion database.
    - Adding Additional Properties: Include more properties in the Create database page and Update issue nodes to capture additional information as needed.
    - Adjusting Trigger Events: Modify the events in the On issues created/updated/deleted node to include or exclude specific Jira events based on user preferences.