Source connector
Intercom Tickets connector
Intercom Tickets integration for databases, warehouses and BI tools
Ticketed support workflows inside Intercom. Datrise captures Intercom Tickets entities such as tickets, ticket types, contacts, assignees, states and ticket attributes, then lands normalized and typed models for warehouse reporting, attribution, and AI workflows.
Of the 6 objects, 6 sync as upserts keyed on the primary key and 0 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_tickets_tickets`) with a schema derived from the Intercom Tickets 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 Tickets pipeline page, and join the waitlist to get the Intercom Tickets connector with guided onboarding.
What Intercom Tickets 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 |
|---|---|---|
| tickets | intercom_tickets_tickets | Upsert by primary key, incremental on updated-at |
| ticket types | intercom_tickets_ticket_types | Upsert by primary key, incremental on updated-at |
| contacts | intercom_tickets_contacts | Upsert by primary key, incremental on updated-at |
| assignees | intercom_tickets_assignees | Upsert by primary key, incremental on updated-at |
| states | intercom_tickets_states | Upsert by primary key, incremental on updated-at |
| ticket attributes | intercom_tickets_ticket_attributes | Upsert by primary key, incremental on updated-at |
Popular destinations for Intercom Tickets
Choose a destination below to open the ready pipeline page.
- AAirtable
Relational spreadsheet destination for ops and go-to-market teams.
View pipeline - AAmazon Athena
Serverless SQL over S3 data lake tables.
View pipeline - AAmazon DynamoDB
Serverless key-value and document store on AWS.
View pipeline - AAmazon QuickSight
AWS serverless BI with SPICE and embedded analytics.
View pipeline - AAmazon Redshift
AWS petabyte-scale warehouse with Spectrum.
View pipeline - AAmazon S3 Data Lake
Object storage landing zone for parquet and snapshots.
View pipeline - AApache Superset
Open-source BI for SQL exploration, charts, and dashboard publishing.
View pipeline - AAzure Data Lake Storage
ADLS Gen2 object storage for analytics workloads.
View pipeline - AAzure Synapse
Microsoft analytics workspace with SQL pools.
View pipeline
Intercom Tickets connector FAQ
- What Intercom Tickets data does the connector extract?
- 6 objects: tickets, ticket types, contacts, assignees, states and ticket attributes. Each lands in its own table with types preserved; history-style objects (0) load as append-only streams.
- Is the Intercom Tickets 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 Tickets data?
- Into 43 destinations: relational databases, cloud warehouses, data lakes, spreadsheets and BI tools. Each Intercom Tickets → destination pair has its own page with the object-to-table mapping.
Related sources
Other sources in the same category, each with its own connector page.
Early access
Launch your Intercom Tickets pipeline with guided onboarding
Join the waitlist to get priority access for Intercom Tickets integrations with guided setup, schema-aware mapping, and production-grade incremental sync.