Jira + Zendesk: support tickets and engineering work joined up.
Create Jira issues from Zendesk tickets, notify Zendesk requester when engineering ships, and sync ticket-issue state for full traceability.
Workflows fire when something happens in Zendesk.
- Ticket AssignedWebhook
- Ticket CommentedWebhook
- New TicketWebhook
- Ticket SolvedWebhook
- Ticket UpdatedWebhook
Workflows do something in Jira, instantly.
- Add CommentAPI
- Add WatcherAPI
- Assign IssueAPI
- Create IssueAPI
- Delete IssueAPI
- Get IssueAPI
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 Jira.
6 Zendesk triggers wired to 17 Jira actions. Most-used pairing: Ticket Assigned → Add Comment.
Or fire it the other way around.
6 Jira triggers wired to 17 Zendesk actions downstream.
See Jira → Zendesk →Common Zendesk → Jira 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 Jira in five steps.
No code, no glue, no half-day setup. Each step is one click.
- 1ConnectAuthorize Zendesk and Jira
Open Tiny Command, authorize Zendesk and Jira 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 Jira action
Drop the Jira → Add Comment action below it. Map fields from the Zendesk payload into the Jira inputs.
jira.add-comment - 5PublishPublish and forget
Hit Publish. Tiny Command runs it in production from second one. Watch the run-log fill up.
Questions about Zendesk + Jira.
How do I file a Zendesk ticket as a Jira issue?
Can I notify Zendesk requester when the Jira issue closes?
How do I add Zendesk customer tier to Jira issue?
Can I auto-link Zendesk to existing Jira issues for the same bug?
How do I avoid noise from low-priority Zendesk tickets?
Can I post Jira PR progress back to Zendesk?
Other apps that pair well with Zendesk.
Wire Zendesk to Jira in 2 minutes.
Free tier available. No credit card. No onboarding call.
