CRM / Finance
Freshdesk OAuth
Freshworks OAuth varies by product, account domain, and regional authorization host and needs a dedicated endpoint resolver.
Manual / specialised flowProvider docs
What this workflow can do
- Manual provider checklist
- Provider-specific inputs
- Generic OAuth form
Before starting
- Freshdesk account domain and Freshworks region
- clientId and clientSecret
- redirectUri and product scopes
- authorization code
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.
- 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.
Specialised flow
Manual provider setup
Freshworks OAuth varies by product, account domain, and regional authorization host and needs a dedicated endpoint resolver.
Required inputs
- Freshdesk account domain and Freshworks region
- clientId and clientSecret
- redirectUri and product scopes
- authorization code
Troubleshooting
- Use the regional Freshworks authorization server associated with the customer account.
- Do not mix Freshdesk account domains, regions, or credentials from different app registrations.
Provider checklist
- Identify the account region and construct the matching OAuth endpoints.
- Register the exact callback URL and required Freshdesk scopes.
- Exchange the code server-side and retain the returned refresh token.
- Verify with a low-risk account or agent endpoint on the customer's domain.