Resources · Make integration

Baserow Make integrationAutomate Baserow with Make.

What if your Baserow rows filled themselves in? The Baserow Make integration gives you nine modules, the bricks you chain into a scenario, and Make runs that scenario for you on a schedule. This page shows what each one does and walks you through the first build.

Try the Baserow integration on MakeSee the 9 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Baserow Make integration actually do?

It links your Baserow base to Make, the tool that runs your automations, so a change in a table can set off a chain of actions without anyone clicking. Baserow keeps the data. Make watches it, reads it, writes back to it, and passes it along to the other apps you already use.

Three shapes cover most of what teams build. The first is intake: a request lands in your table, Watch Created Rows picks it up and Create a Row opens the matching record in your delivery table, so nothing gets retyped between the two.

The second is upkeep. List Rows pulls a page of rows on the schedule you set, Get a Row fetches one record when you already know which, and Update a Row writes the result back. A support team uses it to keep ticket rows aligned with whatever the helpdesk says.

The third is paperwork. Upload a File drops a document into the base, so the signed quote sits next to the client row instead of in someone's inbox, and Delete a Row closes the loop when a record has to go.

What the integration will not do: it works on rows and files, nothing else. Everything the listed modules leave out goes through Make an API Call, which knocks directly on the Baserow API, the technical door other tools use to reach the product. It reuses the connection, meaning your Baserow account linked to Make once and shared by every module. Baserow also runs on n8n, so if the choice is still open, read n8n vs Make and the Baserow n8n integration. On budget, Make counts operations, one per module run, and Make pricing shows how that adds up.

Connect

How do you connect Baserow to Make?

  1. 01

    Start the connection from a module

    Drop any Baserow module into a scenario and click Create a connection. Make offers a Connection name field, optional but worth filling if you juggle several Baserow bases. On the requirements side, a Baserow account is all you need.

  2. 02

    Create a database token in Baserow

    In Baserow, click your Workspace at the top left, open My settings, then Database tokens. Hit Create token+, give it a name, pick the workspace, and create it. The three dots to the right of the token reveal the Token value to copy.

  3. 03

    Paste the token and save

    Back in Make, paste that value into the Baserow API token field. The Baserow API URL field already holds a default: leave it alone if your base lives on baserow.io, then click Save. Confirm access if Make asks, and every Baserow module reuses that connection.

First scenario

Build your first scenario, step by step

GoalWhen a new row is created in Baserow, Make opens the matching record in a second table.

  1. 01

    Create the scenario

    From the Scenarios page in Make, create a new scenario and click the + to place the first module. An empty canvas with one circle in the middle is exactly what you want at this point.

  2. 02

    Add the trigger

    Search Baserow by name, pick Watch Created Rows, and click Create a connection if your account is not linked yet. The clock badge on the circle means Make will go and look, it does not wait to be called.

  3. 03

    Point it at the right table

    Fill the module fields. Once the connection exists, Make reads your Baserow account and lists what it can see, so you pick the table from a menu instead of typing a reference you half remember.

  4. 04

    Add the action

    Click the + on the right of the trigger and add Create a Row. Map the values coming out of the first module onto the new row, and the second table fills itself.

  5. 05

    Test with Run once

    Click Run once, then create a row in Baserow. Make executes the chain a single time and shows the bundles each module received, a bundle being one item on the move, here one row.

  6. 06

    Schedule it and switch it on

    Open the clock on the first module and set how often Make should look, every 15 minutes out of the box. Flip the scenario on and it keeps running without you.

Triggers

What starts a Baserow scenario

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

Baserow1Watch Created Rows

Watch Created Rows

Scheduled trigger

In Make“Trigger when new rows are created.”

This is the one module that can make a Baserow scenario start by itself. It watches a table and hands each new row to the rest of the chain, one row per bundle, so a line someone typed two minutes ago becomes the input of your automation.

How it fires
on a schedule. Make checks the app on the scenario's schedule, so new rows arrive in batches rather than the second they appear.
When to use it
a table your team or a form writes into, where every new line should set something off.
Watch out
it reacts to rows being created, not to rows being edited. A value corrected an hour later will not wake the scenario.
Modules

What Baserow can do inside a scenario

Baserow gives you 8 modules in 3 groups. For each one: what it does for you, when to reach for it, and what to watch out for.

Actions

6 modules
Baserow1

Create a Row

Action

In Make“Creates a new row.”

It writes a new line in a Baserow table from whatever the previous module passed along. One run, one row, and the base fills itself while your team is busy elsewhere.

When to use it
a form answer, a new order or an inbound email that has to exist as a record before anyone can work on it.
Watch out
it adds without looking. If the same row can arrive twice, check with List Rows first.
Baserow2

Delete a Row

Action

In Make“Deletes an existing row.”

