DatriseAI-first ETL

Intercom Tap PlanetScale

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

How Datrise loads Intercom Tap into PlanetScale

Datrise syncs Intercom Tap's records, events, and configuration objects into PlanetScale as a typed table per source entity. Flexible or custom fields land in JSON columns, and timestamps such as created, updated, and status changes are typed as DATETIME.

Sync is incremental: Datrise uses a watermark on updated-at, applied with INSERT … ON DUPLICATE KEY UPDATE, so re-runs update only what changed. Vitess sharding by tenant or entity key for very large tables. PlanetScale disallows foreign-key constraints by default, so Datrise models relationships by stable id columns rather than enforced FKs.

Ideal for horizontally scalable MySQL apps on Vitess.

Endpoints

Intercom Tap: SaaS or API data source for analytics and warehouse sync.

PlanetScale: Serverless MySQL platform with safe schema workflows.

How Intercom Tap entities map to PlanetScale

Intercom Tap entityPlanetScale objectNotes
recordsintercom_tap_recordsid PK · custom fields → JSON columns
eventsintercom_tap_eventsDATETIME events
configuration objectsintercom_tap_configuration_objectsid PK · linked to intercom_tap_records

FAQ

How does Datrise handle Intercom Tap's custom fields in PlanetScale?

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

How does the Intercom Tap to PlanetScale sync stay up to date?

It runs incrementally — Datrise uses a watermark on updated-at, applied with INSERT … ON DUPLICATE KEY UPDATE.

Related pipelines

Early access

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