Connect Zendesk to FastHook
Automate Zendesk support tickets, comments, users and organizations with FastHook Workflows.
Choose from 14 Triggers and 19 Actions.
OAuth availability
Connect using OAuth and your native Zendesk subdomain. Customer connections are pending Zendesk Global OAuth approval; the development client supports only the FastHook development account.
Connect your account
- When customer OAuth becomes available, choose New source → Provider app → Zendesk in FastHook Sources.
- Enter your native Zendesk subdomain and authorize FastHook as an administrator. Choose a ticket event; FastHook manages the webhook.
- Add Zendesk Actions to a Workflow, select resources, map input fields and test the result.
- Activate the Workflow when you are ready to process ticket events.
Example automations
- Create a support ticket from an incoming form response.
- Send a Slack notification when a ticket becomes urgent.
- Add an internal ticket note after a CRM task completes.
Triggers
- Ticket Created
- Ticket Status Changed
- Ticket Comment Added
- Ticket Agent Assignment Changed
- Ticket Priority Changed
- Ticket Tags Changed
- Ticket Subject Changed
- Ticket Group Assignment Changed
- Ticket Organization Changed
- Ticket Requester Changed
- Ticket Soft Deleted
- Ticket Undeleted
- Any Zendesk Event
- Custom Zendesk Events
Actions
- Get Current User
- List Tickets
- Get Ticket
- Create Ticket
- Update Ticket
- Add Ticket Comment
- List Ticket Comments
- Add Ticket Tags
- Remove Ticket Tags
- Search
- List Users
- Get User
- Create User
- Update User
- List Organizations
- Get Organization
- Create Organization
- Update Organization
- Custom API Request
Working with Zendesk
A Zendesk administrator must connect the account to manage webhooks. Actions follow the connected user’s Zendesk permissions.
FastHook groups selected ticket events into one managed webhook per account, verifies Zendesk HMAC signatures and deduplicates repeated deliveries.
The exact original webhook payload is archived before processing. Ticket-event schemas describe an open common envelope based on official examples; event-specific fields remain flexible.
Action output schemas are converted from the pinned official Zendesk Support OpenAPI document. Custom API responses have a flexible body.
List operations use cursor pagination with at most 100 records per page. Map meta.after_cursor into the next call’s cursor; search uses numbered pages and Zendesk’s result limits.
Add Ticket Comment defaults to an internal note. Select Public comment to send a public reply, which may notify the requester through your Zendesk business rules.
Global OAuth approval is required before customers can connect their own Zendesk accounts. A local client is limited to its development account.
Zendesk reference · Explore Zendesk integrations · Zendesk API documentation