Sync Zendesk tickets with subsequent comments to GitHub issues
Needs changesNeeds changes. This template uses 1 thing(s) that n8n 3.0 removes: Function (legacy). 1 breaking item(s) found. Static check, last run 2026-10-19.
What this workflow does
This workflow has 7 nodes and runs when an HTTP POST request hits its webhook URL. Along the way it connects Zendesk and GitHub.
How it runs
Trigger: When an HTTP POST request hits its webhook URL.
- Get ticket (Zendesk): get
- Determine (Function): runs custom JavaScript (legacy Function node)
- If: checks a condition and branches into true / false
- Create comment on existing issue (GitHub): create comment
- Create issue (GitHub): uses GitHub
- Update ticket (Zendesk): update
Services it uses
Before you upgrade to n8n 3.0
1 thing in this workflow is removed in n8n 3.0. Fix it before you upgrade:
- Function (legacy) in Determine: replace with Code node, mode 'Run Once for All Items'.
Rather not rewrite it? Many of these flows can be rebuilt in Make (free plan).
| Removed in 3.0 | Replace with |
|---|---|
| Function (legacy) Determine | Code node, mode 'Run Once for All Items' |
Nodes used (5)
- Zendesk
n8n-nodes-base.zendesk - If
n8n-nodes-base.if - Function
n8n-nodes-base.function - GitHub
n8n-nodes-base.github - Webhook
n8n-nodes-base.webhook
From the author
This workflow creates a GitHub issue when a new ticket is created in Zendesk. Subsequent comments on the ticket in Zendesk are added as comments to the issue in GitHub. Prerequisites - Zendesk account and Zendesk credentials. - GitHub account and GitHub…