Understanding Intercom Errors in Hurree

If you're experiencing issues with your Intercom widgets, this guide explains the most common errors and how to resolve them. Each error below matches the message you'll see in Hurree.

If you encounter an error that isn't covered below, please contact our support team for assistance.

Explanation: Hurree was unable to verify your Intercom API key or access token. This usually happens when your token has expired or been revoked, or when access to Hurree has been removed from within your Intercom workspace.

How to solve: Reconnect your Intercom account through Hurree to restore access. Once reconnected, your widgets will begin updating again from the next scheduled sync.

Explanation: The data you're trying to access isn't available on your current Intercom plan. Some Intercom data is only available on higher-tier subscriptions.

How to solve: Review your subscription in Intercom to confirm which features are included on your plan, and upgrade if the data you need sits on a higher tier. Once your plan has been updated, refresh your connection in Hurree and try again.

Explanation: You don't have permission to access this Intercom resource. This can occur if your seat type or permissions have changed, access has been revoked, or you have not been granted the appropriate level of access within your Intercom workspace.

How to solve: Check that your Intercom account has the necessary access rights, or contact your administrator and ask them to review your permissions. Once the required access has been granted, refresh your connection and try retrieving the data again.

Explanation: The requested Intercom resource could not be found. This may occur if a conversation, contact, company, or segment has been deleted, or if the reference is incorrect.

How to solve: Review the relevant Intercom workspace and verify that the record or data source still exists. If it has been removed, you may need to update your widget settings or select an alternative data source.

Explanation: The request took too long to complete. This is usually caused by a temporary network delay or a particularly large volume of data being requested at once.

How to solve: Check your connection and try again, or check your widget after the next scheduled sync period. If timeouts continue, consider narrowing the date range on your widget to reduce the amount of data being retrieved.

Explanation: More than one Intercom user matches the email address provided, so the request could not be completed against a single record. This usually happens when duplicate contacts exist in your workspace.

How to solve: Use a more specific identifier, such as a user ID, in your widget settings and try again. It's also worth reviewing your Intercom workspace for duplicate contacts and merging them where appropriate.

Explanation: The request was well-formed but could not be processed. This usually means a setting or value being sent to Intercom isn't in the format Intercom expects.

How to solve: Check that all fields in your integration settings are correctly filled in and try again. If the error persists, please contact our support team for assistance.

Explanation: Intercom restricts the number of requests that can be made within a given time period. This error means that limit has been reached, usually because a large volume of data was requested at once.

How to solve: Wait a moment before trying again; your access will resume automatically once the rate limit window resets. If you see this error frequently, consider reducing the number of Intercom widgets refreshing at the same time.

Explanation: An unexpected error occurred on Intercom's servers. This is not caused by any action on your part, and as the issue originates within Intercom's infrastructure, it is outside of our control.

How to solve: Internal server errors are typically temporary and often resolve automatically. Wait a moment and try again, or check your widget after the next scheduled sync period. If the error persists after multiple sync attempts, please contact our support team for assistance.

Explanation: Intercom is currently unavailable, most often due to maintenance or an unexpected outage on their side.

How to solve: Wait a few minutes and try again. Your widgets will update automatically once Intercom is back online. If the outage appears to be prolonged, you can check Intercom's status page for updates.

Explanation: Intercom did not respond within the expected time frame. This is usually caused by a temporary delay or heavy load on their servers rather than a problem with your account.

How to solve: Wait a moment and try again, or check your widget after the next scheduled sync period. If timeouts continue, please contact our support team for assistance.

Explanation: You may occasionally see a 502: Server Error. This means an error occurred on Intercom's servers while your request was being processed, and it is not caused by any action on your part.

How to solve: Wait a moment and try again, or check your widget after the next scheduled sync period. If the error persists, please contact our support team for assistance.

Explanation: You may occasionally see 400: Bad Request, 405: Method Not Supported, 406: Not Acceptable, 415: Unsupported Media Type, or bad_request. These indicate that something about the request sent to Intercom was invalid, incorrectly formatted, missing a required parameter, or used a format Intercom doesn't support; they are typically handled automatically and are rarely caused by anything on your side.

How to solve: Review your integration settings for any incorrect entries and try again. If any of these errors persist, please contact our support team with the error name you're seeing, and we'll investigate.

If you've completed the troubleshooting steps above and are still experiencing issues with your Intercom widgets, our support team is here to help. Share the error message you're seeing along with any relevant details, and we'll work with you to identify and resolve the issue as quickly as possible.