Zendesk meets Jira for tickets that stay in sync
Your support team closes tickets faster when engineering has clean, complete context. But the reality is usually messy: someone copies a Zendesk description into Jira, misses a key comment, and now two systems drift apart.
This Zendesk Jira sync hits Support Leads first, because they’re the ones chasing updates. A Product Owner feels it when priorities get scrambled. And an Ops Manager sees the cost when “quick handoffs” turn into daily back-and-forth.
This workflow creates the Jira issue automatically, stores the Jira key back on the Zendesk ticket, then mirrors every new Zendesk comment into Jira so engineering always sees the latest thread.
How This Automation Works
Here’s the complete workflow you’ll be setting up:
n8n Workflow Template: Zendesk meets Jira for tickets that stay in sync
flowchart LR
subgraph sg0["Flow 1"]
direction LR
n0@{ icon: "mdi:swap-horizontal", form: "rounded", label: "IF", pos: "b", h: 48 }
n1["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/jira.svg' width='40' height='40' /></div><br/>Create issue"]
n2["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/zendesk.svg' width='40' height='40' /></div><br/>Update ticket"]
n3["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/zendesk.svg' width='40' height='40' /></div><br/>Get ticket"]
n4@{ icon: "mdi:code-braces", form: "rounded", label: "Determine", pos: "b", h: 48 }
n5["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/jira.svg' width='40' height='40' /></div><br/>Create comment to existing i.."]
n6["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/webhook.dark.svg' width='40' height='40' /></div><br/>On new Zendesk ticket"]
n0 --> n5
n0 --> n1
n4 --> n0
n3 --> n4
n1 --> n2
n6 --> n3
end
%% Styling
classDef trigger fill:#e8f5e9,stroke:#388e3c,stroke-width:2px
classDef ai fill:#e3f2fd,stroke:#1976d2,stroke-width:2px
classDef aiModel fill:#e8eaf6,stroke:#3f51b5,stroke-width:2px
classDef decision fill:#fff8e1,stroke:#f9a825,stroke-width:2px
classDef database fill:#fce4ec,stroke:#c2185b,stroke-width:2px
classDef api fill:#fff3e0,stroke:#e65100,stroke-width:2px
classDef code fill:#f3e5f5,stroke:#7b1fa2,stroke-width:2px
classDef disabled stroke-dasharray: 5 5,opacity: 0.5
class n0 decision
class n6 api
class n4 code
classDef customIcon fill:none,stroke:none
class n1,n2,n3,n5,n6 customIcon
Why This Matters: Ticket Handoffs Break Without a Single Source of Truth
When Zendesk is “where the customer story lives” and Jira is “where work gets done,” you end up translating the same problem twice. The first copy is annoying. The second copy (every follow-up comment, screenshot, reproduction step, or “FYI it’s happening again”) is where things quietly fall apart. A ticket looks resolved in Zendesk while the Jira issue is missing the latest detail. Or engineering fixed the bug, but support never sees the update because it’s trapped in Jira. Multiply that by a busy week and you have a coordination tax nobody volunteered for.
The friction compounds. Here’s where it breaks down in real teams.
- Someone has to create Jira issues manually, so urgent tickets wait in a queue that isn’t visible to customers.
- Comments get lost between tools, which means engineers work with incomplete reproduction steps.
- The Jira issue link isn’t reliably saved back to Zendesk, so support can’t check status without asking around.
- Two separate timelines form, and nobody is sure which one is the “real” version of the conversation.
What You’ll Build: Zendesk Tickets That Automatically Create and Update Jira Issues
This automation starts the moment a Zendesk ticket event hits your n8n webhook. The workflow fetches the ticket details, checks if the ticket already has a Jira Issue Key stored in a custom Zendesk field, and then makes a clean decision: create a new Jira issue or append a comment to the existing one. If it’s a brand-new ticket, n8n generates the Jira issue in the project you choose, then immediately writes the new Jira key back into the Zendesk ticket so the link is permanently attached. When a customer (or agent) adds more detail later, the workflow pulls the Jira key from that Zendesk field and adds the new comment into Jira, keeping engineering’s thread current without anyone copy-pasting.
The workflow begins with a Zendesk webhook trigger. Then it enriches the payload by fetching the full ticket, extracts the Jira key if one exists, and routes down the right path. Jira gets the issue creation and ongoing comments, while Zendesk stays the “front desk” with the Jira key stored for quick visibility.
What You’re Building
| What Gets Automated | What You’ll Achieve |
|---|---|
|
|
Expected Results
Say your team escalates 20 Zendesk tickets a week into Jira, and each ticket averages 3 meaningful follow-up comments. Manually, you’re doing roughly 4 copy/paste moments per ticket (the initial handoff plus the comments). If each one takes about 5 minutes once you find the right issue, that’s around 6–7 hours a week of pure coordination. With this workflow, the “after” is basically zero manual handoff time: the webhook triggers instantly, and the updates flow in while your team keeps working.
Before You Start
- n8n instance (try n8n Cloud free)
- Self-hosting option if you prefer (Hostinger works well)
- Zendesk for tickets and triggers via webhook.
- Jira to create issues and append comments.
- Zendesk custom field (create “Jira Issue Key” in Admin Center)
Skill level: Beginner. You’ll connect credentials, create one Zendesk webhook + trigger, and select the right Jira project.
Want someone to build this for you? Talk to an automation expert (free 15-minute consultation).
Step by Step
A Zendesk webhook fires. When a ticket is created (and later, when comments come in), Zendesk sends the ticket ID and latest comment to your n8n webhook URL.
The workflow pulls full ticket context. n8n fetches the ticket details from Zendesk so it can read your custom field that stores the Jira Issue Key and grab the latest comment content.
A simple check decides what happens next. If the Jira Issue Key field is empty, n8n creates a new Jira issue in your chosen project. If the key exists, it treats the ticket as already linked and prepares an update instead.
Jira and Zendesk stay tied together. For new tickets, the workflow writes the Jira issue key back into the Zendesk ticket field. For existing links, it appends the new Zendesk comment into Jira so engineering sees the same thread support sees.
You can easily modify which Zendesk tickets sync (by status, form, organization, or tags) to match your escalation rules. See the full implementation guide below for customization options.
Step-by-Step Implementation Guide
Step 1: Configure the Webhook Trigger
Set up the inbound Zendesk webhook that initiates the workflow when a ticket is updated.
- Add the Zendesk Ticket Webhook node as the trigger.
- Set the HTTP Method to
POST. - Set the Path to
d596c0c6-7377-4a17-9ed5-6ee953f072b9. - In Zendesk, configure your webhook to send ticket events to the n8n webhook URL generated by this node.
Step 2: Connect Zendesk Ticket Retrieval
Fetch full ticket details based on the incoming webhook payload.
- Add the Fetch Ticket Details node and connect it after Zendesk Ticket Webhook.
- Set the Operation to
get. - Set the ID to
{{$node["Zendesk Ticket Webhook"].json["body"]["id"]}}. - Credential Required: Connect your zendeskApi credentials.
body.id; otherwise Fetch Ticket Details will fail to load the ticket.Step 3: Set Up the Processing Logic
Extract any existing Jira issue key and branch the flow based on whether it exists.
- Add the Extract Jira Key function node connected after Fetch Ticket Details.
- Paste the provided function code to locate the custom field ID
6689934837021and outputJira issue key. - Add the Branch on Key node after Extract Jira Key.
- In Branch on Key, set the string condition to isNotEmpty with Value 1 as
{{$node["Extract Jira Key"].json["Jira issue key"]}}.
Step 4: Configure Jira and Zendesk Actions
When a Jira key exists, append a comment. When it doesn’t, create a Jira issue and update Zendesk with the new key.
- Connect Branch on Key to Append Jira Comment on the “true” output.
- In Append Jira Comment, set Resource to
issueComment, Issue Key to{{$node["Extract Jira Key"].json["Jira issue key"]}}, and Comment to{{$node["Zendesk Ticket Webhook"].json["body"]["comment"]}}. - Credential Required: Connect your jiraSoftwareCloudApi credentials in Append Jira Comment.
- Connect Branch on Key to Generate Jira Issue on the “false” output.
- In Generate Jira Issue, set Project to
10000, Issue Type to10003, and Summary to{{$node["Fetch Ticket Details"].json["subject"]}}. - Set Additional Fields → Description to
=See Zendesk issue at: https://n8n.zendesk.com/agent/tickets/{{$node["Fetch Ticket Details"].json["id"]}}. - Credential Required: Connect your jiraSoftwareCloudApi credentials in Generate Jira Issue.
- Connect Generate Jira Issue to Modify Zendesk Ticket.
- In Modify Zendesk Ticket, set Operation to
updateand ID to{{$node["Zendesk Ticket Webhook"].json["body"]["id"]}}. - Set Update Fields → Custom Fields to ID
6689934837021and value{{$node["Generate Jira Issue"].json["key"]}}. - Credential Required: Connect your zendeskApi credentials in Modify Zendesk Ticket.
Step 5: Test and Activate Your Workflow
Validate the end-to-end flow using a real Zendesk ticket update and then activate the workflow for production use.
- Click Execute Workflow in n8n to enter test mode.
- Trigger a Zendesk ticket update that sends a webhook payload to Zendesk Ticket Webhook.
- Verify that Fetch Ticket Details retrieves the ticket and Extract Jira Key outputs the correct key.
- If the key exists, confirm Append Jira Comment adds the comment to the correct Jira issue.
- If the key is missing, confirm Generate Jira Issue creates an issue and Modify Zendesk Ticket writes the Jira key back to Zendesk.
- When the test is successful, toggle the workflow to Active to enable production execution.
Troubleshooting Tips
- Zendesk credentials and webhooks can fail due to missing admin permissions. If it stops triggering, check Admin Center > Webhooks and the ticket trigger conditions first.
- Jira issue creation can fail if the project requires specific fields (like Issue Type, Component, or Priority). Confirm the required fields in Jira project settings, then map them in the “Generate Jira Issue” node.
- The “Jira Issue Key” field must be the exact Zendesk custom field you created. If comments keep creating new Jira issues, it usually means the workflow is writing the key to the wrong field or not writing it at all.
Quick Answers
About 30 minutes if your Zendesk and Jira accounts are ready.
No. You’ll connect Zendesk and Jira credentials, then choose the right fields and project settings in n8n.
Yes. n8n has a free self-hosted option and a free trial on n8n Cloud. Cloud plans start at $20/month for higher volume. You’ll also need to factor in any Zendesk/Jira plan limitations your accounts already have.
Two options: n8n Cloud (managed, easiest setup) or self-hosting on a VPS. For self-hosting, Hostinger VPS is affordable and handles n8n well. Self-hosting gives you unlimited executions but requires basic server management.
Yes, and you probably should. You can adjust the logic in the “Branch on Key” check to only create Jira issues for specific ticket forms, tags, or groups, and keep everything else in Zendesk. Common tweaks include mapping Jira priority from Zendesk urgency, changing the Jira issue type (Bug vs Task), and syncing only public comments so internal notes don’t leak into engineering threads.
Usually it’s a permissions issue or an expired credential in n8n. Reconnect Zendesk in n8n, then double-check your Zendesk webhook and trigger are still active and pointing to the correct n8n webhook URL. If the webhook fires but no Jira issue gets created, the ticket fetch step often fails because the API token doesn’t have access to the right subdomain or resources. Also worth checking: the payload body in Zendesk includes the ticket ID, because that’s what the workflow uses to fetch the full ticket.
Plenty for most small teams: hundreds of ticket events a day is normal on a modest setup, as long as your Zendesk and Jira APIs aren’t rate-limiting you.
Often, yes, because this flow has branching logic and a “lookup then decide” pattern that gets awkward (and expensive) in simpler tools. n8n handles the “create once, then update forever” behavior cleanly, and self-hosting removes execution anxiety if you have lots of comments. Zapier or Make can still work if you only need a basic “new ticket creates issue” rule and you don’t care about comment sync. The moment you want reliable two-way context, n8n is usually the calmer option. Talk to an automation expert if you want help picking the simplest path.
Once this is live, handoffs stop being a daily project. The workflow keeps Zendesk and Jira aligned so your team can focus on solving the issue, not relaying it.
Need Help Setting This Up?
Our automation experts can build and customize this workflow for your specific needs. Free 15-minute consultation—no commitment required.
