If you're building on Supabase, a lot happens inside your database every day: new user sign-ups, orders, form submissions, status changes. Email notifications for these events are easy to set up, but they're also easy to ignore. An email about a new order can sit unread in an inbox for hours. A text message usually gets read within minutes.
This post shows you how to connect Supabase database events to the DataFlows SMS API, so your team or your customers get an SMS the moment something important happens in your database. You'll learn what Supabase Database Webhooks are, why they pair well with SMS, and the exact steps to wire up a working notification flow using a Supabase Edge Function.
What Is Supabase SMS Notification Integration
Supabase SMS notification integration is the practice of connecting events inside a Supabase Postgres database, such as a new row insert, an update, or a delete, to an SMS API so a text message is sent automatically when the event occurs. Supabase provides Database Webhooks, a built-in feature that fires an HTTP request whenever a table changes. That webhook can call a Supabase Edge Function, which in turn sends a request to the DataFlows SMS API to deliver the text message.
This setup removes the need for a separate polling script or a third-party automation platform. The database change itself triggers the message, so notifications happen close to real time. Common examples include alerting a sales team when a new lead is created, telling a customer their order status has changed, or sending a one-time code when a user record is updated. Because the flow runs on Supabase's own infrastructure combined with the DataFlows API, it stays simple to maintain and easy to extend as new tables or event types are added.
Why It Matters for Australian Businesses
Australian businesses increasingly rely on Supabase to build products fast, from local marketplaces to healthcare booking systems to trades scheduling tools. When something time-sensitive happens in the database, such as a new booking, a failed payment, or a support ticket, the person who needs to know is often away from their inbox.
SMS reaches people wherever they are. Text messages are typically read within minutes of arriving. For a business with staff working in the field or operating outside normal office hours, that speed can be the difference between catching a problem early and finding out about it the next day.
Local delivery matters too. Sending SMS through an Australian provider like DataFlows means messages route through local carrier connections rather than international gateways, which helps with deliverability and keeps the sender experience consistent for Australian recipients.
There's also a cost side to this. Many teams start out sending notifications through a general automation platform that charges per task or per run. Calling the DataFlows SMS API directly from a Supabase Edge Function removes that extra layer, so you're paying for the SMS itself rather than for a workflow tool sitting in between your database and your customer's phone.
Key Benefits
Real-time alerts: Database Webhooks fire the moment a row changes, so the SMS goes out without waiting on batch jobs or scheduled checks.
No extra automation platform required: A Supabase Edge Function can call the DataFlows SMS API directly, keeping the stack simpler and easier to debug.
Works with any table: Webhooks can be attached to any table and any event type, insert, update, or delete, so the same pattern covers orders, bookings, support tickets, and account changes.
Local Australian sender IDs: Messages can be sent from a registered business name or a virtual number, so recipients recognise who the message is from.
Scales with usage: The same Edge Function and webhook pattern handles one notification a day or thousands, since the DataFlows SMS API is built to handle bulk sending.
Step-by-Step Guide
Before you start, sign in to your DataFlows dashboard and go to the Developer section to get your API Token. Keep this token private. You'll store it as a secret in Supabase, not in your database or client-side code.
Step 1: Create a Supabase Edge Function
In your Supabase project, create a new Edge Function, for example send-sms-notification. This function receives the webhook payload from Supabase and forwards the relevant details to the DataFlows SMS API.
const record = payload.record const message = `New order #${record.id} received from ${record.customer_name}` await fetch("https://api.dataflows.com.au/v1/sms/send", { method: "POST", headers: { "Authorization": `Bearer ${Deno.env.get("DATAFLOWS_API_TOKEN")}`, "Content-Type": "application/json" }, body: JSON.stringify({ to: record.notify_number, message: message, sender: "DataFlows" }) })
Step 2: Store your DataFlows API token as a secret
Add your DataFlows API token to your Supabase project's Edge Function secrets rather than hardcoding it. This keeps the token out of your source code and version control.
Step 3: Create a Database Webhook
In the Supabase dashboard, go to Database, then Webhooks, and create a new webhook. Choose the table you want to watch, for example orders, select the event type (insert, update, or delete), and set the webhook to call your Edge Function URL.
Step 4: Test the trigger
Insert a test row into the table, or update an existing one, and confirm the SMS arrives. Check the DataFlows dashboard to see the message logged with its delivery status.
Step 5: Add error handling and logging
Wrap the fetch call in a try/catch block and log failures so a failed SMS send doesn't fail silently. Check the response from the DataFlows API to confirm the message was accepted before treating the notification as complete.
Common Use Cases
Once the webhook and Edge Function are in place, the same pattern can be reused across different tables in your Supabase project. A few examples show how flexible this approach is in practice.
New lead alerts: When a row is inserted into a leads table from a website form, an SMS goes straight to the sales team so they can follow up while the lead is still warm.
Order status updates: When an order row's status column changes from processing to shipped, an SMS lets the customer know their order is on its way, without any manual step from staff.
Booking confirmations and reminders: A new row in a bookings table can trigger an immediate confirmation SMS, and a separate scheduled check can send a reminder closer to the appointment time.
Account and security alerts: An update to a user's email, password, or payment details can trigger a security notice SMS, giving the account owner a chance to react quickly if the change wasn't theirs.
Internal ops alerts: A row inserted into an errors or support_tickets table can notify an on-call staff member immediately, instead of waiting for someone to check a dashboard.
In each case, the underlying mechanism is the same: a Database Webhook watches a table, an Edge Function shapes the message, and the DataFlows SMS API delivers it. Only the table, the event type, and the message text change between use cases.
How DataFlows Helps
DataFlows gives Supabase developers a straightforward SMS API built for exactly this kind of event-driven notification. You send an HTTP request with a phone number, a message, and a sender ID, and DataFlows handles delivery through Australian carrier connections.
Beyond one-off transactional messages, DataFlows also supports Virtual Numbers for two-way conversations, Sender IDs so recipients see your business name, and Contact Lists if you want to combine event-based alerts with broader SMS Marketing or SMS Campaigns. For teams that also use OTP Verification, the same API token and account can handle both transactional Supabase alerts and verification codes, so you're not managing multiple SMS providers.
Because DataFlows' Supabase integration is documented with working code examples, most teams can get a first notification live in under an hour.
Best Practices
Filter events before sending: Only trigger the webhook for the specific insert, update, or delete events you actually need, rather than every change to a table, to avoid unnecessary messages.
Keep messages short and specific: Include only the details the recipient needs, such as an order number or a status, so the SMS stays within standard character limits.
Store phone numbers in a clean format: Save numbers in E.164 format, for example +614XXXXXXXX, in your database so they're ready to send without extra formatting logic.
Separate transactional and marketing sends: Use database-triggered SMS for transactional alerts and keep promotional messages in a separate SMS Marketing flow with proper opt-in and opt-out handling.
Monitor delivery in the DataFlows dashboard: Check delivery status regularly, especially after adding a new webhook, to catch formatting or configuration issues early.
Rotate your API token if it's ever exposed: If a token is accidentally committed to a repository or shared, generate a new one from the Developer section immediately.
Conclusion
Connecting Supabase database events to SMS notifications doesn't require a complex setup. With a Database Webhook, a small Edge Function, and a DataFlows API token, you can turn any row change into a text message that reaches the right person in minutes rather than hours.
Sign up at dataflows.com.au to get your API token and start sending SMS notifications from your Supabase project today.
You May Also Like
Supabase SMS Integration with DataFlows
SMS API Integration Guide
OTP SMS Verification
SMS Verification Using the DataFlows API
How to Send SMS with DataFlows and Zapier