Short.io to MySQL Integration

How Datrise loads Short.io into MySQL

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

Sync is incremental: Datrise uses a watermark on updated-at, applied with INSERT … ON DUPLICATE KEY UPDATE, so re-runs update only what changed. Optional RANGE partitioning by load date. MySQL collation matters for CRM text, so Datrise lands utf8mb4 to preserve emoji and non-Latin characters.

Ideal for operational reporting and app databases already standardized on MySQL.

Endpoints

Short.io: Branded short links and click analytics.

MySQL: Widely used OSS relational engine (InnoDB).

How Short.io entities map to MySQL

Short.io entity	MySQL 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 MySQL?

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 MySQL types.

How does the Short.io to MySQL 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 MySQL 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.