Zendesk is not a native Threetone connector. This guide prepares an external integration and action contract; it does not enable a working support automation.
Prepare the ticket action
You need a Zendesk administrator, an approved test ticket, and an application owner responsible for OAuth and revocation.1
Use the current authentication guidance
Zendesk’s security and authentication reference recommends OAuth and marks API tokens deprecated. Integrations distributed to multiple customers require global OAuth. Do not ask customers to hand over private account credentials. Review the token’s scope and the acting user’s access.
2
Limit the ticket context
Bind the Zendesk instance and exact ticket ID. Return only the subject, state, and permitted excerpts needed for the task. Exclude unrelated requester details and attachments. A ticket ID supplied in a message is not proof that its sender can read that ticket.
3
Confirm visibility before a write
Show the target ticket, final text, and whether the comment is internal or public. Review notification and status effects. If the request times out, inspect the ticket before retrying so the same comment is not added twice. Report rejected or incomplete updates honestly.
Frequently asked questions
Should a new integration start with an API token?
Should a new integration start with an API token?
Use Zendesk’s current OAuth guidance. The provider marks API tokens deprecated, and distributing an integration has additional global OAuth requirements.
Can the agent decide whether a comment is public?
Can the agent decide whether a comment is public?
Make visibility an explicit reviewed decision and enforce it in your service. Do not infer it from generated prose or a generic send action.