Blog

Trigger a Workflow from a Supabase Database Webhook

Tutorial

·

Quick answer: To trigger a workflow from a Supabase database webhook, add the Supabase Trigger to a BuildShip workflow, sign in to Supabase with OAuth, enter your project reference, then pick an event (insert, update or delete), a schema and a table, and click Connect. BuildShip creates the database webhook in your Supabase project for you, so there is no endpoint to copy and no function to write. Map the payload to your workflow inputs, ship the workflow, and every matching row change starts a run you can inspect step by step.

Trigger a workflow from a Supabase webhook: Supabase and BuildShip tutorial cover with the BuildShip node library

What a Supabase database webhook does

A Supabase database webhook sends an HTTP request to a URL whenever a row is inserted, updated or deleted in a table. The payload describes what happened: the event type, the table and schema, and the row itself. For updates, Supabase sends the new row as record and the previous version as old_record, so you can see exactly what changed.

That makes webhooks a good fit for event-driven work:

  • A new row in support_tickets starts an AI step that classifies urgency.

  • A new user signs up, so you send a welcome message and create records in other tools.

  • An order row changes to paid, so you generate an invoice and notify your team.

  • A row is deleted, so you remove related files and records.

Normally you would create the webhook in the Supabase dashboard and point it at a function you host. With BuildShip, the trigger creates the webhook for you.

Before you start

You need three things:

  • A BuildShip workspace. You can start a 7-day trial (a card is required).

  • A Supabase project, and its project reference from the Supabase dashboard.

  • A table to watch. To react to sign-ups, use the auth schema and the users table.

If your workflow will also read or write data, the Supabase nodes connect with your project URL and API key. The Supabase integration page lists them.

Step by step: connect the Supabase Trigger

  1. Create a new workflow in BuildShip. Open the Connect tab, click Add trigger and choose Supabase Trigger from the trigger library.

  2. Authenticate. Click the fingerprint icon and you are sent to Supabase to grant permissions. The trigger uses OAuth, so you do not paste in an API key. When the red fingerprint icon turns green, you are connected.

  3. Enter your Project Reference. It is the unique ID for your project in the Supabase dashboard.

  4. Choose the Event that should start the workflow: insert, update or delete.

  5. Set the Table Schema. This is the Postgres schema the table lives in, which is public for most tables.

  6. Enter the Table Name.

  7. Click Connect. If everything worked, the button shows success.

BuildShip has now created a database webhook in your Supabase project. To check, open your Supabase project, go to Integrations, then Webhooks. You should see a webhook with the same endpoint shown in the post-connection preview, subscribed to the same events.

Map the webhook payload with Get Data

Supabase sends a different payload for each kind of event, so it helps to see a real one before you build.

  1. Trigger the event once. For an update trigger, edit a row in your table.

  2. In the trigger preview, click Get Data. BuildShip fetches the latest data for the selected event type.

  3. Pick the fields you need and add them to the workflow inputs. They are mapped for you.

Because this is an event-based trigger, there is no output mapping. The workflow does not send a response back to Supabase, so any result goes back through a Supabase node, as in the example below.

Build the workflow: classify new support tickets

Here is a small example. A new row lands in support_tickets, and the workflow decides how urgent it is and saves the answer.

  1. Inputs. Map the ticket fields from the trigger data, such as the ticket ID, subject and message.

  2. Branch. Add a Branch node that continues only if the ticket has no urgency yet. This matters if your trigger listens for updates, because your own write would start the workflow again.

  3. AI step. Add an AI node with a short instruction, such as “Rate this ticket as low, normal or urgent, and explain why in one sentence.” Keyless AI nodes run on your BuildShip credits, or you can use your own provider key.

  4. Write back. Add the Update Row node from the Supabase nodes to save the urgency to the same row. There are also Create Row, Get Row, Delete Row and Postgres RPC nodes, plus variants that use a token, if you need other operations.

  5. Notify. Add any node from the library to alert your team, such as an email or messaging step.

If you would rather start from a description, click Build with AI to open Compass, BuildShip’s AI builder. Tell it what the workflow should do, and it builds the flow on your canvas. You can then test it and edit any step.

Need something that is not in the library? Ask AI to generate a custom node, or open the code of any node and change the JavaScript or TypeScript yourself.

Test, ship and debug

  1. Use the test panel to run the workflow with the data you captured through Get Data.

  2. Click Ship to make the workflow active.

  3. Insert or update a row in Supabase.

Then open the logging panel at the bottom of the workspace. You can view logs for the whole workflow or switch to the Node view to see one step at a time. Test runs show live logs, and production logs usually appear within about 45 seconds. Use the refresh icon to load them straight away. To log your own values, add a Log Message to Console node or call logging.log in a node’s code.

Why use a workflow instead of an Edge Function

A Supabase Edge Function is a good choice when the reaction is one small piece of code. A BuildShip workflow helps when the reaction has several steps:

  • Many steps in one place. An AI call, a branch, a database write and a notification live on one canvas, with logs for each step.

  • Full code access. Every node is editable JavaScript or TypeScript, so you are never stuck at the edge of a visual builder.

  • Team access control. Role-based access control separates who can view a workflow, who can edit it and who can ship it.

  • Your own Google Cloud. Workflows run on Google Cloud, and you can run them in your own Google Cloud project.

  • Agents. When a row change needs judgement, a workflow can hand the job to an AI agent built with Agent Max, which can use your other workflows as tools.

FAQ

Do I need to write a Supabase Edge Function?

No. The Supabase Trigger sets up the database webhook for you. You sign in with OAuth, choose the event, schema and table, and click Connect.

Which events can start the workflow?

Inserts, updates and deletes on the table you choose. To react to new sign-ups, set the schema to auth and the table name to users.

How can I check that the webhook was created?

Open your Supabase project and go to Integrations, then Webhooks. You should see a webhook that uses the endpoint shown in the BuildShip trigger preview, with the same event subscriptions.

Can I read and write Supabase data in the same workflow?

Yes. Use the Supabase nodes, such as Get Row, Create Row, Update Row and Delete Row, in the same flow. They connect with your Supabase project URL and API key.

How much does it cost to try?

BuildShip plans start with a 7-day trial, and a card is required to start it. See the pricing page for plans and credits.

Start building

Open a workflow, add the Supabase Trigger and change a row. Start your 7-day trial (a card is required) to try it on your own project. If you also use Firestore, see how BuildShip works with Firestore.

You might also like

All it takes is an idea.

Imagine. Build. Ship.

Subscribe to our newsletter

Stay in the loop with product updates and news.

© 2026 BuildShip, Rowy Inc.

All it takes is an idea.

Imagine. Build. Ship.

Subscribe to our newsletter

Stay in the loop with product updates and news.

© 2026 BuildShip, Rowy Inc.

All it takes is an idea.

Imagine. Build. Ship.

Subscribe to our newsletter

Stay in the loop with product updates and news.

© 2026 BuildShip, Rowy Inc.