Delete a Row takes a line out of a table for good. It keeps a working table short: what has been processed leaves, and what stays is what still needs attention.

When to use it
a queue table where a record has no reason to sit around once the job behind it is finished.
Watch out
a scenario has no undo button. Try it with Run once on a row you can afford to lose.
Baserow3

Get a Row

Action

In Make“Finds a single row in a given table.”

You give it the reference of one record and it hands back that row, so the rest of the chain works with real values instead of guesses. One row in, one bundle out.

When to use it
you already know which record matters and you need what it holds before writing anywhere else.
Watch out
one row is all it returns. Several at once is the job of List Rows.
Baserow4

Make an API Call

Action

In Make“Performs an authorized API call.”

This one is the escape hatch. It sends a request you write yourself to the Baserow API, through the connection already in place, and covers what the eight other modules leave out.

When to use it
what you need exists in Baserow but has no module of its own in Make.
Watch out
nothing is filled in for you here, so keep it for the cases a listed module genuinely cannot handle.
Baserow5

Update a Row

Action

In Make“Updates an existing row.”

Rather than stacking a new line next to the old one, this module edits the record in place. The row grows over time instead of turning into three near-identical copies.

When to use it
a status that moves forward, a total to recalculate, a detail that finally arrived.
Watch out
it has to know which row to touch, so put Get a Row or List Rows in front of it.
Baserow6

Update a File

ActionIn the docs only

Make lists this module for Baserow without saying what it changes, so the honest answer is that its behavior is not documented. The name places it on the file side of the app, next to Upload a File.

When to use it
once you have watched it run on a table you can afford to throw away.
Watch out
undocumented means unpredictable. Keep it out of any scenario that touches records you could not rebuild.

Searches

1 module
Baserow7

List Rows

Search

In Make“Finds a page of rows in a given table.”

List Rows scans a table and hands back whatever it finds there, page by page. Zero, one or many can come back, each as its own bundle, and every module placed after it runs once per bundle.

When to use it
a recap to assemble, or a check to run when you do not know in advance which records match.
Watch out
each bundle costs an operation downstream, so a wide search burns through a plan faster than expected.

Other modules

1 module
Baserow8

Upload a File

Action

In Make“Uploads a file.”

Files travel too. Upload a File pushes a document into Baserow, which is how a contract ends up stored next to the record it belongs to instead of in a folder nobody opens.

When to use it
a signed quote, a photo taken on site, a report the scenario generated a step earlier.
Watch out
the Free plan of Make caps a file at 5 MB and transfer at 512 MB, so heavy attachments need a paid plan.
Need help

Need help automating Baserow with Make?

A person reads every message.

FAQ

Questions people ask next

01Is the Baserow Make integration free?
Yes. Baserow counts as a standard app in Make, and standard apps are included on every plan, Free included, alongside more than 3,000 others. The Free plan gives you 2 active scenarios, a 15 minute gap between two scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of transfer. What you actually spend is operations: one module running on one item is one operation, so a scenario that touches many rows eats the allowance faster than one that touches a few. What Baserow itself costs is a separate matter.
02What do you need to connect Baserow to Make?
A Baserow account and a database token, nothing else. The token is created inside Baserow: you open your workspace settings, go to Database tokens, give it a name, attach it to a workspace, then use the three dots to copy the token value. In Make, that value goes into the Baserow API token field of the connection. The Baserow API URL field is already filled for baserow.io, and only a self-hosted instance needs its own address there. Nothing to install on either side, and one connection serves every Baserow module you add.
03Does the Baserow trigger react in real time?
No, and it is better to know before you build. Watch Created Rows is a scheduled trigger: Make checks the app on the scenario's schedule instead of being called by Baserow. A fresh scenario looks every 15 minutes, which is also the floor on the Free plan, while paid plans go down to 1 minute. Baserow offers no instant trigger in Make, so nothing fires the second a row appears. For back office work the gap goes unnoticed. If a customer is watching the screen, build around it.
04What if a Baserow module is missing?
Use Make an API Call. It belongs to the Baserow app itself, it borrows the connection you already created, and it reaches points of the Baserow API that have no dedicated module in Make. That is the bridge between the modules on the list and everything else the product can do. Make's documentation publishes no limit for this app, so nothing written caps how many rows you can touch: your plan and its operations are the real ceiling. And if a whole area of the process lives outside Baserow, another app in Make takes over.
05Make or n8n for Baserow?
Both cover Baserow, so the decision usually comes down to who touches the automation once it exists. n8n opens up when a workflow needs custom code or lives on infrastructure your team already runs, and it rewards people comfortable reading and writing logic themselves. Make keeps everything inside the browser: modules use plain names, connections are one click, and a colleague can open a scenario months later without a handoff document. Neither tool changes what Baserow itself can do. If the automation has to survive after the person who built it moves on, that is the question worth answering first.
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