Source connector

Intercom connector

Intercom integration for databases, warehouses and BI tools

Customer messaging platform with CRM-style account and conversation context. Datrise captures Intercom entities such as conversations, customer attributes, inbox events, and support engagement, then lands normalized and typed models for warehouse reporting, attribution, and AI workflows.

The Intercom REST API v2.13 authenticates with OAuth 2.0, personal access token, incremental runs key on updated_at, and Intercom caps calls at 10,000 API calls/minute per app and 25,000/minute per workspace, evenly distributed across 10-second windows (e.g. a 1,000/min limit allows ~166 requests per 10s).

Of the 4 objects, 3 sync as upserts keyed on the primary key and 1 as append-only streams, so each incremental run moves only what changed since the last watermark. Every object lands in its own table (for example `intercom_conversations`) with a schema derived from the Intercom API rather than a flattened CSV, in any of the 43 supported destinations.

Datrise is in early access: pick a destination below to open the Intercom pipeline page, and join the waitlist to get the Intercom connector (CRM) with guided onboarding.

Incremental syncSchema-aware mapping43 destinations available

What Intercom data Datrise extracts

Each object lands in its own typed table. Sync mode is derived from the object: history-style objects append, everything else upserts.

Object	Landing table	Sync mode
conversations	intercom_conversations	Upsert by primary key, incremental on updated-at
customer attributes	intercom_customer_attributes	Upsert by primary key, incremental on updated-at
inbox events	intercom_inbox_events	Append-only, incremental by timestamp
support engagement	intercom_support_engagement	Upsert by primary key, incremental on updated-at

Intercom API: setup facts for the connector

Verified against the vendor documentation on 2026-09-02. Unknown values are left blank rather than guessed.

API	Intercom REST API v2.13
Authentication	OAuth 2.0, personal access token — Public apps use OAuth 2.0 (Bearer access token) via Developer Hub review; private/internal apps use a long-lived personal access token instead.
Pagination	cursor — List endpoints page with the `starting_after` cursor (default 20, max 150 per page via `per_page`); Search API cursors are stateless and nested in a `pagination` object, so records updated between pages can be skipped or duplicated.
Rate limit	10,000 API calls/minute per app and 25,000/minute per workspace, evenly distributed across 10-second windows (e.g. a 1,000/min limit allows ~166 requests per 10s)
Incremental cursor	updated_at — Contacts Search accepts `updated_at` with `=`/`>`/`<` operators but only day-level precision (no hour/minute/second) in the workspace's own timezone, so a same-day incremental filter cannot narrow below 24 hours.
Webhooks	Yes — Intercom Webhooks (topic subscriptions, e.g. contact.updated, contact.deleted)
Bulk export	Yes — Data Export API (async job, engagement/delivery stats only, not conversation content)
Deletes detectable	Yes — Subscribe to `contact.deleted`/`company.deleted`/`conversation.deleted` webhook topics (minimal identification payload only), or diff a full ID re-pull since a full refresh no longer returns removed records.

Official API reference

What bites when replicating Intercom

`updated_at` search filtering only supports whole-calendar-day boundaries (`=`, `>`, `<`, no `>=`/`<=`/`!=`) in the workspace's timezone, so sub-day incremental polling has to over-fetch a full day and de-duplicate downstream.
The Data Export API only exports message delivery/engagement statistics (opens, clicks, bounces, etc.), never the actual conversation or message content, and allows just one active export job per workspace at a time (a second request while one is running returns HTTP 429); each completed job's `download_expires_at` window closes the file permanently once passed.
`*.deleted` webhook payloads (contact.deleted, company.deleted, conversation.deleted) carry only identifying fields, not the deleted object's last-known attributes, so a connector relying on webhooks alone cannot reconstruct what the record looked like before removal.
Search API pagination cursors are stateless: contacts or conversations updated by someone else while you are paging through results can appear twice or be skipped entirely.

Compare this against every other documented API

Popular destinations for Intercom

Choose a destination below to open the ready pipeline page.

A
Airtable
Relational spreadsheet destination for ops and go-to-market teams.
View pipeline
A
Amazon Athena
Serverless SQL over S3 data lake tables.
View pipeline
A
Amazon DynamoDB
Serverless key-value and document store on AWS.
View pipeline
A
Amazon QuickSight
AWS serverless BI with SPICE and embedded analytics.
View pipeline
A
Amazon Redshift
AWS petabyte-scale warehouse with Spectrum.
View pipeline
A
Amazon S3 Data Lake
Object storage landing zone for parquet and snapshots.
View pipeline
A
Apache Superset
Open-source BI for SQL exploration, charts, and dashboard publishing.
View pipeline
A
Azure Data Lake Storage
ADLS Gen2 object storage for analytics workloads.
View pipeline
A
Azure Synapse
Microsoft analytics workspace with SQL pools.
View pipeline

Intercom connector FAQ

What Intercom data does the connector extract?: 4 objects: conversations, customer attributes, inbox events and support engagement. Each lands in its own table with types preserved; history-style objects (1: inbox events) load as append-only streams.
Is the Intercom integration incremental?: Yes. After the initial full load, every run reads only records changed since the last watermark (updated-at or event timestamp) and applies an upsert or an append depending on the object.
Where can I load Intercom data?: Into 43 destinations: relational databases, cloud warehouses, data lakes, spreadsheets and BI tools. Each Intercom → destination pair has its own page with the object-to-table mapping.

Related CRM sources

Other sources in the same category, each with its own connector page.

Early access

Launch your Intercom pipeline with guided onboarding

Join the waitlist to get priority access for Intercom integrations with guided setup, schema-aware mapping, and production-grade incremental sync.