“invalid access token or incorrect hosting region” error while connecting Intercom (Fin AI) with Document360
Cause
This error typically occurs when:
- The API access token is invalid or inactive.
- The incorrect Intercom hosting region is selected during the integration setup.
The token validation and hosting region configuration are managed on the Intercom (Fin AI) side. This behavior is outside the control of Document360.
Resolution
Verify the following:
- Ensure the API access token entered is valid and active.
- Ensure the correct Intercom hosting region is selected during configuration.
If the issue persists after validation, contact Intercom support for further investigation.
FAQ
Why are no results displayed in Zendesk Federated Search for the English language variant?
Zendesk’s default English language slug is en-us. If the English language variant in Document360 is configured with a different slug, such as en, Zendesk Federated Search may not return any results.
Federated Search works only when the language slugs match between both platforms. To ensure results are displayed correctly, the language slug configured in Document360 must match the corresponding Zendesk language slug.