Real-time
Two-way sync
Changes in Gatekeeper or Supabase instantly reflect in both systems. No stale data, no manual imports.
Business productivity ⇄ Database
Gatekeeper to Supabase integration — real-time, two-way sync
Keep Gatekeeper 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 Gatekeeper and Supabase
Mirror Gatekeeper's data into Supabase so your own code can read and write it like any other table, with changes flowing both ways in seconds.
Engineers integrate with tools like Gatekeeper through APIs, which means auth, pagination, rate limits, webhooks, and retry logic, all maintained forever and all different for every tool. Meanwhile the data would be trivial to use if it simply lived in Supabase.
Stacksync mirrors Contracts, Vendors (Suppliers), Files, Workflow form data from Gatekeeper into Row Level Security Policies, JSONB Columns, Database Functions, Storage Object Metadata in Supabase and keeps both sides in sync in real time. Your services query the database directly, and inserts or updates your code makes flow back into Gatekeeper, so the tool and the database never disagree.
Common use cases
- 01 Write contract or vendor records into Gatekeeper when a deal closes in the CRM to kick off downstream procurement and legal workflows.
- 02 Two-way sync Contracts between Gatekeeper and an ERP or warehouse so value, renewal dates, owner, and status stay current without manual re-keying.
- 03 Consolidate Supabase project data into a warehouse for analytics while keeping the app database as the system of record
- 04 Sync application tables in Supabase with the CRM two-way so new signups appear as contacts and sales edits flow back to the app
Common sync patterns
React to changes as they happen
Updates in Gatekeeper arrive as row changes in Supabase, so triggers, jobs, and services can respond in near real time.
One integration pattern for the whole stack
Every synced tool looks the same from the database, so each new integration is configuration, not a new codebase.
Read Gatekeeper with a query
Records from Gatekeeper are ordinary rows in Supabase; join them, index them, and use them in application logic without touching the vendor API.
What you can sync between Gatekeeper 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.
| Gatekeeper objects | Supabase objects | How this pairing syncs | |
|---|---|---|---|
| Vendors (Suppliers) Company records for counterparties and suppliers with onboarding status, compliance, risk, contacts, and spend; read and written to keep vendor master data aligned with a CRM or ERP. | Database Functions Postgres functions that can transform or validate synced rows. | Vendors (Suppliers) is specific to Gatekeeper and Database Functions to Supabase — each maps to any object or custom field on the other side. | |
| Files Document files attached to contracts and vendors - executed PDFs, certificates, and compliance evidence; read to pull signed files and evidence out, or written to push generated documents in. | Storage Object Metadata File metadata rows that can be joined to synced application data. | Files is specific to Gatekeeper and Storage Object Metadata to Supabase — each maps to any object or custom field on the other side. | |
| Workflow form data The structured data captured on Gatekeeper workflow forms (intake requests, vendor onboarding, risk assessments); exposed by the API since 2025 so form results sync into an operational database, not only contract and vendor records. | Tables Standard Postgres tables; the primary two-way sync target. | Workflow form data is specific to Gatekeeper and Tables to Supabase — each maps to any object or custom field on the other side. | |
| Custom data groups Customer-configured custom fields and data groups; because the JSON:API and its docs are dynamic, any custom data added in Configuration exposes the same read/write endpoints as the standard objects and syncs the same way. | Views Read-side projections exposed to outbound syncs. | Custom data groups is specific to Gatekeeper and Views to Supabase — each maps to any object or custom field on the other side. | |
| Users Gatekeeper user and team records governed by role-based access; read to map contract and vendor owners, approvers, and internal contacts to CRM or HR records. | Schemas Namespaces (public and custom) that scope sync access. | Users is specific to Gatekeeper and Schemas to Supabase — each maps to any object or custom field on the other side. | |
| Categories The classification taxonomy applied to contracts and vendors (type, department, business unit); synced so categorization stays consistent between Gatekeeper and downstream reporting or ERP dimensions. | auth.users Managed authentication users, often mirrored into CRM or support systems. | Categories is specific to Gatekeeper and auth.users to Supabase — each maps to any object or custom field on the other side. |
How changes propagate between Gatekeeper 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.
Gatekeeper Supabase Interval-based propagation
DetectionStacksync polls Gatekeeper for changes on an incremental schedule, reading only records changed since the previous pass. No native developer webhook subscription API and no database change-data-capture log.
DeliveryEach detected change is applied to Supabase as a row-level write, with types converted between the two schemas.
Supabase Gatekeeper 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 Gatekeeper through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Gatekeeper: Gatekeeper publishes no fixed public per-minute request quota; throughput is governed per key by its endpoint permissions, and every call is recorded (parameters, payload, response) under API Logs for monitoring. Pace bulk writes and use JSON:API pagination on list endpoints.
- 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 Gatekeeper ⇄ Supabase
Connect Gatekeeper and Supabase for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Gatekeeper–Supabase connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Gatekeeper 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 Gatekeeper or Supabase record.
Observability
Monitoring
Track your Gatekeeper ⇄ Supabase sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Gatekeeper and Supabase.
How the Gatekeeper and Supabase connectors work
Gatekeeper
- Integration surface
- RESTful API following the JSON:API specification, tenant-scoped with interactive docs at {tenant}.gatekeeperhq.com/api_docs and a published Postman collection. The API is dynamic: it exposes the standard Contract and Vendor objects plus any custom data groups and workflow-form data configured in the tenant.
- Authentication
- API keys created and managed under Configuration > API Keys and passed as a token; each key carries granular per-endpoint permissions set to read-only or write, so access is scoped per object. Multiple keys can be issued and revoked independently.
- Change detection
- No native developer webhook subscription API and no database change-data-capture log; detect changes by polling the JSON:API list endpoints filtered and sorted on updated-at timestamps. Gatekeeper's own event automation - Workflow Engine phase transitions and Interconnect process orchestration - runs inside the platform rather than as a subscribable webhook stream.
- Capabilities
- read · write
- Rate limits
- Gatekeeper publishes no fixed public per-minute request quota; throughput is governed per key by its endpoint permissions, and every call is recorded (parameters, payload, response) under API Logs for monitoring. Pace bulk writes and use JSON:API pagination on list endpoints.
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 Gatekeeper 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 Gatekeeper 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.
Gatekeeper
connected
Supabase
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Gatekeeper 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 · Gatekeeper ⇄ 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.
Gatekeeper SupabaseCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Gatekeeper and Supabase integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Gatekeeper and Supabase: authenticate both systems, choose the objects to sync (such as Gatekeeper's Vendors (Suppliers) and Files), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Change detection on Gatekeeper: No native developer webhook subscription API and no database change-data-capture log; detect changes by polling the JSON:API list endpoints filtered and sorted on updated-at timestamps. Gatekeeper's own event automation - Workflow Engine phase transitions and Interconnect process orchestration - runs inside the platform rather than as a subscribable webhook stream. On Supabase: Log-based CDC via Postgres logical replication, the same WAL feed that powers Supabase Realtime; database webhooks can also fire on row changes. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the Gatekeeper side: Contracts, Vendors (Suppliers), Files, Workflow form data, plus custom fields where Gatekeeper exposes them. On the Supabase side: Row Level Security Policies, JSONB Columns, Database Functions, Storage Object Metadata. 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 Gatekeeper and Supabase: React to changes as they happen; One integration pattern for the whole stack; Read Gatekeeper with a query. Updates in Gatekeeper arrive as row changes in Supabase, so triggers, jobs, and services can respond in near real time.
-
Gatekeeper: RESTful API following the JSON:API specification, tenant-scoped with interactive docs at {tenant}.gatekeeperhq.com/api_docs and a published Postman collection. The API is dynamic: it exposes the standard Contract and Vendor objects plus any custom data groups and workflow-form data configured in the tenant. Authentication: API keys created and managed under Configuration > API Keys and passed as a token; each key carries granular per-endpoint permissions set to read-only or write, so access is scoped per object. Multiple keys can be issued and revoked independently. 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.
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
CSA STAR
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 441 integrations available for Gatekeeper and Supabase.
Popular · 4 of 441
No integrations match .
