A Supabase connection lets the Supabase steps — Insert a row, Update rows, Upsert, Delete rows, Find rows, Call a function, Upload a file to storage and Get a signed URL — and the New row trigger work with your Supabase project.

Who can do this

  • Workspace Admins and Editors, on every plan.

Before you start

  • Your project's URL. In Supabase: your project › Project Settings › Data API (or API) › Project URL — https://abcdefghijklmnop.supabase.co.
  • A key, and which one. Under Project Settings › API Keys:
    • The anon (or publishable) key works within your row-level security policies — Bizomate sees and changes only what your policies allow it. Use it where you can.
    • The service-role (or secret) key bypasses row-level security — Bizomate can read and change every row. Use it only when the workflows need it.

Steps

  1. Select Connections in the bar at the top, then + Add connection.
  2. Under Database, select Supabase.
  3. In Connection name, type a name — for example Consulace bookings.
  4. In Project URL, paste the project's URL.
  5. In API key, paste the key. "A service-role key bypasses row-level security — Bizomate can read and change every row. Use the anon key with your own policies where you can."
  6. Optional: choose a date in This key expires on · optional.
  7. Leave Test the connection before saving ticked, then select Save connection.

What happens next

  • The connection appears under Database, and every Supabase step and the New row trigger list it under Connection.
  • Test reads the project's API description and says what it reached and which key it is, for example "Reached abcdefghijklmnop.supabase.co · 8 tables, service role key".

Good to know

  • The lists in the steps come from what the key can see. With the anon key, a table your policies hide is not listed.
  • A project on your own domain works too, as long as its address is https and on the public internet.
  • The key is never shown again; to change it, Reconnect and paste it again.

If something goes wrong

What you see Why What to do
Supabase refused it — "Supabase refused: Invalid API key. Check the connection's details on Connections." The key is wrong, or belongs to another project. Copy the key again from the same project.
"The project URL must be the project's https address — https://abcdefghijklmnop.supabase.co. Check it on Connections." The URL is missing https, or is not a URL. Paste the Project URL as Supabase shows it.
"Could not reach Supabase: …" The address is wrong, or the project is paused. Check the URL; restore a paused project in Supabase.
"… is not on the public internet …" The address is a private one. Use the project's public address.