Intercom

Skill apideck-libraries/api-skills/providers/claude/plugin/skills/intercom

One abstraction, 146 SaaS connectors. Agent skills for Apideck's Unified API — integrate Salesforce, QuickBooks, BambooHR, Jira, Shopify and 140+ more by changing one string.

Install

npx -y skills add apideck-libraries/api-skills --skill intercom

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Intercom via Apideck's Proxy API + managed Vault auth — Apideck handles auth and proxies HTTP calls to Intercom's native API. Use when the user wants to call Intercom (no unified API resource mapping). Routes through Apideck with serviceId "intercom".

The file declares its own license as Apache-2.0. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

3.9 KB, as published. Nobody here has run it

Intercom (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 serviceId to 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.