DatriseAI-first ETL

Intercom Redash

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

How Datrise loads Intercom into Redash

Datrise syncs Intercom's conversations, customer attributes, inbox events, and support engagement into Redash as SQL tables Redash queries and visualizes. Flexible or custom fields land in flattened columns for query results, and timestamps such as created, updated, and status changes are typed as temporal columns.

Sync is incremental: Datrise uses incremental refresh of the connected tables, so re-runs update only what changed. Date-partitioned facts for scheduled queries. Redash caches query results on a schedule, so Datrise keeps tables incrementally fresh so cached dashboards reflect reality.

Ideal for lightweight, query-driven dashboards.

Endpoints

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

Redash: Open-source SQL client for queries, visualizations, and dashboards.

How Intercom entities map to Redash

Intercom entityRedash objectNotes
conversationsintercom_conversationsid PK · custom fields → flattened columns for query results
customer attributesintercom_customer_attributesid PK · linked to intercom_conversations
inbox eventsintercom_inbox_eventstemporal columns events
support engagementintercom_support_engagementid PK · linked to intercom_conversations

FAQ

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

Flexible values are stored as flattened columns for query results, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native Redash types.

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

It runs incrementally — Datrise uses incremental refresh of the connected tables.

Related pipelines

Early access

Connect Intercom to Redash 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.