Resources · Make integration

Supabase Make integrationAutomate Supabase with Make.

Can a database run part of your back office? The Supabase Make integration lets you build scenarios, automations that run without you, on top of your tables and files. You get 12 modules, the bricks you snap together: 1 trigger, 9 actions, 2 searches. This page shows what each does.

Try the Supabase integration on MakeSee the 12 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Supabase Make integration actually do?

It connects your Supabase project to Make so your data stops waiting on someone to click. Make covers the two halves of Supabase you actually use, the tables where your rows live and the storage buckets where your files sit. A change on one side can drive the other, and the modules on this page are the vocabulary you have for that.

Mirror what changes into a second table. Watch Events catches a row the moment it is created, updated or deleted, and Create a Row writes the matching line into a history table, so you keep a trail your app never had to build.

Give every file a home. Create a Bucket opens a storage space, Upload a File drops the document into it, and List Buckets tells you what already exists before you add one more. A support team parks signed forms that way, one space per customer.

Answer the how many question without opening a dashboard. Get Rows Count returns the size of a table, Search Rows pulls the rows that match a filter, and the rest of the scenario decides what to do with the answer.

What the list does not cover: no module creates a table or changes its columns, and the documentation states no size or volume limit for this app. When a job falls outside the 12 modules, Make an API Call reaches any endpoint of the Supabase API once your project is linked. Supabase lives outside Make too: read the Supabase n8n integration, weigh the two tools in n8n vs Make, and see what a plan costs on Make pricing.

Connect

How do you connect your Supabase project to Make?

  1. 01

    Grab your project ID and API key

    Both values live in your Supabase account. Open your project, click Project Settings and copy the Project ID. Then open Project Settings again, go to API Keys, scroll down to Secret keys and copy that key. This assumes an account with an organization and a project already in place.

  2. 02

    Add a Supabase module and open the connection

    In Make, add a Supabase module to a scenario, then click Create a webhook, the address Make opens so Supabase can call it, and Create a connection. A connection is your Supabase account linked to Make once and reused by every Supabase module after it. The Connection name field is optional.

  3. 03

    Paste the two values and save

    Drop what you copied into the Project ID field and the API Key field, then click Save. If Make asks you to confirm access to the account, accept. Nothing else to set up: the next Supabase module you add is offered the same connection.

First scenario

Your first scenario, step by step

GoalWhen a row changes in Supabase, Make adds a line to a history table.

  1. 01

    Create the scenario

    From the Scenarios page in Make, start a new scenario and click the + to place the first module. Search for Supabase by name and pick Watch Events.

  2. 02

    Link your project

    The first time, click Create a webhook and Create a connection, then paste your two values. Fill in the module fields after that: with the connection in place, Make lists what it can read in your project.

  3. 03

    Add the action

    Click the + on the right of Watch Events and add Create a Row. Map the values coming out of the trigger into the fields of the new row, so every change leaves a trace.

  4. 04

    Test with Run once

    Click Run once, the button that fires the scenario a single time, then change a row in Supabase. Make shows the bundles, the items traveling from one module to the next, and you read what arrived.

  5. 05

    Switch it on

    Happy with the test? Turn the scenario on. Supabase then calls Make on its own every time a row moves, with no interval to set, and the history table fills up while you work on something else.

Triggers

What starts a Supabase scenario?

1 module starts a scenario when something happens in Supabase. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Supabase as soon as it happens.

Supabase1Watch Events

Watch Events

Instant trigger

In Make“Triggers when a record has been created, updated or deleted.”

Watch Events sits on your data and starts the scenario the moment a record shows up, changes or goes away. No loop to program, no page to refresh, and nothing to click on your side.

How it fires
instant. Supabase calls Make through the webhook as soon as a record moves, so there is no interval to set and no table to poll.
When to use it
a table other people write into, sign-ups or orders placed from your app, where reacting late costs you something.
Watch out
creation, update and deletion all come through the same door. Check what actually changed before the next module acts on the record.
Modules

What Supabase can do inside a scenario

Supabase gives you 11 modules in 2 groups. For each one: what it does for you, when to reach for it, and what to watch out for.

Actions

9 modules
Supabase1

Create a Bucket

Action

In Make“Creates a new storage bucket.”

Opens a new storage bucket in your project, the container your files will land in, without leaving the scenario.

When to use it
a new client signs up and every document of theirs should sit in a space of its own.
Watch out
run List Buckets first when the same scenario can fire twice for one client, so you do not build the same space again.
Supabase2

Create a Row

Action

In Make“Creates a new row in an existing table.”

Writes one new row into a table you already have. That row is often the end product of the scenario: a lead, a log line, an order.

When to use it
a form filled somewhere else should leave a record in your own database rather than in a spreadsheet nobody owns.
Watch out
the table has to exist already, since no module in this list creates one.
Supabase3

Delete a Bucket

Action

In Make“Deletes a storage bucket.”

Removes a storage bucket from the project. A scenario has no undo button, so this one is worth a second look.

When to use it
a temporary space built for one import or one campaign, cleaned up once the job is done.
Watch out
put it behind a step that checks the name, never right after a trigger that can fire on any record.
Supabase4

Delete Rows

Action

In Make“Deletes all rows matching the filter.”

