Ticket Solved: Zendesk trigger

Anatomy

What this trigger looks like in a workflow.

Drop it on the canvas. Configure a couple of fields. Publish.

In the builder

Trigger

Ticket Solved

When the matching event happens

on ticket solvednew ticket solvedwatch for ticket solvedwhen a ticket is solved in zendeskwhen ticket solved

What this trigger returns

for the curious

You don’t need to read this. Tiny Command auto-maps every field into the visual picker so downstream nodes can pull values by clicking. We show it here for power users who want to know what’s on the wire.

{
  "event": "ticket.solved",
  "subject": "Help needed",
  "ticket_id": 12345
}

Output shape

Fields available to downstream nodes.

Every field below can be referenced by name in any action or filter that comes after this trigger.

Field	Type	Example
event	string	"ticket.solved"
subject	string	"Help needed"
ticket_id	number	12345

FAQ

Questions about Ticket Solved.

How does the Ticket Solved trigger work in Zendesk?

Fires when a ticket is marked solved in Zendesk. Common use: kick off CSAT surveys, log resolution to CRM, or run an AI quality-of-resolution check.

Is the Ticket Solved trigger real-time?

Yes. Ticket Solved uses webhooks or push subscriptions, not polling. Your workflow fires within seconds of the event happening in Zendesk.

What data does Ticket Solved return?

The full event payload from Zendesk. The output shape table on this page lists every field, its type, and an example value so you can map fields into downstream nodes.

Can I filter Ticket Solved so only some events start a workflow?

Yes. Add a Filter node right after the trigger and match on any field, whether that's subject, sender, status, or anything else in the payload. Workflows only continue when the filter passes.

Do I need Zendesk admin permissions to use Ticket Solved?

For most Zendesk accounts a standard user can authorize the trigger. Some Zendesk plans require an admin to enable third-party webhooks. Check Zendesk's docs if the trigger fails to register.

More triggers

Other Zendesk triggers.

Trigger

Ticket Assigned

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.

Trigger

Ticket Commented

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.

Trigger

New Ticket

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.

Trigger

Ticket Updated

Fires whenever any field on a Zendesk ticket changes (status, priority, assignee, group, tags, custom fields). Combine with field filters to react only to the changes you care about.

Trigger

New User

Fires when a new user (end-user or agent) is created in Zendesk. Use to enrich the user, sync into your CRM, or auto-add to an organization.

How do I trigger when a Zendesk ticket is solved?

What this trigger looks like in a workflow.

Fields available to downstream nodes.

Drop these actions after Ticket Solved.

Questions about Ticket Solved.

Other Zendesk triggers.

Build a workflow on this trigger.