DatriseAI-first ETL

Intercom Tickets PlanetScale

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

How Datrise loads Intercom Tickets into PlanetScale

Datrise syncs Intercom Tickets'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 Tickets: SaaS or API data source for analytics and warehouse sync.

PlanetScale: Serverless MySQL platform with safe schema workflows.

How Intercom Tickets entities map to PlanetScale

Intercom Tickets entityPlanetScale objectNotes
recordsintercom_tickets_recordsid PK · custom fields → JSON columns
eventsintercom_tickets_eventsDATETIME events
configuration objectsintercom_tickets_configuration_objectsid PK · linked to intercom_tickets_records

FAQ

How does Datrise handle Intercom Tickets'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 Tickets 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 Tickets 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.