Resources · Zapier integration

Baserow Zapier integrationAutomate Baserow with Zapier.

The Baserow Zapier integration gives you 3 triggers, 3 actions and 2 searches to read and write rows in your Baserow tables without code. Here is what each one does, what it costs in tasks, how fast it reacts, and where it trips people up.

See the 8 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Baserow Zapier integration actually does

Baserow is an open source database you build without code, made of tables and rows. Zapier links it to other apps: when a row appears or changes, it can start an automation, and other apps can create, update, look up or delete rows in your tables. Everything works at the row level, and every operation asks for a table ID.

Three things people actually get out of it. A live intake table: a form, a CRM or a shop sends each new entry into Baserow with Create Row, so nobody retypes anything. A status mirror: Row Updated watches a table and pushes the change to a chat channel or another tool when someone edits a status cell. A lookup before writing: Get Single Row fetches a known row so the next step can read its values, then Update Row writes the new ones back.

What it does not do matters just as much. Nothing here creates a table, a field or a database: the structure stays in Baserow, Zapier only moves rows. There is no instant trigger either, so every trigger waits for Zapier's next check. And you will not find a search by field value in the list: Get Single Row wants the row ID, and List Rows brings back a page of rows from a table.

If you are weighing tools, the same app has a Baserow n8n integration and a Baserow Make integration page, so you can compare the operations side by side.

Vocabulary

Zapier vocabulary in one minute

Eight words come back on every line of this page. Here they are in plain English, once.

Zap
The automation you build in Zapier: one trigger, then one or more actions that run each time the trigger event happens.
Trigger
The event that starts the Zap, like a new Baserow row. Once the Zap is switched on, Zapier waits for that event.
Action
What the Zap does after it starts: the step that writes, sends or changes something for you, like Create Row.
Task
What Zapier bills you for: one action that completes successfully. The number on your plan is a count of those.
Polling vs instant
A polling trigger is checked on a timer and Zapier keeps only what is new. An instant one is reported by the app the moment it happens.
Filter
A step that lets the Zap continue only when the incoming data matches your condition, and stops it otherwise.
Search step
A step that looks up something already stored in an app, so the steps after it can reuse what it found.
Connection
Your Baserow account linked to Zapier once, then reused by every step of every Zap that touches Baserow.
Cost

What a Baserow Zap really costs

Baserow is not a premium app on Zapier, so it works on the free plan. The bill is counted in tasks, and the rules are less obvious than they look.

  • Premium appNo, works on the free plan
  • Free plan100 tasks a month, two-step Zaps only
  • BilledEach successful action, never the trigger
  • Triggers on Baserow3, all polling

The trigger never costs a task, and neither do the checks Zapier runs to look for new rows. Each action that succeeds counts as one task; one that fails counts for nothing. In a Zap with three actions, each successful action is billed on its own, so it eats three times what a one-action Zap does. The free plan gives 100 tasks a month and unlimited Zaps, but only two steps per Zap. Add a filter or a search like Get Single Row and the Zap becomes multi-step, which needs a paid plan.

Connect

Connect your Baserow account to Zapier

  1. 01

    Open your connections

    In Zapier, go to the Apps page and click + Add connection. You need a Baserow account, plus read or write access on any table you do not own but want the Zap to touch.

  2. 02

    Pick Baserow

    Type Baserow in the search box of the dialog, select it, then click Add connection. A new browser tab then opens on the Baserow side, where the rest happens.

  3. 03

    Sign in and allow access

    Log in to Baserow in that tab and grant Zapier access to the account. The connection then shows up in your list, ready for every Baserow step you add later.

First Zap

Your first Baserow Zap, step by step

