SeaTable Zapier integrationAutomate SeaTable with Zapier.
The SeaTable Zapier integration gives you 3 triggers, 6 actions and 2 searches. New rows, changed rows and new files can start a Zap; Zaps can create, update, lock or delete rows and look them up. All three triggers are polled.
Verified Trustpilot reviews · AI, automation & growth agency
What the SeaTable Zapier integration actually does
SeaTable sits between a spreadsheet and a database: tables, typed columns, files and signatures in cells. The integration lets Zapier watch those tables and write into them, so rows move between SeaTable and your other tools without exports or copy and paste.
Three results teams usually build first. Approved rows that cannot drift: New Row starts the Zap, a filter keeps the approved ones, and Lock Row freezes them so nobody edits a figure after sign-off. A table fed by other tools: Create Row writes a row from whatever app starts the Zap, and Update Row corrects it later once you know its row ID. The right record, found first: Find Row looks up a row by a column value and, if you tick the box, creates it when it is missing.
What Zapier does not do here deserves a line too. The row triggers only read the first 1000 rows of a table, unless you point them at a view. A file upload does not count as an update for New or Updated Row. And no trigger is instant, so on the free plan expect up to fifteen minutes before a change is seen.
If you are comparing platforms, the SeaTable n8n integration and the SeaTable Make integration cover the same app with their own operations.
Zapier vocabulary in one minute
Eight words from the editor, in plain English.
- 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. Once the Zap is on, Zapier waits for it: here a new row, a changed row or a new file in a column.
- Action
- What the Zap does once started: the step that writes, sends or moves something for you, such as creating or locking a row.
- Task
- The unit Zapier bills: one action your Zap completes successfully. Your plan's allowance is a count of those.
- Polling trigger
- A trigger Zapier checks on a timer, keeping only what it has not seen yet. All three SeaTable triggers work this way.
- Instant trigger
- A trigger the app reports itself the moment the event happens, with no wait for a check. SeaTable has none on Zapier.
- Filter
- A step that lets the Zap go on only when what arrived meets your condition, and stops it otherwise.
- Search step
- A step that looks up something that already exists, here a row, so the following steps can use what it found.
What a SeaTable Zap really costs
Zapier bills completed actions. Watching your tables for new rows costs nothing, however busy they are.
- Trigger and checks0 tasks
- Each successful action1 task
- Free plan100 tasks a month, two-step Zaps, check every 15 min
- SeaTable on the free planYes, it is not a premium app
The trigger never costs a task, and neither do Zapier's checks of your base. Each action that succeeds counts once: create a row and then lock it, and that is two tasks per record. A failed action is not counted. The free plan gives 100 tasks a month, unlimited Zaps and a check every fifteen minutes, but only two-step Zaps. A filter, a second action or a search step makes the Zap multi-step, which needs a paid plan. SeaTable is not a premium app, so the free plan can use it.
Connect SeaTable to Zapier in three steps
- 01
Open your connections
In Zapier, open the Apps page of your account and click + Add connection. A connection is your SeaTable account linked once, then reused by every SeaTable step of every Zap.
- 02
Pick SeaTable
Search for SeaTable in the dialog, select it and click Add connection. A tab opens on the SeaTable side: sign in with an account that can reach the base and the tables you want to automate.
- 03
Grant access
Allow Zapier to use the account and the connection is ready to pick in any step. If the base belongs to a colleague, make sure your account can read it and write to it first.
Your first Zap: lock rows once they are approved
GoalEvery new row that meets your approval rule gets locked automatically, so nobody can change it afterwards.
- 01
Create the Zap
Start a new Zap, choose SeaTable as the app that starts it and New Row as the event. Pick the connection you added in the previous section.
- 02
Set the trigger
Choose the Table. If it holds more than 1000 rows, select a view with fewer rows or with the newest on top. Test: Zapier brings back the three most recent rows to map on.
- 03
Add the filter
From the plus icon, add a Filter and set the field, the rule and the value. A text rule only works on text, so pick the type that matches your column or nothing passes.
- 04
Add Lock Row
Add SeaTable with Lock Row, choose the same Table and map the row from the trigger into the Row field. Both are required.
- 05
Test, then publish
Run each step once and check that the test row is locked in SeaTable. Then click Publish. The filter makes it a multi-step Zap, so it needs a paid plan.
SeaTable triggers
3 events start a Zap when something happens in SeaTable. Zapier checks for them at the interval your plan allows.
New File/Image/Signature
Polling triggerIn Zapier“Triggers when a new file, image or digital signature is added to a specific column.”
Starts your Zap when a file, an image or a digital signature lands in a column you choose. It watches one asset column of one table, which makes it precise: other edits to the row are ignored.
New Row
Polling triggerIn Zapier“Triggers when a new row is created.”
Fires each time a row is created in the table you pick, and only then: later edits leave it quiet. It is the cleanest start for anything that should happen once per new record.
New or Updated Row
Polling triggerIn Zapier“Triggers when a row is created or updated. (File Uploads does not trigger this event)”
Reacts both to new rows and to changes on existing ones. Use it when a status column moving forward matters more than the creation of the row itself.
SeaTable actions
SeaTable gives you 6 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
API Request (Beta)
ActionIn Zapier“This is an advanced action to execute a SeaTable API call via Zapier on this base. This is useful if you would like to use an API endpoint like Create a new table that Zapier doesn't implement yet. You can get all possible requests and their parameters from the https://api.seatable.io.”
An advanced step that runs a SeaTable API call on your base, for things the ready actions do not do, creating a table for example. It asks for a method and an address.
/api-gateway/ and only base operations are allowed.Create Row
ActionIn Zapier“Creates a new row, probably with input from previous steps.”
Adds a new row to the table you choose, usually filled with data from earlier steps. It is the way to bring records from forms, shops or CRMs into a base.
Delete Row
ActionIn Zapier“Delete an existing row in a table.”
Deletes an existing row from a table. Useful for keeping a working table short once records have been handled somewhere else.
Lock Row
ActionIn Zapier“Lock a row to prevent further changes.”
Locks a row so it can no longer be changed. A simple way to freeze a record once it has been validated, signed or invoiced.
Unlock Row
ActionIn Zapier“Remove the lock from a row.”
Removes the lock from a row so people can edit it again. It pairs with Lock Row when a record has to be reopened for a correction.
Update Row
ActionIn Zapier“Updates an existing row, probably with input from previous steps.”
Changes an existing row, again with values from earlier steps, once you know which row it is.
SeaTable searches
2 search steps look for data that already exists in SeaTable, so a later step can use it.
A search step finds a row that already exists and hands it to the next steps. SeaTable's searches sit at the bottom of the action list in the editor, under SEARCH. Three settings decide what happens around the search.
Find Many Rows (With Line Item Support)
SearchIn Zapier“Finds a row using SQL Query search syntax. Optionally, create a row if none are found.”
Looks for every row whose chosen column matches your search term, and can return them together as line items for the following steps. You choose whether partial matches count and whether case matters.
Find Row
SearchFind or createIn Zapier“Find a row using SQL Query search synctax. Optionally, create a row if none are found.”
Finds one row from a column value and hands it to the steps that follow. The editor also offers it as Find or Create a Row: the same search with the create box ticked, not an extra operation.
The three settings every search exposes
- Successful if no search results are found?Left on its default, a search that finds nothing stops the Zap there and the dependent steps are skipped. Switched on, the Zap carries on empty-handed.
- Create X if it doesn't exist yet?Ticking it turns the search into a find-or-create: the setting above disappears and the step asks for the fields needed to create the missing row.
- 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 a SeaTable Zap breaks
The problems that come up are rarely bugs. They come from the row ceiling, file access and the way Zapier watches tables.
Zapier attaches no help article and no rate limit to SeaTable. The cases below combine what the trigger and action fields say with the general limits every Zap shares. Read them before you publish. If a run fails anyway, the Zapier troubleshooting page is the place to start.
New rows beyond the 1000th are missed
The row triggers read only the first 1000 rows. On a bigger table, pick a view with fewer rows or with the newest entries sorted to the top.File links that later steps cannot open
Without access to images, files and signatures, you only get internal links that need a login. Answer Yes to get usable links, valid for a few hours.An upload that triggers nothing
New or Updated Row ignores file uploads. To react to a new file or signature, use New File/Image/Signature on that column instead.A Zap that rewrites its own table
New or Updated Row plus Update Row on the same table: each update is a new change, which restarts the Zap and burns tasks. Write elsewhere or filter.Rows from before the Zap are ignored
A Zap only reacts to what happens after it is switched on. Existing rows stay as they are; bringing them in is a separate job.A bulk import held back
Pasting or importing thousands of rows at once can trigger Zapier's flood protection, which holds the batch rather than running every row.
Need help automating SeaTable with Zapier?
A person reads every message.
