Connector · Support
Zendesk, in every client’s workflows.
Open a ticket, update a ticket, or start when a ticket is opened, with the client’s own Zendesk account.
- Triggers
- 2start a workflow
- Actions
- 2steps in a workflow
Start a workflow when something happens in ZendeskBeta
By webhook where Zendesk sends one, by checking where it does not. A webhook is checked once a day to see it is still on, and if Zendesk turns it off the alert carries a Reconnect button.
- A ticket is openedWebhookA new ticket, within seconds. Webhooks are made with an admin’s token. The requester’s name and email are not in the event: find the user by the requester ID in a step.
- A ticket is solved (or reaches a status)WebhookA ticket moves to the status you choose, within seconds. Webhooks are made with an admin’s token.
Do it in Zendesk
A step with its own fields: values from the run go in by name, and what Zendesk answers is there for the next step.
- Open a ticketA new ticket from the requester, with the message as its first comment.
- Update a ticketChange a ticket’s status, add a comment, or both, found by id.
Connect the client’s Zendesk
On the client’s page in Thrum: Add credential, type Zendesk API token.
In the client’s Zendesk: Admin Center → Apps and integrations → APIs → Zendesk API → enable Token access → Add API token. The triggers make webhooks, which needs an admin’s email and token.
The key is stored encrypted and bound to that client: another client’s workflow cannot use it, and no template or pack copies it.
Watched like everything else
When Zendesk stops answering or refuses the client’s key, you hear about it, and your client does not.
- A failing request
- Tried 3 times, 5 seconds apart and doubling, only for errors a retry can fix
- A service that asks for a pause
- Given it, up to an hour
- Requests at once, per account
- 2, per worker; the rest wait their turn
- Timeout
- 15 seconds, unless the step sets its own
- Private and internal addresses
- Refused, on every redirect too
- The client’s key
- Encrypted, bound to the client, and kept out of every run record
- A step that keeps failing
- Marks the workflow Degraded and alerts you, not the client
Zendesk and its logo are trademarks of their owner, used here only to say what Thrum works with; no endorsement is implied.
Thrum is cooking.
Get early access and you’ll be among the first in. Early members get a launch perk.