Zapier Storage to MySQL Integration

How Datrise loads Zapier Storage into MySQL

Datrise syncs Zapier Storage's stored values, keys, secrets, zaps, update events, and storage buckets 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

Zapier Storage: Key-value storage used by Zapier automations.

MySQL: Widely used OSS relational engine (InnoDB).

How Zapier Storage entities map to MySQL

Zapier Storage entity	MySQL object	Notes
stored values	`zapier_supported_storage_stored_values`	id PK · custom fields → JSON columns
keys	`zapier_supported_storage_keys`	id PK · linked to zapier_supported_storage_stored_values
secrets	`zapier_supported_storage_secrets`	id PK · linked to zapier_supported_storage_stored_values
zaps	`zapier_supported_storage_zaps`	id PK · linked to zapier_supported_storage_stored_values

FAQ

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