DatriseAI-first ETL

PipeRun PlanetScale

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

How Datrise loads PipeRun into PlanetScale

Datrise syncs PipeRun's contacts, accounts, deals, activities, and lifecycle events 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

PipeRun: CRM widely used in Latin America for sales pipeline and customer ops.

PlanetScale: Serverless MySQL platform with safe schema workflows.

How PipeRun entities map to PlanetScale

PipeRun entityPlanetScale objectNotes
contactspiperun_contactsid PK · custom fields → JSON columns
accountspiperun_accountsid PK · linked to piperun_contacts
dealspiperun_dealsid PK · linked to piperun_contacts
activitiespiperun_activitiesDATETIME events

FAQ

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