GitHub + Zendesk: support tickets and engineering work, joined up.
Create GitHub issues from Zendesk tickets, and notify the original Zendesk requester when the engineering fix ships. Closes the loop between support and code.
Workflows fire when something happens in Zendesk.
- Ticket AssignedWebhook
- Ticket CommentedWebhook
- New TicketWebhook
- Ticket SolvedWebhook
- Ticket UpdatedWebhook
Workflows do something in GitHub, instantly.
- Add LabelsAPI
- Create CommentAPI
- Create IssueAPI
- Create Pull RequestAPI
- Submit PR ReviewAPI
- Create ReleaseAPI
Pick the way that fits your stack.
Pair pages are mirrored. Each direction gets its own dedicated page.
When something happens in Zendesk, do it in GitHub.
6 Zendesk triggers wired to 23 GitHub actions. Most-used pairing: Ticket Assigned → Add Labels.
Or fire it the other way around.
1 GitHub triggers wired to 17 Zendesk actions downstream.
See GitHub → Zendesk →Common Zendesk → GitHub workflows.
Pick a pairing to set it up in two minutes. Each one is a fully editable recipe.
Fires when a ticket is assigned (or reassigned) to an agent in Zendesk. Use to ping the assignee, start an SLA clock, or audit workload balance.
Fires when a ticket is assigned (or reassigned) to an agent in Zendesk. Use to ping the assignee, start an SLA clock, or audit workload balance.
Fires when a ticket is assigned (or reassigned) to an agent in Zendesk. Use to ping the assignee, start an SLA clock, or audit workload balance.
Fires when a ticket is assigned (or reassigned) to an agent in Zendesk. Use to ping the assignee, start an SLA clock, or audit workload balance.
Fires when a comment (public or internal) is added to a Zendesk ticket. Common use: notify Slack of customer replies, log activity, or mirror conversations into a CRM.
Fires when a comment (public or internal) is added to a Zendesk ticket. Common use: notify Slack of customer replies, log activity, or mirror conversations into a CRM.
Fires when a comment (public or internal) is added to a Zendesk ticket. Common use: notify Slack of customer replies, log activity, or mirror conversations into a CRM.
Fires when a comment (public or internal) is added to a Zendesk ticket. Common use: notify Slack of customer replies, log activity, or mirror conversations into a CRM.
Fires when a new support ticket is created in Zendesk, across any channel (email, web form, chat, API, social). The standard inbound hook for AI triage and routing.
Connect Zendesk and GitHub in five steps.
No code, no glue, no half-day setup. Each step is one click.
- 1ConnectAuthorize Zendesk and GitHub
Open Tiny Command, authorize Zendesk and GitHub once each. Both connections are available to every workflow on your account.
- 2TriggerPick a Zendesk trigger
Drop the Zendesk → Ticket Assigned trigger onto the canvas. Tiny Command auto-registers the webhook.
POST /v1/webhooks/zendesk.trigger-ticket-assigned - 3TransformAdd a filter or AI step
Optionally add a Filter node ("subject contains URGENT") or an AI step ("classify intent") between trigger and action.
- 4ActionAdd the GitHub action
Drop the GitHub → Add Labels action below it. Map fields from the Zendesk payload into the GitHub inputs.
github.add-labels-to-issue - 5PublishPublish and forget
Hit Publish. Tiny Command runs it in production from second one. Watch the run-log fill up.
Questions about Zendesk + GitHub.
How do I file a Zendesk ticket as a GitHub issue?
Can I notify the Zendesk requester when the GitHub issue closes?
How do I add Zendesk customer-tier context to the GitHub issue?
Can I auto-link Zendesk tickets to existing GitHub issues for the same bug?
How do I avoid noise from low-priority Zendesk tickets?
Can I post GitHub PR progress back into the Zendesk ticket?
Other apps that pair well with Zendesk.
Wire Zendesk to GitHub in 2 minutes.
Free tier available. No credit card. No onboarding call.
