DatriseAI-first ETL

Manatal to PlanetScale Integration

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

How Datrise loads Manatal into PlanetScale

Datrise syncs Manatal's candidates, jobs, applications, pipeline stages, match scores, and clients 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

Manatal: AI recruitment software with candidate scoring.

PlanetScale: Serverless MySQL platform with safe schema workflows.

How Manatal entities map to PlanetScale

Manatal entityPlanetScale objectNotes
candidatesmanatal_candidatesid PK · custom fields → JSON columns
jobsmanatal_jobsid PK · linked to manatal_candidates
applicationsmanatal_applicationsid PK · linked to manatal_candidates
pipeline stagesmanatal_pipeline_stagesid PK · linked to manatal_candidates

FAQ

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