Zendesk

Token auth is Basic, as the user. Ticket JSON paths were not re-fetched; preview before charting.

What you can track

Tickets created and solved, backlog, and satisfaction, once test_job shows the fields. This playbook does not name a JSON path it did not re-read. Do not assume tickets[].created_at until the preview prints it.

Credential

API token access, enabled in Admin Center → Apps and integrations → APIs → Zendesk API. The token acts as the user. Use an agent with a light role. Zendesk wants Basic auth of [email protected]/token:TOKEN, base64-encoded. Store the encoded string, not the raw token.

Host: your-company.zendesk.com. Suggested name: ZENDESK_AUTH. Header: Authorization: Basic {{secret:ZENDESK_AUTH}}.

Where to get it

The path above, and Security and auth.

tlly job

Start with a GET the preview can show, then set extract from the keys it prints. Do not schedule a guessed path. A typical first preview (path unverified):

{"series":"zendesk_tickets","cron":"0 7 * * *","request":{"url":"https://your-company.zendesk.com/api/v2/tickets.json?page[size]=100","headers":{"Authorization":"Basic {{secret:ZENDESK_AUTH}}"}},"extract":{"format":"json","items":"tickets","date":"created_at","aggregate":"count"}}

If the preview’s top-level keys differ, change items and date. Cursor paging (after or next_page) is not followed.

Gotchas

The token can do whatever that user can. Keep the user read-mostly.
Ticket comments and user emails are personal data. Chart counts, not text. tlly will refuse to store long text, but you should not request it.
Rate limits were not re-read. Daily is enough.

Alert ideas

Red when the open backlog (once you have a real count) is above the ceiling. Yellow when created-today is far above solved-today.

Verification

Auth steps match the members-area Zendesk guide and the security-and-auth doc it links. The tickets URL and tickets / created_at paths in the sample job are unverified. Confirm with test_job and edit the spec to match the body.