Resources · Zapier integration

NocoDB Zapier integrationAutomate NocoDB with Zapier.

The NocoDB Zapier integration covers 1 trigger, 6 actions and 2 searches. Enough to react when a row is added or edited in a table, write rows one at a time or in bulk, and look a record up before touching it, all from a no-code editor.

See the 9 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the NocoDB Zapier integration does for you

NocoDB turns a database into tables you edit like a spreadsheet. Zapier links apps together without code. With the two connected, Zapier spots rows that are added or changed in a NocoDB table, and can create, update, delete or look up rows for you, in any table your account reaches.

Three outcomes cover most uses. Tables that talk to each other: New or Updated Record watches one table and Create Record writes the matching row into another, so an order logged by sales appears in the delivery table. No more duplicates: Create or Update Record compares a field you choose and updates the row that matches instead of adding a second one. Bulk work in one step: the two Advanced actions create or update several rows in a single action, handy when an earlier step hands over a whole list rather than one item at a time.

The gaps are worth knowing up front. There is only one trigger, so nothing fires on a deleted row, and it watches a single table per Zap. Every operation asks for a workspace, a base and a table, and the workspace choice only means something on NocoDB cloud: a self-hosted instance shows one option. If your project needs more than that, see the NocoDB n8n integration or the NocoDB Make integration.

Vocabulary

Zapier vocabulary in one minute

Eight words that come back in every block of this page.

Zap
The automation you build on Zapier: one trigger, then one or more actions that run each time the trigger event happens.
Trigger
The event that starts the Zap. With NocoDB, a row added or edited in the table you picked.
Action
What the Zap does once it has started: the step that creates, updates or deletes a row for you.
Task
The unit Zapier bills. One action completed successfully is one task, and your plan caps how many you get per month.
Polling vs instant
Polling: Zapier checks the app on a timer. Instant: the app tells Zapier right away. The NocoDB trigger is polling.
Filter
A step that lets the Zap continue only when the data meets a condition you set. Otherwise the run stops there.
Search step
A step that finds a row that already exists, so the steps after it can use or update it without guessing.
Multi-step Zap
Any Zap beyond one trigger and one action. A search, a filter or a second action makes it one, and a paid plan is then needed.
Cost

What it costs to keep running

The bill follows successful actions, not the number of Zaps.

  • Free plan100 tasks a month
  • Free plan Zap2 steps maximum
  • Premium appNo
  • Trigger typePolling

Watching a NocoDB table never costs a task, however often Zapier checks. Each action that goes through counts as one task, and one that fails is not counted. A Zap that searches a row and then updates it spends one task per action that succeeds. The free plan includes 100 tasks a month and unlimited Zaps, but each Zap stops at two steps. A search step or a filter makes the Zap multi-step, and that needs a paid plan. NocoDB is not a premium app.

Connect

Connect NocoDB to Zapier in 3 steps

  1. 01

    Add the connection

    On the Apps page of your Zapier account, click + Add connection. A dialog with a search box opens: type NocoDB and pick it from the list of apps that comes up.

  2. 02

    Sign in to NocoDB

    Click Add connection and sign in to NocoDB in the tab that opens. Use the account that can see the workspaces, bases and tables your Zaps will read or write.

  3. 03

    Grant access

    Allow Zapier into the account when NocoDB asks. The connection appears on your Apps page, and every NocoDB step of every Zap reuses it without a new sign-in.

First Zap

Your first Zap: from a confirmed order to a delivery row

GoalWhen an order row is added or edited in NocoDB and is confirmed, find the customer in another table and create a delivery row.

  1. 01

    Watch the orders table

    Start a new Zap with NocoDB and New or Updated Record. Pick the workspace, base, table and time field. Test: Zapier brings back the three most recent rows.

  2. 02

    Keep confirmed orders only

    Add a Filter. In Configure & test, choose the status field from the test row, the rule, and the value that means confirmed in your table.

  3. 03

    Find the customer

    Add Search Records from the SEARCH part of the event list, on your customers table, and map the customer from the order into it.

  4. 04

    Create the delivery row

    Add Create Record on the delivery table and map the order and the customer found. Write into a different table from the one you watch, or the Zap will loop.

  5. 05

    Test and publish

    Test every step, read what came back, then Publish. With a filter and a search this Zap is multi-step, so it needs a paid plan.

