Skip to content

The moment it happens

Sync monday.com items to Jira without duplicates

New and updated monday.com items show up as Jira issues, and changes update the same issue instead of creating a new one.

Runs
The moment it happens
Apps
Jira, monday.com
AI
Not needed
Access
read+write on both

Send this to your assistant

Create a ClickRuntime automation: when an item is created or changes on my Product board in monday.com, create a matching Jira issue in project APP, or update it if one exists, and write the Jira key back to the item.

Paste it into your assistant. It tells you what it will send or change before it runs live.

First time? Adding ClickRuntime to your assistant takes about two minutes.

Why use it

Why teams use this automation

When product managers plan in monday.com and engineers work in Jira, the two drift apart. Titles change on one side but not the other, and simple syncing tools create a new ticket for every edit, filling Jira with duplicates.

Keeping a link between each item and its issue means every change lands on the right ticket. Both teams see the same names and statuses, and Jira stays clean.

What you get out of it

  • One item, one issue

    Each monday.com item is linked to a single Jira issue, so edits never create duplicates.

  • Changes arrive instantly

    monday.com notifies ClickRuntime the moment an item changes, so Jira is updated within seconds.

  • Both teams in their own tool

    Product stays in monday.com and engineering stays in Jira, with nobody copying updates between them.

  • Easy to trace

    The Jira key on each item links the two, making it easy to jump between tools.

How it works

What happens, step by step

  1. monday.com tells ClickRuntime whenever an item on your board is created or changed.

  2. ClickRuntime looks up whether that item is already linked to a Jira issue.

  3. If it is, the existing issue's title and status are updated; if not, a new issue is created.

  4. New issue keys are written back to the monday.com item and remembered, so each item only ever has one issue.

Before it runs live

  • Connect Jira
  • Connect monday.com
  • Paste your automation's link into the other app's webhook settings

What you get

RunsThe moment it happens
Sync monday.com items to Jira without duplicatesjust nowSucceeded
Jira · APPAPP-217 updated: "Northwind SSO login" moved to In Progress (from monday.com status Working on it).

Build your own

Need it to work differently?

This template is a starting point. Copy the prompt and change it, or describe a different automation from scratch, with your own conditions, more apps or an AI step. Your assistant writes it, tests it and runs it on ClickRuntime.
  • Your own rules

    Conditions, thresholds, filters and exceptions, written the way you'd explain them to a colleague.

  • Any number of apps

    One automation can read from one app and update several others. Over 248 apps are ready, and anything with an API works too.

  • AI where it helps

    Summaries, classification, extraction and drafts use ClickRuntime's built-in AI, with no extra key.

  • On a schedule or on each event

    Runs as often as every 5 minutes, or the moment an app sends an event, and keeps track of what it already handled.

Changes you can ask for

  • Act only on the items that match your own rules, and skip the rest
  • Add an AI step, for example to summarize, sort or draft a reply
  • Add another app, for example also send it to Slack
  • Combine it with other Jira and monday.com steps into one automation

Under the hood

The code that runs this automation

This is the Python script that runs each time the automation starts. Your AI assistant writes it for you when you send the prompt, and you allow each step in your assistant. To change how the automation works, describe the change to your assistant and it updates the script for you. For every function it can use, see the script reference.
sync_monday_com_items_to_jira_without_duplicates.pyexample
from clickruntime import on_event, credentials, http, state

BOARD = 1234567890
STATUS_TO_TRANSITION = {"Working on it": "21", "Done": "31"}

def monday(query, **variables):
    resp = http.post("https://api.monday.com/v2", json={"query": query, "variables": variables},
                     headers={"Authorization": credentials.secret("MONDAY_API_TOKEN"), "API-Version": "2024-10"})
    resp.raise_for_status()
    return resp.json()["data"]

JIRA_URL = "https://api.atlassian.com/ex/jira/your-cloud-id/rest/api/3"

def jira(method, path, **kw):
    resp = http.request(method, JIRA_URL + path, headers={"Authorization": "Bearer " + credentials.connection("jira", "work")}, **kw)
    resp.raise_for_status()
    return resp.json() if resp.content else None

@on_event
def handle(event):
    body = event.json or {}
    if "challenge" in body:
        return {"challenge": body["challenge"]}
    e = body.get("event") or {}
    item_id = str(e.get("pulseId", ""))
    if not item_id:
        return {"synced": False}
    key = state.get(f"item:{item_id}")
    name = monday("query ($i: [ID!]) { items(ids: $i) { name } }", i=[item_id])["items"][0]["name"]
    if key:
        jira("PUT", f"/issue/{key}", json={"fields": {"summary": name[:250]}})
        label = (e.get("value") or {}).get("label", {}).get("text")
        if label in STATUS_TO_TRANSITION:
            jira("POST", f"/issue/{key}/transitions", json={"transition": {"id": STATUS_TO_TRANSITION[label]}})
    else:
        key = jira("POST", "/issue", json={"fields": {"project": {"key": "APP"}, "issuetype": {"name": "Task"}, "summary": name[:250]}})["key"]
        state.set(f"item:{item_id}", key)
        monday("mutation ($b: ID!, $i: ID!, $v: String!) { change_simple_column_value(board_id: $b, item_id: $i, column_id: \"jira_key\", value: $v) { id } }",
               b=BOARD, i=item_id, v=key)
    return {"item": item_id, "issue": key}

FAQ

Common questions

Which changes are synced?
New items and changes to the name and status. Other columns can be mapped as well.
How is a monday.com status matched to Jira?
Through a small mapping you set, such as Working on it to In Progress. Statuses without a mapping are left alone.
How do I connect the trigger?
Add the automation's trigger link as a webhook in your monday.com board's integrations, for item created and column changed.
What permissions does it need?
read+write on both. Nothing else in your accounts is used.
Does it need AI?
No. It runs without AI, so it doesn't use your plan's AI allowance.
How many runs does it use?
One run for each event the app sends.
Can I change how it works?
Yes. Describe the change to your AI assistant, for example a different schedule, channel or filter. It updates the automation, tests it and tells you what changed.

Set up “Sync monday.com items to Jira without duplicates” from your assistant

Copy the prompt above, or connect your assistant first. Free plan, no credit card.