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: