Monday.com to Jira Backlog Harmonizer with Fuzzy Duplicate Detection - n8n Workflow

• Project Management Offices (PMOs) utilizing both Monday.com for intake and Jira for development.


• Software development teams who need a clean, de-duplicated Jira backlog.


• Advanced n8n users looking for complex integration patterns involving custom logic and fuzzy matching.


• Anyone seeking a reliable n8n template for project task management across platforms.

Maintaining consistency between project intake tools (like Monday.com) and engineering backlog tools (like Jira) is critical but often complicated by duplicates, inconsistent data formats, and manual transfers. This specialized n8n workflow solves these problems by providing an automated, intelligent synchronization pipeline. The core value of this n8n automation lies in its custom 'Fuzzy Match' logic, which goes beyond simple exact matches to identify similar-sounding or slightly mistyped issues, ensuring a clean Jira backlog. By leveraging the n8n trigger on Monday.com, data is standardized, checked against the existing Jira environment, and either a new issue is created, or an existing one is updated, completing the loop with immediate feedback logged back to Monday.com.

The process begins immediately when an item is created or updated in Monday.com, activating the specialized n8n trigger, 'Listen for Monday.com Webhook'.

1. Data Normalization: The raw payload is first processed by the 'Normalize Monday Fields' function, an n8n node that standardizes the summary, description, and component data for Jira compatibility.


2. Jira Backlog Query: The n8n workflow then uses the 'Query Jira Backlog' n8n node to retrieve a list of existing issue summaries from Jira, establishing a baseline for comparison.


3. Fuzzy Duplicate Check: The custom JavaScript within the 'Detect Duplicates (Fuzzy Match)' n8n node runs a character-level similarity algorithm. If the new Monday summary has an 80% or greater similarity to any existing Jira summary, the workflow flags it as a duplicate.


4. Decision Gate: The 'Is Duplicate Found?' n8n node directs the flow. If a duplicate is found, the workflow routes to 'Update Jira Issue (Duplicate)'. If it is a new task, it proceeds to 'Create New Jira Issue'.


5. Action and Feedback: For new items, the 'Create New Jira Issue' n8n node adds the task to the Jira backlog. Finally, the 'Update Monday Item (Log Action)' n8n node closes the feedback loop, documenting the successful creation and providing the Jira issue key directly in the original Monday.com item. This comprehensive approach ensures bi-directional visibility.

To set up this powerful n8n workflow, follow these steps:

1. Import the n8n template: Copy the provided JSON code and paste it into your n8n instance using the 'New' -> 'Import from JSON' option.


2. Configure Credentials: You will need valid credentials for the following services:

1. Setup Monday Webhook: The 'Listen for Monday.com Webhook' n8n trigger requires a specific path (e.g., /webhook/76739f12-e0c0-48f8-ac17-6401f012e3a3). Copy the generated webhook URL from the n8n node configuration and paste it into your Monday.com automation settings to trigger this specific n8n workflow upon task creation.


2. Activate: Save the n8n workflow and toggle it to active. Test the flow by creating a new item in the designated Monday.com board.

This n8n workflow relies on several specialized nodes to achieve its intelligent synchronization:

Listen for Monday.com Webhook (n8n trigger):
Function: Serves as the starting n8n trigger, listening for real-time item creation/updates from Monday.com.
Key Configuration: Configured with a unique webhook path to receive data payloads.
Normalize Monday Fields (Function n8n node):
Function: Custom JavaScript used to map unstructured Monday column values into standardized JSON fields (summary, component, severity, description).
Key Configuration: Custom code iterates through column_values to extract and clean data.
Query Jira Backlog (Jira n8n node):
Function: Connects to Jira and executes the getAll operation to retrieve existing issue summaries, essential for the subsequent fuzzy matching.
Detect Duplicates (Fuzzy Match) (Function n8n node):
Function: The core intelligence of this n8n workflow. It uses a custom similarity function to perform fuzzy comparison between the new Monday summary and all Jira summaries. It sets the crucial duplicateFound flag.
Key Configuration: Custom code implements an 80% similarity threshold for matching.
Is Duplicate Found? (If n8n node):
Function: A logical router that directs the flow based on the boolean output of the fuzzy matching node.
Create New Jira Issue (Jira n8n node):
Function: Creates a new Jira issue (Type: Task, Project: Kanban) when no duplicate is detected.
Key Configuration: Uses expressions to pull summary, description, and other fields from the normalized Monday data.
Update Monday Item (Log Action) (Monday.com n8n node):
Function: Executes the final step of the feedback loop, adding an update/comment to the original Monday item, confirming the Jira action.
* Key Configuration: Uses the original mondayItemId and includes dynamic text about the Jira status.