Real-time
Two-way sync
Changes in Rollworks or Supabase instantly reflect in both systems. No stale data, no manual imports.
Marketing ⇄ Database
Rollworks to Supabase integration — real-time, two-way sync
Keep Rollworks 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 Rollworks and Supabase
Give your team Rollworks's contacts, campaigns, and engagement in Supabase: query them with SQL, push audiences built from your own data back to Rollworks, and skip the marketing API.
Rollworks 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 Audience Segments, Campaigns, Ad Groups and Ads, Reporting and Attribution from Rollworks into JSONB Columns, Database Functions, Storage Object Metadata, Tables 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 Rollworks to drive campaigns and ads, with Rollworks kept authoritative for engagement. You decide which side owns which fields, and Stacksync resolves conflicts by rules you set.
Common use cases
- 01 Mirror billing and subscription records into Supabase tables the application can join directly
- 02 Reflect auth.users state into support and CRM systems so teams see account status without querying the database
- 03 Activate high-intent accounts by writing them into a Target Account List tier when a product or intent signal fires in an operational database.
- 04 Create and edit Prospecting v2 Campaigns and Ad Groups programmatically so budgets and targeting stay in step with an internal planning system.
Common sync patterns
React to marketing changes as row changes
A new lead, form fill, or list change in Rollworks 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.
Query Rollworks like a database
Contacts, leads, audiences, and campaign metrics from Rollworks live in Supabase as ordinary tables or collections, joinable with the rest of your data and reachable without touching the vendor API.
What you can sync between Rollworks 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.
| Rollworks objects | Supabase objects | How this pairing syncs | |
|---|---|---|---|
| Accounts (TAL Items) Individual accounts identified by domain; added or removed via the tier items endpoint (POST/DELETE) so an operational database can control which domains are targeted. | Schemas Namespaces (public and custom) that scope sync access. | Accounts (TAL Items) is specific to Rollworks and Schemas to Supabase — each maps to any object or custom field on the other side. | |
| Audience Segments CRM (email), custom (cookie or ID), and lookalike segments created via /audience/v1/segments; membership is written from a warehouse with a duration of 1 to 540 days. | auth.users Managed authentication users, often mirrored into CRM or support systems. | Audience Segments is specific to Rollworks and auth.users to Supabase — each maps to any object or custom field on the other side. | |
| Campaigns Prospecting v2 campaigns running on Web and LinkedIn with budget, KPI, and flight settings; created and edited via API and read back for status and pacing. | Row Level Security Policies Row-level access rules that govern what the REST layer exposes. | Campaigns is specific to Rollworks and Row Level Security Policies to Supabase — each maps to any object or custom field on the other side. | |
| Ad Groups and Ads Campaign subdivisions carrying attribute, contextual, geo, and device targeting plus creative; read and written to keep targeting aligned with an internal planning system. | JSONB Columns Semi-structured payloads such as event properties or nested objects. | Ad Groups and Ads is specific to Rollworks and JSONB Columns to Supabase — each maps to any object or custom field on the other side. | |
| Reporting and Attribution Delivery and attribution metrics (impressions, clicks, cost, conversions, view-throughs) from the GraphQL Reporting API; read-only, aggregated by campaign, ad, and account domain. | Database Functions Postgres functions that can transform or validate synced rows. | Reporting and Attribution is specific to Rollworks and Database Functions to Supabase — each maps to any object or custom field on the other side. | |
| Target Account Lists Named lists of B2B accounts for ABM; managed through /audience/v1/target_accounts so a CRM or warehouse can push and reconcile the accounts RollWorks advertises against. | Storage Object Metadata File metadata rows that can be joined to synced application data. | Target Account Lists is specific to Rollworks and Storage Object Metadata to Supabase — each maps to any object or custom field on the other side. |
How changes propagate between Rollworks 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.
Rollworks Supabase Interval-based propagation
DetectionStacksync polls Rollworks for changes on an incremental schedule, reading only records changed since the previous pass. Polling — reporting is pulled via GraphQL queries and account/audience membership is reconciled on a schedule.
DeliveryEach detected change is applied to Supabase as a row-level write, with types converted between the two schemas.
Supabase Rollworks 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 Rollworks through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Rollworks: NextRoll does not publish explicit rate limits; access tokens expire 24 hours after issue and refresh tokens rotate on use, so long-running syncs must keep refreshing credentials.
- 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 Rollworks ⇄ Supabase
Connect Rollworks and Supabase for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Rollworks–Supabase connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Rollworks 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 Rollworks or Supabase record.
Observability
Monitoring
Track your Rollworks ⇄ Supabase sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Rollworks and Supabase.
How the Rollworks and Supabase connectors work
Rollworks
- Integration surface
- REST APIs (Audience, Prospecting v2) plus a GraphQL Reporting API
- Authentication
- OAuth 2.0 via NextRoll (Authorization Code grant, Bearer tokens per RFC 6749/6750); Personal Access Tokens supported for server-side scripts
- Change detection
- Polling — reporting is pulled via GraphQL queries and account/audience membership is reconciled on a schedule; no change webhooks or CDC feed is published
- Capabilities
- read · write
- Rate limits
- NextRoll does not publish explicit rate limits; access tokens expire 24 hours after issue and refresh tokens rotate on use, so long-running syncs must keep refreshing credentials.
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 Rollworks 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.
- 01
Connect your apps
Authenticate Rollworks 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.
Rollworks
connected
Supabase
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Rollworks 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.
objects · Rollworks ⇄ SupabaseCustomers 12,480Sales Orders 8,213Invoices 5,902Items 1,344 - 03
Map fields
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Rollworks SupabaseCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Rollworks and Supabase integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Rollworks and Supabase: authenticate both systems, choose the objects to sync (such as Rollworks's Accounts (TAL Items) and Audience Segments), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
On the Supabase side: JSONB Columns, Database Functions, Storage Object Metadata, Tables, plus custom fields where Supabase exposes them. On the Rollworks side: Audience Segments, Campaigns, Ad Groups and Ads, Reporting and Attribution. Stacksync auto-detects both schemas and converts types between the two systems.
-
Yes. Each object mapping can be bidirectional or restricted to a single direction (both systems accept writes). Read-only mirrors, one-way pushes, and full two-way sync can be mixed in the same integration.
-
Common patterns for Rollworks and Supabase: React to marketing changes as row changes; Keep contact attributes consistent; Query Rollworks like a database. A new lead, form fill, or list change in Rollworks arrives as a row change in Supabase, so scoring, jobs, and notifications run in the tooling your team already uses.
-
Rollworks: REST APIs (Audience, Prospecting v2) plus a GraphQL Reporting API. Authentication: OAuth 2.0 via NextRoll (Authorization Code grant, Bearer tokens per RFC 6749/6750); Personal Access Tokens supported for server-side scripts. Supabase: 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. Stacksync manages authentication, retries, and rate limits on both sides.
-
Supabase: Supabase Realtime is built on the Postgres write-ahead log, streaming row changes over websockets. Rollworks: There is no change-notification webhook or CDC channel; account, audience, campaign, and reporting data must be polled, so freshness depends on the sync interval. Stacksync's field mapping accounts for these differences between Rollworks and Supabase without custom code.
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.
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:
Related integrations
Every pair below is a real-time, two-way sync. Search all 404 integrations available for Rollworks and Supabase.
Popular · 6 of 404
-
Rollworks ⇄ MySQL -
Rollworks ⇄ SQL Server -
Supabase ⇄ Iterable -
Supabase ⇄ Bingads -
Supabase ⇄ Twitter Ads -
Supabase ⇄ Marketo
No integrations match .
