Integration reference

Zendesk Trigger and Action reference

React to support ticket events and manage tickets, comments, users and organizations in FastHook Workflows.

Authentication

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.

• Trigger account type: oauth2; reconnect by oauth.
• Action connection type: oauth2; available modes: Connected Zendesk account.

Create or reuse the account from a Trigger or Action dialog, or manage it under Settings → Connected accounts. See Authentication and permissions for scopes and access diagnostics, or Connected accounts for reuse, reconnect, revocation, and credential rotation.

Scopes and permissions

Base Trigger authorization requests: read, write.

Operation-specific requirements appear in the tables below. Custom event selections can add scopes dynamically, so the current Trigger or Action dialog remains authoritative for the exact consent request.

Use Zendesk as a Trigger

The current provider manifest contains 14 available Trigger definitions. Representative definitions include:

• Ticket Created
• Ticket Status Changed
• Ticket Comment Added
• Ticket Priority Changed

Choose the narrowest event definition that fits the Workflow. Configure provider-specific resource and event filters in the Source dialog before adding broader Workflow Filters.

Use Zendesk Actions

The current Action manifest contains 19 operations. Representative Actions include:

• Create Ticket
• Update Ticket
• Add Ticket Comment
• Create User

The Action editor reads its required permissions, fields, remote resource pickers, output schema, and rate limit from the provider manifest. Available fields can change with the selected operation and authentication mode.

Build a Workflow

1. Create a Source using a Zendesk Trigger definition.
2. Create a Workflow with that Source as its Trigger.
3. Add the required Zendesk Action and select the connected account.
4. Map Trigger or earlier-Step data into the Action fields with the field picker.
5. Add a Filter, Paths, Delay, or Transformation when the route needs it.
6. Activate the Workflow, produce a controlled event, and verify the run in Audit and in Zendesk.

Troubleshooting Zendesk

The account is missing or cannot be selected

Confirm the active FastHook team, provider, account status, and authentication mode. A disabled or revoked account cannot execute an Action.

A resource picker is empty

Verify that the connected provider identity can access the resource itself. OAuth consent does not add workspace, repository, channel, drive, project, base, or record permissions.

The editor asks for additional scopes

Reconnect the same account from the affected Trigger or Action so FastHook can request its current manifest scopes. Then reopen the editor and select the resource again.

An active Workflow returns 401, 403, or a permission error

Compare the selected operation’s access requirements below with the account recorded in Audit. Check provider-side membership and object access before repeating the Action.

The provider returns 429 or a temporary 5xx

Inspect the Step attempt and retryability in Audit. FastHook can retry temporary failures, but provider quotas and idempotency rules still apply.

Provider-specific checks

• 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.

Next

• Explore Zendesk integrations
• Trigger configuration
• Action configuration
• Data mapping
• Error handling
• Authentication and permissions
• All automation integrations