Skip to content
Marketing ⇄ Database

Iterable to Supabase integration — real-time, two-way sync

Keep Iterable and Supabase in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.

  • SOC 2 and 6 other compliance frameworks
  • POC with real engineers in minutes

Adopted by fast-scaling companies moving mission-critical data in real time

Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect Iterable and Supabase

Give your team Iterable's contacts, campaigns, and engagement in Supabase: query them with SQL, push audiences built from your own data back to Iterable, and skip the marketing API.

Iterable holds the people, audiences, and campaign activity that marketing runs on, but that data sits behind interfaces built for marketers, not for your internal systems. Engineers and analysts who need contacts, list membership, or engagement, for reporting, attribution, or product logic, end up writing integration code against a rate-limited API and maintaining it forever. Meanwhile the customer and usage data marketers want for targeting already lives in Supabase, hard to get into campaigns without manual exports.

Stacksync mirrors Events, Campaigns, Templates, Lists from Iterable into Database Functions, Storage Object Metadata, Tables, Views in Supabase field by field, in real time, and in both directions. Marketing records become rows your code can query and join with product and customer data; audiences and attributes computed in Supabase, from usage, orders, or account status, sync back into Iterable to drive campaigns and ads, with Iterable kept authoritative for engagement. You decide which side owns which fields, and Stacksync resolves conflicts by rules you set.

Common use cases

  • 01 Push product events captured in Supabase Postgres to marketing tools for lifecycle campaigns
  • 02 Consolidate Supabase project data into a warehouse for analytics while keeping the app database as the system of record
  • 03 Write list subscribe/unsubscribe changes from a CRM back into Iterable Lists so suppression and opt-in state stay current before the next send.
  • 04 Two-way sync User profiles and their custom data fields between Iterable and a Postgres database or CRM so attributes and subscription state stay aligned in both systems.

Common sync patterns

Engagement and results next to the customer

Opens, clicks, sends, RSVPs, or ad activity from Iterable land in Supabase beside the matching customer record, ready for reporting and revenue attribution.

React to marketing changes as row changes

A new lead, form fill, or list change in Iterable arrives as a row change in Supabase, so scoring, jobs, and notifications run in the tooling your team already uses.

Keep contact attributes consistent

Lifecycle stage, subscription status, or plan maintained on either side stays current on the other, ending exports and dual data entry.

What you can sync between Iterable and Supabase

Representative objects on each side — any object or custom field can map to any target. Schemas are auto-detected; types are converted between the two systems.

Iterable objects Supabase objects How this pairing syncs
Commerce / Purchases Purchase and cart activity tracked via /api/commerce/trackPurchase and /api/commerce/updateCart, feeding revenue attribution and abandoned-cart journeys. auth.users Managed authentication users, often mirrored into CRM or support systems. Commerce / Purchases is specific to Iterable and auth.users to Supabase — each maps to any object or custom field on the other side.
Export data Historical user and event records pulled through the Export API (/api/export/data.json, data.csv, and userEvents) across data types like emailSend, emailOpen, emailClick, emailBounce, purchase, and customEvent. Row Level Security Policies Row-level access rules that govern what the REST layer exposes. Export data is specific to Iterable and Row Level Security Policies to Supabase — each maps to any object or custom field on the other side.
Users User profiles keyed by email or userId with custom data fields; upserted via POST /api/users/update, read via GET /api/users/{email} or getByUserId, bulk-written via /api/users/bulkUpdate (up to 1000 users per call), and deleted or GDPR-forgotten. JSONB Columns Semi-structured payloads such as event properties or nested objects. Users is specific to Iterable and JSONB Columns to Supabase — each maps to any object or custom field on the other side.
Events Custom and system events tracked via /api/events/track and /api/events/trackBulk (up to 1000 events per call); a single user's event history is read via GET /api/events/{email}. Database Functions Postgres functions that can transform or validate synced rows. Events is specific to Iterable and Database Functions to Supabase — each maps to any object or custom field on the other side.
Campaigns Email, SMS, push, and in-app sends; metadata and metrics read via GET /api/campaigns and /api/campaigns/metrics, created and sent via /api/campaigns/create and /api/campaigns/trigger. Storage Object Metadata File metadata rows that can be joined to synced application data. Campaigns is specific to Iterable and Storage Object Metadata to Supabase — each maps to any object or custom field on the other side.
Templates Reusable email/SMS/push/in-app message templates with handlebars fields; read via /api/templates and per-channel get endpoints, written via /api/templates/email/upsert and the other channel upserts. Tables Standard Postgres tables; the primary two-way sync target. Templates is specific to Iterable and Tables to Supabase — each maps to any object or custom field on the other side.