Triggers

The NocoDB trigger

1 event starts a Zap when something happens in NocoDB. Zapier checks for them at the interval your plan allows.

1

New or Updated Record

Polling trigger

In Zapier“Triggers when record is updated or created.”

Fires the Zap when a row is created or edited in the NocoDB table you chose, and passes that row to the steps after it. One trigger covers both cases, so a Zap built on it reacts to fresh rows and to corrections alike.

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
an event agency that wants each change to its guest list pushed to the catering table.
Watch out
it needs a created or last-modified time field in that table.
Actions

The NocoDB actions

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

1

Create Record

Action

In Zapier“Create a record to NocoDB table.”

Adds one new row to the table you pick, filled from whatever the earlier steps carried. The workhorse of most NocoDB Zaps.

When to use it
a coworking space that logs every new member request as a row in its members table.
Watch out
written into the table your trigger watches, it starts the Zap again.
2

Create Records (Advanced)

Action

In Zapier“Create multiple records.”

Writes several rows in a single action rather than one per run, for when an earlier step hands over a whole batch.

When to use it
a school that receives a class list at once and wants one row per student.
Watch out
test it on a small batch first, and check every row landed where you expected before going live.
3

Delete Record

Action

In Zapier“Delete a record on selected NocoDB table.”

Removes a row from the selected NocoDB table, the one an earlier step identified.

When to use it
clearing a lead from the prospects table once it has been copied into the clients one.
Watch out
the row removed is whichever one the earlier step picked, so test on a throwaway table before pointing it at real data.
4

Update Record

Action

In Zapier“Update a record on selected NocoDB table.”

Changes the content of one existing row, the one you point it to, without creating anything new.

When to use it
flipping a project row to done once the matching invoice is paid in another table.
Watch out
updating the table watched by New or Updated Record counts as an edit, so the Zap fires itself again.
5

Update Records (Advanced)

Action

In Zapier“Update multiple records on selected NocoDB table.”

Edits several rows of the selected table in one action, the bulk counterpart of Update Record.

When to use it
marking every stock line of a returned shipment as back in the warehouse.
Watch out
a bulk change on a watched table is a quick way to trigger a flood of runs; aim it at a table no Zap watches.
6

Create or Update Record

Action

In Zapier“Create or Update Record based on selected field.”

Checks the table for a row whose lookup field matches the value you send: if it finds one, it updates it, if not, it creates a new row.

When to use it
a supplier list fed from several sources that must keep one row per supplier.
Watch out
the Primary Lookup Field is required, and the value must match the row exactly for an update to happen.
Searches

The NocoDB searches

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

A search step creates nothing: it finds a row that already exists and hands it to the next steps. You pick it from the Action event list, under the SEARCH heading. Some action fields also offer + Add search step, which inserts one right before and wires it in.

1

Get Record by ID

Search

In Zapier“Get a record using record id.”

Fetches one precise row from a table using its record ID, the identifier NocoDB gives each row.

When to use it
an earlier step already carries the ID, and you need the rest of the row before acting on it.
Watch out
the Record ID is required; without it from an earlier step, use Search Records instead.
2

Search Records

SearchFind or create

In Zapier“Search one or more records in NocoDB.”

Looks through a table for one or more rows and returns them to the Zap. The editor also lists it as Find or Create Records in NocoDB if not found: same search, with the create box ticked.

When to use it
checking that a customer row exists before linking an order to it.
Watch out
the find-or-create line is not a separate operation.

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 and skips the steps that depended on it. Switched on, the Zap carries on empty-handed.
  2. Create X if it doesn't exist yet?
    Ticking it turns Search Records into a find-or-create: the setting above disappears and the step asks for the fields needed to create the missing row.
  3. If multiple search results are found?
    Three ways out when several rows match: keep the first one, which is the default, stop the Zap, or pass all of them on at once.