Wipes every row that matches the filter you set, in one pass. One row or the whole table, the filter decides.

When to use it
clearing a staging table before a fresh import, or removing the records of a customer who asked for it.
Watch out
try the same filter with Search Rows first and read what comes back. Deletion does not replay backwards.
Supabase5

Get a Bucket

Action

In Make“Returns detailed information about a storage bucket.”

Brings back the details of one bucket you name, so the rest of the scenario works on something solid instead of a guess.

When to use it
a branch that should only continue when the space it expects is really there.
Watch out
it reads one bucket at a time. For a sweep of the whole project, List Buckets is the one.
Supabase6

Get Rows Count

Action

In Make“Returns the number of rows in a table.”

Hands back a single figure: how many rows the table holds at that moment. Cheap to run, easy to read in a scenario.

When to use it
a total you want stored somewhere else, or a check before an import that must not double the size of a table.
Watch out
the count covers the whole table. For a slice of it, Search Rows and its filter fit better.
Supabase7

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Calls any endpoint of the Supabase API yourself, signed with the connection already in place. It is the way out when the other modules stop short.

When to use it
a corner of your project none of the listed modules touch, once you have the endpoint in front of you.
Watch out
this one asks you to read the Supabase API documentation and build the call. Keep it for the cases where the plain modules genuinely fall short.
Supabase8

Upload a File

Action

In Make“Uploads a file into a storage bucket.”

Sends a file into one of your buckets, so the scenario ends with the document stored where your app goes looking for it.

When to use it
an invoice, a site photo or a signed contract arriving from another app that belongs in your project, not in an inbox.
Watch out
the Free plan of Make takes files up to 5 MB. Worth knowing before you route scans through it.
Supabase9

Upsert a Record

Action

In Make“Creates a new record or updates an existing record.”

Keeps a record unique. Make creates it when it is missing, updates it when it is already sitting in the table, and you stop writing two branches for one job.

When to use it
a sync that runs again and again, where the same customer must not show up twice.
Watch out
try it on two or three records first. One pass can rewrite what was there.

Searches

2 modules
Supabase10

List Buckets

Search

In Make“Lists storage buckets.”

Returns the storage buckets of the project, one bundle per bucket, and the next module works through them one by one.

When to use it
an inventory of the spaces you own, or a check before a scenario creates one more.
Watch out
the answer is a list. Think that through before you chain a delete behind it.
Supabase11

Search Rows

Search

In Make“Lists rows based on a filter.”

Pulls the rows that match your filter and passes them on, one bundle per row.

When to use it
finding the record a scenario needs before it updates anything, or pulling a slice of the table for a report.
Watch out
an empty answer is a normal answer. Say what the scenario should do when nothing matches.
Need help

Need help automating Supabase with Make?

A person reads every message.

FAQ

Questions people ask next

01Is the Supabase Make integration free?
Yes. Supabase counts as a standard app in Make, so it is there from the Free plan and the app itself adds nothing to the bill. What the Free plan limits is everything around it: 2 active scenarios, a 15 minute minimum between two scheduled runs, meaning scenarios Make starts on a clock, 5 minutes of run time, files up to 5 MB and 512 MB of transfer. Every time a module works on one item it counts an operation, and operations are what your plan pays for. Paid plans bring the interval down to 1 minute, drop the ceiling on active scenarios and allow 40 minutes per run.
02What do you need to connect Supabase to Make?
A Supabase account with an organization and a project already created, plus two values copied from that project: the Project ID and the API Key. Both come from Project Settings, the key on the API Keys screen, at the bottom under Secret keys. On the Make side you add a Supabase module, click Create a webhook, then Create a connection, name the connection if you want one, paste the two values and save. Confirm access if Make asks for it. Every Supabase module you add later reuses that same connection, so this is a one time job.
03Does the Supabase trigger react in real time?
Yes. Watch Events is an instant trigger, so Supabase calls Make through a webhook as soon as a record is created, updated or deleted. You pick no interval and Make does not keep asking your tables whether something moved. The 15 minute floor of the Free plan applies to scheduled scenarios, which is a different subject. Two practical points: the scenario has to be switched on to hear anything, and the same trigger covers creation, update and deletion, so check what changed before the next module acts on the record.
04What if a module is missing or a limit gets in the way?
Make an API Call answers the first half. It performs an authorized call to any endpoint of the Supabase API with the connection you already set up, which covers what the listed modules leave out. For the second half, the Supabase documentation in Make publishes no figure for a limit on this app. The ceilings you will actually meet are the ones on your Make plan: run time, active scenarios, file size, transfer. Those move with the plan you pay for, not with the app, so check them before you route heavy files through a scenario.
05Make or n8n for Supabase?
It depends on the team more than on the app. Make gives you a visual editor where modules snap one after the other, a Free plan to test on, and the 12 Supabase modules described here. n8n also has a Supabase node, and a full comparison of the two tools lives elsewhere on the site. The question worth answering first is who will open this automation in six months and what that person is comfortable maintaining. Pick the tool they will not be afraid of, then build the same scenario in it.
Hack'celeration Lab

Get our weekly automation tips.

No spam. Unsubscribe anytime.

Same platform

Other docs you might need on this stack.

Browse all integrations