Particle to Supabase Integration

How Datrise loads Particle into Supabase

Datrise syncs Particle's devices, events, variables, firmware versions, product fleets, and device logs into Supabase as a typed table per source entity in your Supabase Postgres. 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 for high-volume tables. Datrise lands into a dedicated schema and leaves row-level security to you, so synced tables don't inherit public access by accident.

Ideal for app builders who want CRM data alongside their Supabase product data.

Endpoints

Particle: IoT device fleet telemetry and events.

Supabase: Postgres platform with auth, storage, and realtime APIs.

How Particle entities map to Supabase

Particle entity	Supabase object	Notes
devices	`particle_devices`	id PK · custom fields → jsonb columns
events	`particle_events`	timestamptz events
variables	`particle_variables`	id PK · linked to particle_devices
firmware versions	`particle_firmware_versions`	id PK · linked to particle_devices

FAQ

How does Datrise handle Particle's custom fields in Supabase?

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

How does the Particle to Supabase 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 Particle to Supabase 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.