DatriseAI-first ETL

Intercom DuckDB

AI-first ETL from Intercom into DuckDB. Governed entities, incremental sync, typed landing tables.

How Datrise loads Intercom into DuckDB

Datrise syncs Intercom's conversations, customer attributes, inbox events, and support engagement into DuckDB as a typed table per source entity in a DuckDB file. Flexible or custom fields land in JSON or STRUCT columns, and timestamps such as created, updated, and status changes are typed as TIMESTAMP WITH TIME ZONE.

Sync is incremental: Datrise uses rewrites changed entities into the local database (or Parquet) on each run, so re-runs update only what changed. Hive-partitioned Parquet by load date when exporting. DuckDB is single-writer and embedded, so Datrise produces a consistent file snapshot rather than concurrent streaming writes.

Ideal for local and notebook analytics without standing up a server.

Endpoints

Intercom: Customer messaging platform with CRM-style account and conversation context.

DuckDB: In-process analytics database for fast local OLAP.

How Intercom entities map to DuckDB

Intercom entityDuckDB objectNotes
conversationsintercom_conversationsid PK · custom fields → JSON or STRUCT columns
customer attributesintercom_customer_attributesid PK · linked to intercom_conversations
inbox eventsintercom_inbox_eventsTIMESTAMP WITH TIME ZONE events
support engagementintercom_support_engagementid PK · linked to intercom_conversations

FAQ

How does Datrise handle Intercom's custom fields in DuckDB?

Flexible values are stored as JSON or STRUCT columns, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native DuckDB types.

How does the Intercom to DuckDB sync stay up to date?

It runs incrementally — Datrise uses rewrites changed entities into the local database (or Parquet) on each run.

Related pipelines

Early access

Connect Intercom to DuckDB the easy way

Skip brittle scripts and manual exports. Join the waitlist to get a guided setup, AI-assisted mapping, and reliable incremental sync for this integration.