Skip to content
Per-pair page

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.

Trigger app
GitHub as the trigger

Workflows fire when something happens in GitHub.

Action app
Zendesk as the action

Workflows do something in Zendesk, instantly.

See all 17 actions →
Both directions

Pick the way that fits your stack.

Pair pages are mirrored. Each direction gets its own dedicated page.

GitHubZendesk

When something happens in GitHub, do it in Zendesk.

1 GitHub triggers wired to 17 Zendesk actions. Most-used pairing: New GitHub EventAdd Comment to Ticket.

ZendeskGitHub

Or fire it the other way around.

6 Zendesk triggers wired to 23 GitHub actions downstream.

See ZendeskGitHub
Popular pairings

Common GitHub → Zendesk workflows.

Pick a pairing to set it up in two minutes. Each one is a fully editable recipe.

Showing 4 of 17 combinations
How it works

Connect GitHub and Zendesk in five steps.

No code, no glue, no half-day setup. Each step is one click.

  1. 1
    Connect
    Authorize GitHub and Zendesk

    Open Tiny Command, authorize GitHub and Zendesk once each. Both connections are available to every workflow on your account.

  2. 2
    Trigger
    Pick a GitHub trigger

    Drop the GitHub → New GitHub Event trigger onto the canvas. Tiny Command auto-registers the webhook.

    POST /v1/webhooks/github.trigger-event
  3. 3
    Transform
    Add a filter or AI step

    Optionally add a Filter node ("subject contains URGENT") or an AI step ("classify intent") between trigger and action.

  4. 4
    Action
    Add the Zendesk action

    Drop the Zendesk → Add Comment to Ticket action below it. Map fields from the GitHub payload into the Zendesk inputs.

    zendesk.add-comment-to-ticket
  5. 5
    Publish
    Publish and forget

    Hit Publish. Tiny Command runs it in production from second one. Watch the run-log fill up.

FAQ

Questions about GitHub + Zendesk.

How do I file a Zendesk ticket as a GitHub issue?
Zendesk Ticket tagged "needs-engineering" → GitHub Create Issue with body = ticket conversation + customer context. Save GitHub issue URL in Zendesk ticket custom field for round-trip tracking.
Can I notify the Zendesk requester when the GitHub issue closes?
Yes. GitHub Issue Closed → look up linked Zendesk ticket → Zendesk Add Comment (public=true) with "fix shipped, check your version". Or send a follow-up email via Gmail.
How do I add Zendesk customer-tier context to the GitHub issue?
Get User from Zendesk for the requester. Pass plan tier, monthly spend, and organization into the GitHub issue body and as labels (e.g., "tier:enterprise"). Helps triage prioritize.
Can I auto-link Zendesk tickets to existing GitHub issues for the same bug?
Yes. AI checks the new Zendesk ticket against existing open GitHub issues. If match found, add the Zendesk ticket URL as a comment on the existing issue instead of creating a duplicate.
How do I avoid noise from low-priority Zendesk tickets?
Filter the trigger on Zendesk priority (Urgent/High only) or by tag. Low-priority tickets stay in Zendesk. Or batch into a weekly digest of low-priority issues for engineering to review in bulk.
Can I post GitHub PR progress back into the Zendesk ticket?
Yes. GitHub PR linked to the Zendesk-spawned issue progresses → Zendesk Add Comment (public=false) with "fix in review", "fix merged", "deploying". Support agent sees status without leaving Zendesk.
Related

Other apps that pair well with GitHub.


Wire GitHub to Zendesk in 2 minutes.

Free tier available. No credit card. No onboarding call.