Supabase · Row added, changed or deleted — The moment a row changes, through a Supabase database webhook — starts a run as soon as Supabase sends the change. It is an instant trigger — see How instant triggers work. Supabase sends changes only to a webhook set in your project, so you paste Bizomate's address and a secret there once.

To check a table every few minutes instead, with nothing to set up in Supabase, use New row.

Who can do this

Workspace Admins and Editors, on every plan. Viewers see the trigger and its status, but not the secret.

Before you start

  • A Supabase connection in this workspace, for the table list — see Connect Supabase.
  • Rights in your Supabase project to create a database webhook.

Steps

In Bizomate

  1. Open the workflow in the designer and open the trigger picker. Under Supabase, select Row added, changed or deleted — Supabase · instant.
  2. Choose the Connection, then the Table — empty takes any table the webhook sends.
  3. In When a row is, choose Added, Changed, Deleted or Any.
  4. Below, One step in Supabase says what to do there: Supabase sends row changes only to a webhook set in your project. In Supabase › Database › Webhooks, create a webhook on the table for the events you want: method POST, this address as its URL, and an HTTP header named X-Bizomate-Secret holding the secret. Save. Bizomate takes only deliveries that carry the secret.
  5. Beside Webhook address, select Copy.
  6. Beside Secret, select Copy — Shown once — copy it now. Bizomate checks every event against it. Keep it until you have pasted it into Supabase; once you leave the trigger, it shows only as dots.

In Supabase

  1. Open Database › Webhooks and select Create a new hook.
  2. Name it — Bizomate bookings — and choose the Table and the Events — Insert, Update, Delete.
  3. Choose HTTP Request, method POST, and paste the address as the URL.
  4. Under HTTP Headers, add a header named X-Bizomate-Secret and paste the secret as its value.
  5. Select Create webhook.

Back in Bizomate

  1. Publish the workflow.
  2. Add or change a row in the table. Add or change a row in the table in Supabase; it appears here within seconds.

What happens next

  • Each change starts one run, with {{ trigger.event }} (insert, update or delete), {{ trigger.table }}, the row's columns under {{ trigger.row.guest_name }}, and — for a change or a deletion — the row as it was under {{ trigger.oldRow }}.
  • Every delivery is checked. One without the secret in its X-Bizomate-Secret header is answered 401 and starts nothing.
  • The webhook can send more than this trigger takes. Changes to another table, or of another kind, are ignored.

Good to know

  • Lost the secret? Beside the dots, select New secret, confirm with Make a new secret, and paste the new one into the webhook's X-Bizomate-Secret header in Supabase. Until you do, the webhook's deliveries are refused.
  • One workflow, one address. Two workflows on the same table's changes need two webhooks in Supabase, one each.
  • Runs start in Production and count in the month's allowance.

If something goes wrong

What you see Why What to do
Nothing arrives The webhook is not set, or not for this table and event. Check Database › Webhooks in Supabase.
Supabase's webhook log shows 401 The X-Bizomate-Secret header is missing or wrong. Paste the secret again — or, if it is lost, select New secret and paste that.
Changes arrive but start no run They are for another table, or another kind than When a row is. Set Table and When a row is to match.