Customer service software and support ticket system
Zendesk currently provides 8 triggers that can start a workflow and 13 actions a workflow can run. Use those building blocks to connect support activity to the full account history and the next internal action.
New ticket in view
Triggers when a new ticket is created in a view
New Ticket
Fires when a new ticket is created (optionally filtered by organization). Requires a Zendesk Trigger with Notify active webhook.
Updated Ticket
Fires when an existing ticket is updated. Requires a Zendesk Trigger with Notify active webhook.
Tag Added to Ticket
Fires when a ticket update includes the specified tag. Requires a Zendesk Trigger with Notify active webhook.
New Organization
Fires when a new organization record is created. Uses Zendesk event webhook (no Trigger needed).
New User
Fires when a new user is created. Uses Zendesk event webhook (no Trigger needed).
New Suspended Ticket
Fires when a ticket is suspended. Requires a Zendesk Trigger with Notify active webhook. Suspended tickets auto-delete after 14 days.
New Action on Ticket
Fires when the specified ticket updates. Requires a Zendesk Trigger with Notify active webhook.
Create Ticket
Create a new ticket in Zendesk.
Update Ticket
Modify ticket fields or status via API call.
Add Tag to Ticket
Apply one or more tags to a ticket.
Add Comment to Ticket
Append a public/private comment to a ticket.
Create Organization
Create a new organization record.
Update Organization
Update existing organization fields.
Create User
Add a new user to the Zendesk instance.
Delete User
Remove a user and associated records from the account.
Find Organization(s)
Search organizations by name, domain, external ID, or other criteria.
Find Ticket(s)
Search tickets by ID, field, or content.
Find User(s)
Search users by email, name, role, or other criteria.
Update User
Update existing user fields.
Custom API Call
Make a custom API call to a specific endpoint
These recipes are generated from the triggers, actions, and categories currently available for this piece. Use them as starting points, then choose the exact fields, conditions, and records your workflow should update.
Start from a supported Zendesk event, then create or update the appropriate CRM, project, or custom record with the source context preserved.
Starts with
New ticket in view
Finishes with
Create or update a Coherence record
Use a change in Coherence to run a supported Zendesk action, so the next step follows the record instead of relying on someone to copy it.
Starts with
A Coherence record or workflow changes
Finishes with
Create Ticket
Combine Zendesk with another integration and Coherence records to connect support activity to the full account history and the next internal action.
Starts with
New ticket in view
Finishes with
Create Ticket, then preserve the outcome in Coherence
The exact authentication fields depend on Zendesk. The workflow structure stays straightforward:
Authorize the Zendesk account and permissions the workflow needs.
Select one of the current triggers or actions listed above and map its fields.
Run a small test, inspect the result in both systems, and only then enable the workflow.
Explore apps that share a category with Zendesk or provide a complementary trigger or action.
Zendesk currently provides 8 triggers that can start a workflow and 13 actions a workflow can run. Use those building blocks to connect support activity to the full account history and the next internal action.
Zendesk currently lists 8 triggers and 13 actions in the integration catalog. The supported list is refreshed from the pieces available in Coherence, so review the capability names on this page before building a workflow.
Yes. A workflow can combine supported Zendesk triggers or actions with Coherence records and other available integrations. The exact flow depends on the authentication, permissions, triggers, and actions exposed by each connected app.
The listed triggers and actions are designed for visual workflows. If the pre-built integration does not expose a capability you need, HTTP and webhook steps can cover APIs that your team is authorized to use.
Start automating in minutes. No credit card required.
