Skip to main content
Triggr creates, lists and searches Zendesk tickets, reads ticket comments, and lists organizations and views.

Set up Zendesk

You need a Zendesk admin account.
1

Turn on API token access

In Admin Center, go to Apps and integrations > APIs > API configuration, select Allow API token access and click Save. See Zendesk’s Turning on and off API access.
2

Create an API token

Go to APIs > API tokens, click Add API token, enter a Description such as Triggr and click Save. Copy the token before you click Save again; Zendesk won’t show it in full afterwards. See Zendesk’s Managing API token access.
3

Choose the user Triggr acts as

Triggr sends the token with a user’s email address and sees only what that user can. Use an admin, or an agent with access to the tickets, organizations and views your workflows need; a dedicated user such as triggr@yourcompany.com makes Triggr’s changes easy to spot.

Connect it in Triggr

The Base Configuration serves workflows that don’t run for a client.
1

Open the configuration

Go to Integrations > Zendesk and click Configure on the Base Configuration card.
The Base Configuration card with Status Not Configured, Admin Consent Not Required and a Configure button.
2

Enter the token, address and user

Enter the token as ApiKey, your Zendesk address with nothing after the host as BaseURL (such as https://yourcompany.zendesk.com), and the user’s email as EmailAddress. Click Save Configuration.
The Zendesk configuration window with ApiKey, BaseURL and EmailAddress fields, an Allow insecure TLS switch under Advanced, and a Save Configuration button.

Set up each client

Per-client integrations never fall back to the Base Configuration, so a client’s Zendesk steps fail until it’s configured. Click Configure on each client’s row and fill in all three fields: your own Zendesk details, or a token from the client’s own Zendesk account.
The Per-Client Configuration card listing Acme Corp and Globex, each Not Configured with Admin Consent Not Required and a Configure button.

Use Zendesk in workflows

  • Create Ticket takes a ticket object in jsonBody, in the shape of Zendesk’s Create Ticket endpoint. Only comment is required; add requester_id or organization_id as needed.
  • List Tickets For Organization takes an organizationId from Get Organizations.
  • Global Search takes Zendesk search syntax, such as type:ticket status:open, with page and perPage (up to 100).
  • Actions with pageSize use cursor pagination: pass meta.after_cursor as afterCursor while meta.has_more is true.

Troubleshooting

Configure the client as described in Set up each client.
Check ApiKey is the full token, EmailAddress is a verified user in the same account, the token is still active (Zendesk deletes tokens unused for 30 days) and Allow API token access is still on.
The EmailAddress user can’t see what the action asks for. Use an admin, or widen the user’s role.
BaseURL must be https:// plus the host only. Triggr adds /api/v2 itself.
Create a new one, paste it into ApiKey in every configuration that uses it, then deactivate the old one under APIs > API tokens.