| name | intercom-common-errors |
| description | Diagnose and fix Intercom API errors by HTTP status code and error type.
Use when encountering Intercom errors, debugging failed API requests,
or troubleshooting integration issues.
Trigger with phrases like "intercom error", "fix intercom",
"intercom not working", "debug intercom", "intercom 401", "intercom 429".
|
| allowed-tools | Read, Grep, Bash(curl:*) |
| version | 1.6.0 |
| license | MIT |
| author | Jeremy Longshore <jeremy@intentsolutions.io> |
| tags | ["saas","support","messaging","intercom"] |
| compatibility | Designed for Claude Code |
Intercom Common Errors
Overview
Quick reference for diagnosing and fixing Intercom REST API errors by HTTP
status code. Every Intercom error returns the same envelope, so triage is
fast: read the errors[].code, match it to the table below, apply the fix.
All Intercom errors share this shape:
{
"type": "error.list",
"request_id": "req_abc123",
"errors": [{ "code": "unauthorized", "message": "Access Token Invalid" }]
}
The full per-code catalog (causes + copy-paste fixes) lives in
references/error-reference.md.
Prerequisites
- An Intercom access token in
INTERCOM_ACCESS_TOKEN (Developer Hub > Your App > Authentication).
curl and jq for the diagnostic commands.- For the TypeScript fixes: the
intercom-client SDK (npm install intercom-client).
Instructions
- Capture the error. Grab the HTTP status and the JSON body. Use Read on your app logs, or Grep the codebase for the failing call site to see how the request is built.
- Match the code. Find the
errors[].code in the Error Handling table below.
- Confirm the token/limits first. Run the diagnostic script in references/diagnostics.md to rule out auth and rate-limit issues in one shot.
- Apply the fix. Open references/error-reference.md, jump to your status code, and use the causes + fix snippet there.