GoalEach new row in an intake table gets checked, and the ones marked as qualified are copied into a second table.

  1. 01

    Create the Zap

    Start a new Zap and pick Baserow as the app that starts it, with Row Created as the event. Choose your Baserow connection.

  2. 02

    Point it at the table

    Paste the Table ID of your intake table, the number shown between brackets when you click the three dots next to the table name in Baserow.

  3. 03

    Test the trigger

    Run the test: Zapier brings back the three most recent rows of that table, so you can pick a real one to map the next steps on.

  4. 04

    Add the filter

    Add a Filter step, choose the status column you created in your table, a text rule and your own value, here Qualified. This makes the Zap multi-step, so a paid plan.

  5. 05

    Add Create Row

    Add Baserow again with Create Row, enter the Table ID of the target table, and map each field from the trigger row. Test the step.

  6. 06

    Publish

    Read what each test returned, then click Publish. From then on, new rows are picked up at your plan's check interval, with no further clicks.

Triggers

The 3 Baserow triggers

3 events start a Zap when something happens in Baserow. Zapier checks for them at the interval your plan allows.

1

Row Created

Polling trigger

In Zapier“Trigger when new row is created.”

Starts your Zap each time a row is added to the Baserow table you chose. From there, a fresh entry can be copied, announced or enriched elsewhere without anyone retyping it.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
a form or a teammate fills a table and the rest of your tools need to hear about each new entry.
Watch out
it asks for the Table ID, the number between brackets you see behind the three dots next to the table.
2

Row Created or Updated

Polling trigger

In Zapier“Trigger when a new row is created or an existing one is updated.”

Fires for both events at once: a brand new row, or an edit to a row that already exists in the table. It is the broad net, useful when you care about the latest state of a row rather than how it got there.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
you keep another tool in sync with a Baserow table and want every addition and every correction to follow.
Watch out
if a later step of the same Zap edits a row in this very table, the edit sets the Zap off again, in a loop.
3

Row Updated

Polling trigger

In Zapier“Trigger when an existing row is updated.”

Reacts only when an existing row changes, and ignores rows that were just created. That makes it the right starting point for anything driven by an edit: a status cell moved, an owner reassigned, a date filled in.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
a teammate changes a status in Baserow and someone else needs to be told without checking the table.
Watch out
any edit counts, so pair it with a filter on the field you care about, or the Zap runs on every small correction.
Actions

The 3 Baserow actions

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

1

Delete Row

Action

In Zapier“Deletes an existing row.”

Removes one row from a table. The Zap tells Baserow which table and which row to delete, both by their ID.

When to use it
a record is cancelled in its source app and should no longer sit in your Baserow table.
Watch out
the Row ID is required and the deletion is real, so test it on a copy of the table first.
2

Create Row

Action

In Zapier“Creates a new row.”

Adds a new row to the table you name and fills its fields with values from earlier steps. This is the action that turns form entries, orders or leads into Baserow data.

When to use it
collecting entries from another app into one table that your team works from.
Watch out
the Table ID is required, and it must be the target table, not the one your trigger watches.
3

Update Row

Action

In Zapier“Updates an existing row.”

Changes the values of a row that already exists, for example a status, an amount or a date, using values from earlier steps.

When to use it
a payment or a reply arrives elsewhere and the matching Baserow row should show it.
Watch out
it needs both the Table ID and the Row ID, so you usually place Get Single Row or a trigger that carries the ID before it.
Searches

The 2 Baserow searches

2 search steps look for data that already exists in Baserow, so a later step can use it.

A search step looks up something that already lives in Baserow and passes it on to the next steps. In the editor, Baserow's searches sit at the bottom of the Action event list, under SEARCH. Adding one makes the Zap multi-step. Baserow offers no find-or-create variant here. Three settings decide what happens next.

1

Get Single Row

Search

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

Fetches one row from a table when you already know its ID, and hands it to the following steps. It reads, it never writes.

When to use it
another app stores the Baserow Row ID and you need the current contents of that row before acting.
Watch out
it looks up by Row ID only, so it cannot find a row from an email or a name.
2

List Rows

Search

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

Returns a page of rows from the table you point it at, instead of a single one. The following steps can work from what comes back.

When to use it
a later step needs several rows of a table at once rather than one known record.
Watch out
it brings back a page, not necessarily the whole table, so do not count on it to read everything.

