Turn new support tickets into developer tasks without copy paste. When a ticket appears in Zendesk, a linked issue is created or updated in GitHub. Support teams and engineers stay aligned with less effort.

A webhook receives the ticket event and pulls the full record from Zendesk. A small function checks a custom field that stores the GitHub issue number. If a number is found, the flow posts a comment to that GitHub issue using the latest ticket message. If no number exists, it opens a new GitHub issue with the ticket subject and then writes the new issue number back to the Zendesk custom field for future syncing.

You will need a Zendesk webhook that sends the ticket id and comment to the n8n URL, a Zendesk custom field to hold the GitHub issue number, and a GitHub token with repo access. After setup, handoff time drops, errors shrink, and fixes move faster. Use it for bug reports, incident follow ups, and product feedback that starts in support and must go to engineering.

• Webhook listens for new ticket events sent from Zendesk.
• Retrieves full ticket details by id for reliable context.
• Reads a Zendesk custom field to get or store the GitHub issue number.
• IF logic routes either to create a new issue or add a comment to an existing one.
• Creates a GitHub issue using the ticket subject for a clear title.
• Updates the Zendesk ticket custom field with the created issue number.
• Posts a comment to the matching GitHub issue with the latest ticket message.

• Reduce manual handoff from 15 minutes to 1 minute
• Automate 100% of ticket to issue creation and updates
• Improve data accuracy by 90% by removing copy paste
• Connect Zendesk and GitHub in one simple flow
• Handle more tickets per agent without extra steps

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 GitHub. See the Tools Required section above for links to create accounts with these services.
3. In n8n, open the Webhook node and copy the Production URL. Keep the workflow active so the URL can receive requests.
4. In your Zendesk admin center, create a webhook that points to the n8n Webhook Production URL. Use POST and send JSON.
5. In Zendesk, create two triggers: one for Ticket is created and one for Ticket comment is added. Set both to notify the webhook and include the ticket id and the latest comment in the JSON payload.
6. Create a custom ticket field in Zendesk to store the GitHub issue number. Note its field id from the field settings.
7. In n8n, double click the Get ticket and Update ticket nodes. In the 'Credential to connect with' dropdown, click 'Create new credential' for Zendesk, then follow the on screen steps to add your subdomain, email, and API token.
8. Double click the Create issue and Create comment nodes. In the 'Credential to connect with' dropdown, click 'Create new credential' for GitHub and add a personal access token with repo scope. Save the credential.
9. Set the GitHub owner and repository in both GitHub nodes to match your repo. Ensure the token has access to that repo.
10. Open the Determine function node and replace the ISSUE_KEY_FIELD_ID with your Zendesk custom field id so the flow can read and write the GitHub issue number.
11. Turn on the workflow, then create a test ticket in Zendesk. Confirm a new GitHub issue appears and the Zendesk custom field updates with the issue number.
12. Add a new public comment to the same ticket. Verify the comment is posted to the linked GitHub issue. If something fails, check n8n execution logs, confirm the Zendesk webhook payload includes the ticket id, verify credentials, and make sure the field id and repo settings are correct.