Short.io to PlanetScale Integration

How Datrise loads Short.io into PlanetScale

Datrise syncs Short.io's links, domains, clicks, referrers, countries, and link tags 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

Short.io: Branded short links and click analytics.

PlanetScale: Serverless MySQL platform with safe schema workflows.

How Short.io entities map to PlanetScale

Short.io entity	PlanetScale object	Notes
links	`short_io_links`	id PK · custom fields → JSON columns
domains	`short_io_domains`	id PK · linked to short_io_links
clicks	`short_io_clicks`	id PK · linked to short_io_links
referrers	`short_io_referrers`	id PK · linked to short_io_links

FAQ

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