Zapier Storage to Neon Integration

How Datrise loads Zapier Storage into Neon

Datrise syncs Zapier Storage's stored values, keys, secrets, zaps, update events, and storage buckets into Neon as a typed table per source entity. Flexible or custom fields land in jsonb columns, and timestamps such as created, updated, and status changes are typed as timestamptz.

Sync is incremental: Datrise uses a watermark on updated-at, applied with INSERT … ON CONFLICT DO UPDATE, so re-runs update only what changed. Optional declarative partitioning by load date. Neon separates compute from storage, so Datrise batches writes to keep autoscaling compute from cold-starting on every small change.

Ideal for serverless Postgres workloads that scale to zero between syncs.

Endpoints

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

Neon: Serverless Postgres destination with branching and autoscaling.

How Zapier Storage entities map to Neon

Zapier Storage entity	Neon object	Notes
stored values	`zapier_supported_storage_stored_values`	id PK · custom fields → jsonb 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 Neon?

Flexible values are stored as jsonb columns, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native Neon types.

How does the Zapier Storage to Neon sync stay up to date?

It runs incrementally — Datrise uses a watermark on updated-at, applied with INSERT … ON CONFLICT DO UPDATE.

Related pipelines

Early access

Connect Zapier Storage to Neon 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.