Apify to PlanetScale Integration

How Datrise loads Apify into PlanetScale

Datrise syncs Apify's actors, runs, datasets, key-value stores, request queues, and run logs 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

Apify: Web scraping and browser automation platform.

PlanetScale: Serverless MySQL platform with safe schema workflows.

How Apify entities map to PlanetScale

Apify entity	PlanetScale object	Notes
actors	`apify_actors`	id PK · custom fields → JSON columns
runs	`apify_runs`	id PK · linked to apify_actors
datasets	`apify_datasets`	id PK · linked to apify_actors
key-value stores	`apify_key_value_stores`	id PK · linked to apify_actors

FAQ

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