When it breaks

When it breaks

Zapier attaches no error specific to NocoDB. What goes wrong comes from how Zaps work, and one trap is sharper here because the trigger also fires on edits.

Three cases explain most of the surprises with a NocoDB Zap once it is live. If one keeps coming back, our Zapier troubleshooting page goes through the fixes.

  • The Zap edits itself into a loop

    Any Create, Update or Create or Update action aimed at the table New or Updated Record watches is a fresh edit there. The Zap restarts each time and burns through tasks.

  • Existing rows are never processed

    A Zap only reacts to what happens after you publish it. Rows already in the table do not start it, and handling that backlog is a separate job.

  • A big import is held back

    Import or bulk-edit many rows at once and the trigger suddenly returns a huge batch. Zapier's flood protection can hold that batch back rather than run it.
Need help

Need help automating NocoDB with Zapier?

A person reads every message.

FAQ

NocoDB and Zapier: the questions people ask

01Is the NocoDB Zapier integration free?
Yes, NocoDB is not a premium app, so it works on Zapier's free plan. That plan gives 100 tasks a month and unlimited Zaps, with a limit people miss: two steps per Zap, one trigger and one action. New or Updated Record followed by Create Record fits. Add a search, a filter or a second action and the Zap becomes multi-step, which needs a paid plan. NocoDB itself is not a premium app, so nothing else locks it.
02How many tasks does a NocoDB Zap use?
One per action that succeeds, none for the trigger. Checking a NocoDB table for new or edited rows costs nothing, however often Zapier looks, and an action that fails is not counted. In a Zap with several actions, each action that completes counts on its own. The trap is the loop: a Zap that updates the very table it watches restarts after each update and spends a task every time. Aim your actions at another table, or filter the runs out.
03Does NocoDB trigger Zaps in real time?
No. New or Updated Record is a polling trigger: Zapier asks NocoDB for new or changed rows at a fixed interval, NocoDB does not call Zapier itself. On the free plan that check runs every 15 minutes, on Professional every 2 minutes, and on Team and Enterprise every minute. A row edited just after a check waits for the next one. On paid plans you can also start a check by hand from the editor, which helps while you test the Zap.
04What do you need to connect NocoDB to Zapier?
A NocoDB account and a Zapier account. From the Apps page in Zapier, add a connection, choose NocoDB, sign in on the tab that opens and grant access. Then each step asks for a workspace, a base and a table. The workspace choice only matters on NocoDB cloud; on a self-hosted instance, a single option shows. For the trigger, the table also needs a created or last-modified time field, so add one before building.
05Why does a NocoDB Zap keep running on its own?
Because the trigger fires on edits as well as new rows. A Zap that starts on New or Updated Record and then updates, creates or upserts a row in the same table makes a change that the trigger picks up at its next check, and the cycle goes on. The cleanest fix is to write into a different table. If you must write to the same one, add a filter right after the trigger on a field that tells your team's edits apart from the Zap's, if the table has one, and let only the first kind through.
06What if the NocoDB operation you need is not there?
Then this integration cannot do it as it stands. On Zapier, NocoDB offers one trigger, six actions and two searches: create, update, upsert and delete rows, one by one or in bulk, and look them up by ID or by search. There is no trigger on deleted rows and no operation on the structure of a table. Either reshape the scenario around what exists, or look at another automation tool that connects NocoDB differently.
07Zapier, Make or n8n for NocoDB?
Weigh them on criteria, not on reputation. Zapier is the fastest to learn and covers rows well, with bulk actions and an upsert, but its only trigger is polling, every 15 minutes on the free plan, and it watches one table per Zap. Every step also asks for a workspace, a base and a table. This page only covers what Zapier offers, so compare what each one offers for NocoDB with the step your process cannot do without.
Same platform

Other docs you might need on this stack.

Browse all integrations