The three settings every search exposes

  1. Successful if no search results are found?
    Left on its default, a search that finds nothing stops the Zap there and the steps that needed it are skipped. Switched on, the Zap goes on empty-handed.
  2. Create X if it doesn't exist yet?
    This box turns a search into a find-or-create. Baserow does not offer that variant for its searches, so you will not see it on these two steps.
  3. If multiple search results are found?
    Three ways out when several items match: keep the first one, which is the default, stop the Zap, or pass all of them on at once.
When it breaks

When a Baserow Zap breaks

Zapier ties no help article to Baserow, so the failures below are the ones every Zap runs into, seen from a Baserow table.

Most problems come from what a Zap cannot see and from Zaps that feed themselves. If yours keeps failing, our Zapier troubleshooting page walks through the usual checks.

  • Old rows are never picked up

    A Zap only reacts to rows created or edited after you publish it. Rows already in the table stay where they are; moving that backlog is a separate job.

  • The Zap triggers itself in a loop

    Row Updated plus Update Row on the same table: each write looks like a new edit, the Zap starts again and burns through your task count fast.

  • A bulk import goes quiet

    Import a large batch of rows at once and the trigger suddenly returns a huge pile. Zapier's flood protection can hold that batch back.

  • The same row never runs twice

    Zapier remembers what it has already seen on a polling trigger, so a row that started the Zap once will not start it again as a new row.
Need help

Need help automating Baserow with Zapier?

A person reads every message.

FAQ

Baserow Zapier integration: common questions

01Is the Baserow Zapier integration free?
Yes, Baserow is not a premium app, so it works on the free Zapier plan. That plan gives 100 tasks a month and unlimited Zaps, but each Zap is limited to two steps, one trigger and one action. Adding a filter, a second action or a Baserow search such as Get Single Row turns it into a multi-step Zap, and multi-step Zaps need a paid plan. The cost is then counted in tasks, like any other app on the platform.
02How many tasks does a Baserow Zap use?
One task per action that succeeds, and nothing for the trigger. Zapier does not bill the checks it runs to look for new rows either, however often they happen. A Zap with Row Created and Create Row therefore costs one task per new row. A Zap that creates a row, then updates another, then sends a message costs three tasks per run. An action that fails is not counted against your plan.
03Is Baserow on Zapier real time?
No, all three Baserow triggers are polling triggers. Zapier asks Baserow for new or changed rows at a fixed interval set by your plan: every 15 minutes on Free, every 2 minutes on Professional, every minute on Team and Enterprise. On paid plans you can also run a check by hand from the editor. The type is decided by the app's own API, so there is no setting in the editor that makes a Baserow trigger instant.
04What does it take to connect Baserow to Zapier?
A Baserow account, and read or write access on any table you do not own yourself but want the Zap to touch. You add the connection once from the Apps page with + Add connection, sign in to Baserow in the tab that opens, and allow access. After that, every operation asks for a Table ID, which Baserow shows between brackets when you click the three dots next to a table.
05Why does a Baserow Zap keep running on its own?
Most likely it writes into the table its own trigger watches. Row Updated or Row Created or Updated sees the change made by Update Row in the same table, treats it as a fresh edit and starts the Zap again, which eats tasks quickly. Point the action at a different table, or add a filter that only lets through the edits you actually care about, so the Zap's own writes no longer qualify.
06What if the Baserow operation you need is not listed?
Then Zapier does not offer it for Baserow today. The integration covers rows only: three triggers on created or updated rows, three actions to create, update or delete a row, and two searches by Row ID or by page of rows. Creating tables or fields, or searching a row by a field value, is not part of it. The workaround is usually to chain a search and an action, or to look at another automation tool.
07Zapier, Make or n8n for Baserow?
It depends on your criteria rather than on a winner. On Zapier, Baserow works on the free plan, all three triggers are polled, and anything beyond one trigger and one action needs a paid plan. Make and n8n each expose their own set of Baserow operations, described on their own pages. Check first that the triggers, actions and searches you need exist on the tool, then weigh which tool your team already runs.
Same platform

Other docs you might need on this stack.

Browse all integrations