Zendesk

Connect Zendesk to surface every automation, trigger, AI macro, and installed app operating against your support tickets. The OAuth connector polls the Zendesk Support REST API on a 15-minute cadence and records each automation + integration as an observed agent.

What gets observed

  • Automations + triggers (with conditions + actions).
  • AI macros and macro-suggestion activity.
  • Installed third-party apps (their authoring + last-event timestamps).
  • Audit log events (admin changes, role updates, app installs).
  • Ticket-side effects from automations (close, transfer, tag) tagged with the rule id that fired.

Ticket content itself is not stored — Trefur captures the metadata envelope around each automated action. For per-prompt fidelity on the Advanced AI add-on, route Zendesk's outbound model traffic through the collector LLM proxy.

Setup

  1. Sign in to app.trefur.com as an account owner or admin.
  2. Open Integrations → Zendesk → Connect.
  3. Enter your Zendesk subdomain (e.g. acme.zendesk.com) and click Continue. [Screenshot: Trefur dashboard, Integrations → Zendesk subdomain prompt]
  4. You're bounced through Zendesk's OAuth consent screen. Approve the requested scopes. [Screenshot: Zendesk consent screen]
  5. On success Trefur stores a refresh token in the credential vault and kicks off an instant scan. The first inventory normally completes in under 60 seconds.

OAuth scopes requested

ScopeWhat it grants
readRead access to tickets, automations, macros, apps, and audit events.
triggers:readRead access to trigger configuration.

Troubleshooting

SymptomFix
The OAuth consent screen won't load or errors out.Double-check the subdomain you entered (it must be your real Zendesk subdomain, without https://). Trefur owns the OAuth application and its redirect, so there is nothing to register on your side. If it still fails, an account owner may need to allow third-party OAuth access for your account.
Audit log events not showing up.The audit-log API requires a Zendesk Enterprise plan. Connector still works on lower tiers — you simply see triggers + macros + automations without audit events.
AI macros marked as inactive.Advanced AI must be enabled on the account for the AI-macro endpoints to return data. Without it the connector still inventories regular macros + triggers.

Back to all integrations.