Zendesk

What you need

Three things, all from one screen in Zendesk, and no command line.

Zendesk has deprecated the older email and API token pair, so use this if you can. The old fields are still here for accounts that have not moved yet.

Either way Worclaude reads Zendesk and only reads. Nothing it does can change a ticket, add a comment or alter a queue.

1. Subdomain

The first part of your Zendesk address. If your team opens https://acme.zendesk.com, this is acme. Pasting the whole address is fine too.

2 and 3. Client ID and secret

In Zendesk:

1. Admin Center → Apps and integrations → APIs → Zendesk API.
2. Open the OAuth Clients tab and press Add OAuth client.
3. Fill in:
   • Client name — Worclaude, or anything you will recognise later.
   • Redirect URLs — Zendesk insists on something here even though this kind of client never sends anyone anywhere. Put your own Zendesk address, https://acme.zendesk.com, and forget about it.
4. Press Save. Zendesk shows the secret once, in a box you cannot reopen. Copy it now.
5. Copy the Unique identifier from the same page. That is the Client ID.

Paste both into the fields here. That is the whole setup.

Whose tickets can it see? Requests made this way are attributed to whoever created the OAuth client, and see exactly what that person sees. If you create it as an admin, the source can read the whole queue. If results ever look thinner than you expect, ask the chat who it is connected as.

The older way: email and API token

Deprecated by Zendesk, and still working for now.

1. Admin Center → Apps and integrations → Zendesk API.
2. Turn Token access on, if it is off.
3. Add API token, name it worclaude, and copy it once.

The email is the agent this source reads as. An API token is not a password; if the field rejects a password, that is why.