How changes propagate between Iterable and Supabase

Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.

Iterable Supabase Sub-second propagation

DetectionIterable notifies Stacksync of record changes through webhook events. System Webhooks push email/SMS/push/in-app and custom events (send, open, click, bounce, complaint, unsubscribe) as JSON POSTs in near real time.

DeliveryEach detected change is applied to Supabase as a row-level write, with types converted between the two schemas.

Supabase Iterable Sub-second propagation

DetectionSupabase pushes changes as they happen — webhook events backed by change data capture. Log-based CDC via Postgres logical replication, the same WAL feed that powers Supabase Realtime.

DeliveryEach detected change is written to Iterable through its API, with automatic retries and rate-limit backoff.

Rate-limit considerations

  • Iterable: Limits are per endpoint and per project/key; exceeding one returns HTTP 429, so exponential backoff is advised. Event tracking allows far higher volume than metadata endpoints like campaigns/templates, and the Export API is throttled more tightly. Since Nov 10, 2025, passing the key in the query string or body is rate-limited more strictly than the Api-Key header.
  • Supabase: SQL access is bounded by connection limits (pooled connections are provided); the REST layer is subject to the platform's limits.
What ships with Iterable ⇄ Supabase

Connect Iterable and Supabase for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Iterable–Supabase connection.

Real-time

Two-way sync

Changes in Iterable or Supabase instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Iterable or Supabase data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.

At scale

Event queues

Handle millions of events per minute without losing a single Iterable or Supabase record.

Observability

Monitoring

Track your Iterable ⇄ Supabase sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Iterable and Supabase.

How the Iterable and Supabase connectors work

Iterable

Integration surface
Iterable REST API (JSON over HTTPS): Users, Events, Campaigns, Templates, Lists, Catalogs, and Commerce endpoints, plus a bulk Export API for historical data
Authentication
API key sent in the Api-Key HTTP header (also accepted as Api_Key; the name is case-insensitive). Keys are scoped by type - Server-side, JavaScript (Web SDK), or Mobile - with optional JWT-enabled keys. US projects use api.iterable.com; EU projects use api.eu.iterable.com.
Change detection
System Webhooks push email/SMS/push/in-app and custom events (send, open, click, bounce, complaint, unsubscribe) as JSON POSTs in near real time; historical backfill and incremental catch-up run through the Export API over a date range.
Capabilities
read · write · webhooks
Rate limits
Limits are per endpoint and per project/key; exceeding one returns HTTP 429, so exponential backoff is advised. Event tracking allows far higher volume than metadata endpoints like campaigns/templates, and the Export API is throttled more tightly. Since Nov 10, 2025, passing the key in the query string or body is rate-limited more strictly than the Api-Key header.

Supabase

Integration surface
Direct PostgreSQL wire protocol connection, plus an auto-generated REST API (PostgREST)
Authentication
Database credentials (connection string) for SQL access; API keys (anon / service role) for the REST layer
Change detection
Log-based CDC via Postgres logical replication, the same WAL feed that powers Supabase Realtime; database webhooks can also fire on row changes
Capabilities
read · write · CDC · webhooks
Rate limits
SQL access is bounded by connection limits (pooled connections are provided); the REST layer is subject to the platform's limits
How it works

How to connect Iterable to Supabase — three steps, no code

Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.

  1. 01

    Connect your apps

    Authenticate Iterable and Supabase with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Iterable connected
    Supabase connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Iterable and Supabase objects to sync — Stacksync auto-detects both schemas, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Iterable ⇄ Supabase
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    Iterable Supabase
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Iterable and Supabase integration FAQ

SECURITY

Security teams trust Stacksync

As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.

Learn more about security
SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS

SSO & SCIM

Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.

Alerts

Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.

Secure connection options

Securely connects to your systems with:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Related integrations

Every pair below is a real-time, two-way sync. Search all 500 integrations available for Iterable and Supabase.

Popular · 8 of 500
All Iterable integrations All Supabase integrations Browse all integrations
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.

Book a demo Tour the platform on your own