New support tickets move to engineering without manual copy and paste. The flow links Zendesk tickets with Jira issues so teams stay in sync. It fits support teams that escalate bugs and product requests to developers.

A webhook catches new Zendesk tickets. Ticket details are pulled, then a small function checks a Zendesk custom field used to store a Jira issue key. The route then splits. If a key already exists, the flow adds the latest Zendesk comment to the matching Jira issue. If no key exists, it creates a new Jira issue with the ticket subject and a link back to the Zendesk ticket, then writes the Jira issue key into the Zendesk custom field. This creates clear traceability both ways and removes copy and paste steps.

Setup needs Zendesk and Jira accounts, API access, a Jira key custom field in Zendesk, and a webhook that posts to the n8n URL. Update your Jira project and issue type values, and set your Zendesk field ID in the function and update nodes. Expect faster escalations, fewer errors, and a cleaner audit trail. Great for bug triage, incident reports, and feature requests that need developer input.

• Webhook trigger captures new Zendesk tickets on POST events.
• Gets full ticket details to use the subject and ticket ID.
• Function checks a Zendesk custom field to find an existing Jira issue key.
• IF node routes to create a new Jira issue or add a Jira comment.
• Creates a Jira issue with the Zendesk subject and a link back to the ticket.
• Updates the Zendesk ticket by saving the Jira issue key in a custom field.
• Adds a comment to the existing Jira issue using the incoming Zendesk comment.

• Reduce manual escalations from 10 minutes to 1 minute
• Automate 90% of ticket to issue handoffs
• Improve data accuracy by 95% by removing copy and paste
• Connect Zendesk and Jira with live links for clear traceability
• Handle 3 times more escalations without adding staff

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 Zendesk and Jira Software Cloud. See the Tools Required section above for links to create accounts with these services.
3. Open the Webhook node in n8n and copy the Production URL. In your Zendesk Admin Center, create a webhook that sends a JSON POST to this URL when a ticket is created or updated with a comment.
4. In the n8n credentials manager, create a Zendesk credential. Use your Zendesk subdomain, email, and an API token from the Zendesk admin API page. If unsure, double click the Zendesk nodes and use Create new credential, then follow on screen instructions.
5. Create a Jira Software Cloud credential in n8n. Use your Atlassian site domain, email, and an API token from your Atlassian account security page. If unsure, double click the Jira nodes and use Create new credential, then follow on screen instructions.
6. Open the Create issue node and set your Jira project and issue type. Replace the default project and type values with the ones your team uses.
7. Update the description template in the Create issue node so the Zendesk link uses your own subdomain, not the placeholder domain.
8. In Zendesk, create or confirm a custom ticket field to store the Jira issue key. Copy its field ID.
9. Open the Update ticket node and replace the custom field ID with your Zendesk field ID so the Jira key is saved to the right place.
10. Open the Determine function node and set the ISSUE_KEY_FIELD_ID constant to the same Zendesk field ID.
11. Test the create path: make a new Zendesk ticket with no Jira key. Confirm a Jira issue is created and the Jira key appears in the Zendesk ticket.
12. Test the comment path: add a public comment to a ticket that already has a Jira key. Confirm the comment shows up on the linked Jira issue.
13. Troubleshoot as needed: if issue creation fails, check Jira project and permissions; if the update fails, verify the Zendesk field ID and API token; if comments do not post, confirm the webhook event includes the comment and the IF condition is true.