CRM / Finance
Zendesk OAuth
Zendesk OAuth endpoints are built from the customer's Zendesk subdomain, so a fixed generic provider endpoint is insufficient.
Specialised flow
Manual provider setup
Zendesk OAuth endpoints are built from the customer's Zendesk subdomain, so a fixed generic provider endpoint is insufficient.
Required inputs
- Zendesk subdomain
- clientId and clientSecret
- redirectUri
- authorization code and requested scopes
- 01UnderstandReview why this provider needs a specialized setup path.
- 02CollectGather the required provider-specific fields.
- 03Run setupComplete the provider flow outside the generic OAuth form.
- 04ValidateUse the checklist to confirm token and metadata handling.
What this workflow can do
- Manual provider checklist
- Provider-specific inputs
- Generic OAuth form
Before starting
- Zendesk subdomain
- clientId and clientSecret
- redirectUri
- authorization code and requested scopes
Result handling
- Use the checklist to complete provider-specific setup outside the generic form.
- Anonymous OAuth Hub workflows do not store secrets, tokens, or provider payloads.
Troubleshooting
- The OAuth client must be registered by a Zendesk administrator in the target account.
- Authorization, token, and users/me URLs must all use the same customer subdomain.
Provider checklist
- Collect and validate the Zendesk subdomain before constructing endpoints.
- Send the user to the account-specific authorization endpoint.
- Exchange the code at the same account's OAuth token endpoint.
- Verify against /api/v2/users/me.json with the bearer token.