intercom skill
Allows an agent to call Intercom's native API through Apideck's Proxy API with managed OAuth2 authentication.
- GitHub stars
- 5
- Files
- 2
- Last commit
- Nov 11, 2026
- License
- Apache-2.0
- Allowed tools
- —
What does the intercom skill do?
intercom allows an agent to call Intercom's native API through Apideck's Proxy API with managed OAuth2 authentication.
Summary generated from the skill's SKILL.md.
About the intercom skill
Communicating with Intercom through Apideck's Proxy API allows developers to interact with Intercom's native endpoints without managing complex authentication flows. An agent should load this skill when a user needs to fetch data from or send requests to Intercom using the platform's original request and response shapes. It functions by routing HTTP calls through a proxy that injects credentials stored in Apideck Vault.
This skill is specifically designed for proxy-only access rather than using a unified resource model. It relies on managed OAuth2 authentication, where Apideck handles the authorization code flow, token exchange, and automatic token refreshes. By using the serviceId intercom, the agent can forward bytes directly to Intercom's downstream URLs. This approach eliminates the need for the agent to handle per-tenant API keys or manual credential plumbing, providing a consistent request envelope for all Intercom API interactions.
What an agent can do with it
- 1Fetch Intercom dataRequest specific information from Intercom by calling its native API endpoints through the proxy.
- 2Manage OAuth2 authenticationHandle user authorization and token refreshes automatically using Apideck Vault.
- 3Execute native API requestsSend custom HTTP methods and bodies directly to Intercom's endpoints without data transformation.
Written from the skill's SKILL.md. Every use case is checked against a quote from it.
How to install the intercom skill
Each command copies the skill folder into the client's skills directory. Restart the client or start a new session to load it.Install the intercom skill in Claude Code
~/.claude/skills/intercom/SKILL.md
$ npx degit apideck-libraries/api-skills/skills/intercom ~/.claude/skills/intercomInstall the intercom skill in Claude Code (project)
.claude/skills/intercom/SKILL.md
$ npx degit apideck-libraries/api-skills/skills/intercom .claude/skills/intercomInstall the intercom skill in Codex
~/.agents/skills/intercom/SKILL.md
$ npx degit apideck-libraries/api-skills/skills/intercom ~/.agents/skills/intercomInstall the intercom skill in Gemini CLI
~/.gemini/skills/intercom/SKILL.md
$ npx degit apideck-libraries/api-skills/skills/intercom ~/.gemini/skills/intercomInstall the intercom skill in Claude.ai
npx degit apideck-libraries/api-skills/skills/intercom intercom && zip -r intercom.zip intercom # claude.ai → Customize → Skills → + → Create skill → Upload a skill → intercom.zip
SKILL.md
View on GitHubIntercom (via Apideck Proxy)
Access Intercom through Apideck's Proxy API with managed Vault auth. Apideck stores credentials, refreshes tokens, and forwards your HTTP calls to Intercom's native API — you keep using Intercom's own request and response shapes, while Apideck eliminates per-tenant credential plumbing and gives you a single auth integration shared across every Apideck connector.
Auth-only / proxy-only connector. Apideck does not map Intercom to a unified-API resource model — your code talks Intercom's own API directly through the Proxy. You still get Vault credential storage, token refresh, retries, and a consistent request envelope.
Quick facts
- Apideck serviceId:
intercom - Mode: Proxy-only (no unified API resources)
- Auth type: oauth2
- Status: beta
- Gotchas: page
- Intercom docs: https://developers.intercom.com/docs
- Homepage: https://www.intercom.com/
When to use this skill
Activate this skill when the user wants to call Intercom via Apideck — for example, "call the Intercom API" or "fetch data from Intercom". This skill teaches the agent:
- That Intercom routes through Apideck's Proxy API, not a unified resource API
- The correct
serviceIdto pass on every call (intercom) - How to keep using Intercom's native request/response shapes while Apideck handles Vault auth
If you need a unified-API surface (one method shape across many vendors), see the connector skills in this catalog whose serviceId is mapped to a unified API.
Auth
- Type: OAuth 2.0
- Managed by: Apideck Vault — Apideck handles the full OAuth dance (authorization code flow, token exchange, refresh). Never ask the user for API keys or tokens directly.
- User setup: Users authorize via the Vault modal. Connection state progresses
available → added → authorized → callable. - Token refresh: automatic. Expired tokens are refreshed transparently on the next API call.
Calling Intercom via the Proxy API
Send any HTTP request to https://unify.apideck.com/proxy. Apideck looks up the user's stored Intercom credentials by x-apideck-consumer-id + x-apideck-service-id, injects them on the way out, and returns Intercom's raw response.
curl 'https://unify.apideck.com/proxy' \
-H "Authorization: Bearer ${APIDECK_API_KEY}" \
-H "x-apideck-app-id: ${APIDECK_APP_ID}" \
-H "x-apideck-consumer-id: ${CONSUMER_ID}" \
-H "x-apideck-service-id: intercom" \
-H "x-apideck-downstream-url: <target endpoint on Intercom>" \
-H "x-apideck-downstream-method: GET"
For POST/PATCH/PUT/DELETE, change x-apideck-downstream-method and pass the body as you would to Intercom directly. Apideck does not transform the body — it forwards bytes.
See Intercom's API docs for available endpoints.
See also
- Intercom gotchas
- Apideck Proxy API reference
apideck-rest— REST patterns including the Proxyapideck-best-practices— Vault, error handling, retriesapideck-unified-api— when to use unified vs proxy- Intercom official docs
Files in this skill
2intercom skill questions
How do I install the intercom skill in Claude Code?
Run npx degit apideck-libraries/api-skills/skills/intercom ~/.claude/skills/intercom. Claude Code loads skills from ~/.claude/skills (all projects) or .claude/skills (one project) and uses a skill when its description matches the task.
Which clients can use the intercom skill?
Any client that reads the Agent Skills format: Claude Code, Codex, Gemini CLI and claude.ai (upload as a ZIP). Scripts in the skill run only where the client allows code execution.
Does this skill provide a unified API resource model for Intercom?
No, this is a proxy-only connector. You must use Intercom's native request and response shapes directly through the proxy.
What serviceId should be used when making calls?
You should use the serviceId 'intercom' for every call.