Supabase + Make Integration Guide
Supabase database webhooks can fire a Make scenario every time a row is inserted, updated, or deleted. This connection turns your Supabase database into a trigger for any automation — syncing data to external CRMs, sending notifications, updating spreadsheets, and orchestrating multi-step workflows without additional backend code.
Why Supabase + Make?
Supabase's database webhooks (powered by pg_net) can send an HTTP POST to any URL when your data changes. Make's Custom Webhook trigger receives this payload and can execute any sequence of Make modules — connecting to 1,500+ services. This combination is powerful for ops-heavy workflows: syncing your database to Google Sheets for reporting, notifying your team in Slack when a new customer signs up, or triggering a document generation workflow when an order is placed.
Setting up the integration
In Make, create a scenario with a Custom Webhook trigger and copy the URL. In Supabase, go to Database → Webhooks → Create a new webhook. Choose the table and events (INSERT, UPDATE, DELETE) that should trigger it. Set the webhook URL to your Make webhook URL. Supabase will POST the old and new record data as JSON. In Make, run the scenario once to receive the Supabase payload — Make auto-detects the structure and exposes all fields.
Data sync patterns
Common Supabase → Make patterns: new row in users table → Make adds row to Google Sheets CRM report; order row status changes to "shipped" → Make sends shipping notification email + updates Airtable; new support ticket inserted → Make creates Jira issue + notifies Slack channel. The reverse also works: Make can call Supabase's REST API (or RPC functions) to write data back — keeping external systems and Supabase in sync bidirectionally.
Real-world use cases
App Studio uses Supabase + Make for: automated reporting (nightly Make scenarios that query Supabase via API and populate Google Data Studio sheets), customer success workflows (new subscription in Supabase → Make creates HubSpot contact + sends personalised welcome sequence), and operational alerts (Supabase webhook on critical table updates → Make sends SMS via Twilio to on-call team). These flows run 24/7 without any infrastructure management.
Common pitfalls
Supabase webhooks deliver at least once — your Make scenario should be idempotent (safe to run twice for the same payload). Make's free plan has a limited number of operations per month and scenarios run sequentially, not in parallel — for high-volume event streams, consider upgrading or batching events. Supabase webhooks time out after 5 seconds; Make's webhook acknowledgment happens immediately, so you won't hit this limit. Secure your Make webhook URL with a secret query param and verify it in a Make filter.
What you can build
- Database-driven automation
- CRM sync
- Reporting pipelines
- Customer success workflows
- Operational alerts
Ready to build with Supabase + Make?
App Studio has built production apps on this exact stack. We can ship your project in 4–8 weeks and handle the full integration — architecture, setup, and launch.
Want expert help with this integration?
Book a free consultation →