Resources · Make integration

SeaTable Make integrationAutomate SeaTable with Make.

Your SeaTable base can keep itself tidy while you work on something else. The SeaTable Make integration gives you 22 modules: 2 triggers that watch rows, 15 actions and 5 searches. This guide shows ops and data teams how to connect a base, build a first scenario and pick the right module.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the SeaTable Make integration do for you?

The SeaTable Make integration links your SeaTable bases to the other apps you use, without writing code. Make watches your tables for new or edited rows, then creates, updates, links or files rows for you. Each step is a module, one brick of the scenario, which is the automation you assemble in Make's visual editor.

Tie every new order to the right customer. Watch New Rows spots each order added to a table, Search Rows finds the matching customer, and Add a Row Link joins the two. Nobody links records by hand anymore.

Keep a safety net before a cleanup. Create a Snapshot saves the complete base, so a scenario that goes on to run Delete a Row has a copy behind it.

Get files to the people who need them. Upload a File/Image drops a document into a row, and Get the public URL from Asset Path returns a download link you can pass to an email or chat app.

Where the modules stop: they cover rows, links, locks, files, snapshots and collaborators. For any other part of the SeaTable API, Make an API Call reuses the same connection. Make's SeaTable documentation also warns that its text is AI-generated, so double-check critical details with SeaTable.

SeaTable has an n8n node too: the SeaTable n8n integration page covers it, and n8n vs Make sets the two tools side by side. Never opened the editor? Make training starts from zero.

Connect

How do you connect SeaTable to Make?

  1. 01

    Open the connection window

    Add any SeaTable module to your scenario and click Create a connection. A connection is your SeaTable account linked to Make once: every SeaTable module in your scenarios reuses it afterwards.

  2. 02

    Generate an API token in SeaTable

    On the SeaTable home page, hover over the base, open its options menu, expand Advanced and select API Tokens. Enter a name, choose the permission, generate the token and copy it.

  3. 03

    Paste it and confirm

    Back in Make, fill Connection name if you want a clear label (it is optional), paste the token and confirm. The documentation accepts an AccountToken, an APIToken or a BaseToken.

First scenario

Your first scenario: link each new order to its customer

GoalWhen a new row lands in your SeaTable orders table, Make finds the matching customer row and links the two.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the + in the middle. Search for SeaTable and pick Watch New Rows as the first module.

  2. 02

    Connect and choose the table

    Select your connection or click Create a connection. Once it exists, Make lists what it can read in the base, so you choose the orders table from a list instead of typing it.

  3. 03

    Look up the customer

    Click the + on the right of the trigger and add Search Rows on your customers table. Drag the customer value from the new order into the keyword: that drag is called mapping.

  4. 04

    Link the two rows

    Next, add Add a Row Link and map the order from the trigger and the customer found by Search Rows. Each bundle, one row passed along, gets its link. Watch New Rows ignores edits, so this link never restarts the scenario.

  5. 05

    Test with Run once

    Add a test order in SeaTable, then click Run once. Make runs the scenario one time and shows the bundles each module received, so you see whether the right customer came back.

  6. 06

    Schedule and switch it on

    Open the clock on the first module. A new scenario runs every 15 minutes by default, which is also the shortest interval on the Free plan. Keep it or adjust it, then switch the scenario on.

Triggers

What starts a SeaTable scenario?

2 modules start a scenario when something happens in SeaTable. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by SeaTable as soon as it happens.

SeaTable1Watch New Rows

Watch New Rows

Scheduled trigger

In MakeTriggers when a new row is created.

Watch New Rows picks up each row added to the table you choose and hands it to the rest of the scenario as a bundle. A form entry, an import or a colleague typing a line all start the same flow.

How it fires
scheduled. Make checks SeaTable on the scenario's schedule, every 15 minutes by default, so a new row waits for the next check instead of starting things the second it is saved.
When to use it
a table where each new line is a job to start, like a lead, a ticket or an order to confirm.
Watch out
edits to existing rows go unnoticed here; that is what Watch Updated Rows is for.
SeaTable2Watch Updated Rows

Watch Updated Rows

Scheduled trigger

In MakeTriggers when a row is created or updated.

Watch Updated Rows reacts to change: it passes a row along when someone edits it, and it also catches rows that were just created. It fits processes driven by a status or a value that moves over time.

How it fires
scheduled. Make checks SeaTable on the scenario's schedule, so an edit shows up at the next run rather than at the moment it is saved.
When to use it
a deal marked as won, a task set to done or a corrected address that another tool must receive.
Watch out
new rows count too, so running it beside Watch New Rows on the same table can send one row through twice.
Modules

What else can Make do in SeaTable?

SeaTable gives you 20 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

SeaTable2

Add a Row Lock

Action

In MakeAdds a row lock to one specific row.

Add a Row Lock places a lock on one specific row. Think of it as the automated way of flagging a line as settled once the scenario has dealt with it.

When to use it
after an invoice row or a signed contract has gone through your process and you want it marked as locked.
Watch out
the module needs to know which row to lock, so put a trigger or a search before it; Delete a Row Lock reverses it.
SeaTable3

Create a Row

Action

In MakeAppends a new row to the table.

Create a Row appends a new line to a table, filled with values mapped from earlier modules: a form reply, a paid order, a contact coming from your CRM.

When to use it
whenever SeaTable is where records from your other apps should end up.
Watch out
it does not check for duplicates. If the same record can arrive twice, run Search Rows first and create the row only when the search comes back empty.
SeaTable4

Create a Snapshot

Action

In MakeCreates a snapshot of the complete base.

Create a Snapshot saves a copy of the complete base, all tables included, at the moment the module runs. You get a point to fall back on, created by the scenario itself.

When to use it
as the first action of a scenario that deletes or rewrites a lot of rows.
Watch out
it captures the whole base, not one table, so place it once at the start and not after a module that returns many bundles, or it runs once per bundle.
SeaTable5

Delete a Row

Action

In MakeDelete a row.

Delete a Row removes one row from a table for good. Paired with a search, it clears test entries, cancelled requests or duplicates without anyone scrolling through the table.

When to use it
when a status or a search result tells you without doubt which row has to go.
Watch out
a deletion does not come back from Make. Run Create a Snapshot first and check the target row with Run once before you switch the scenario on.
SeaTable7

Delete a Row Lock

Action

In MakeRemoves a row lock from one specific row.

Delete a Row Lock lifts the lock from one specific row, the mirror image of Add a Row Lock.

When to use it
a locked record needs to reopen, for instance a quote sent back for changes or a file rejected at a review step in another app.
Watch out
if two scenarios lock and unlock the same rows, decide which one acts when, or they will keep undoing each other's work.
SeaTable8

Get a Row

Action

In MakeRetrieves all values of one specific row.

Get a Row fetches every value of one row you can already point to, and makes them available to the modules that follow. It returns a single bundle, never a list.

When to use it
another app hands you a row reference and you need its full content before sending an email or updating a CRM.
Watch out
without the row's identity it has nothing to fetch; to find a row by what it contains, Search Rows is the better choice.
SeaTable9

Get Metadata

Action

In MakeReturns the complete metadata of the base.

Get Metadata returns the complete metadata of the base: a description of how the base is built rather than the data stored in it. It serves scenario builders more than daily flows.

When to use it
you want to see what the base contains before mapping anything, or a scenario has to adapt to the base it works on.
Watch out
it gives no row content; to read data, reach for List Rows or Get a Row.
SeaTable10

Get the public URL from Asset Path

Action

In MakeReturns the public available download path for this file/image.

Get the public URL from Asset Path turns the path of a file or image stored in SeaTable into a public download link. That link can then travel into an email, a chat message or a client portal.

When to use it
a document attached to a row has to reach someone who has no SeaTable access.
Watch out
the link is public by design, so keep this module for files you are comfortable sharing outside the team.
SeaTable11

Link a Row

Action

In MakeSets up a link between two rows.

Link a Row also creates a link between two rows, and the official directory describes it in exactly the same words as Add a Row Link. Make simply lists both for SeaTable.

When to use it
a scenario you inherited already relies on it, or it fits your setup better after a side-by-side test.
Watch out
neither the directory nor the documentation says which one to prefer, so pick one, test it with Run once and stick with it across scenarios.
SeaTable12

Make an API Call

Action

In MakePerforms an arbitrary authorized API call.

Make an API Call sends a request to any endpoint of the SeaTable API, using the connection you already set up. It is the way out when none of the ready-made modules covers what you need.

When to use it
an operation that appears nowhere in the module list above.
Watch out
this is the one technical module of the app. You write the request yourself, so keep the SeaTable API documentation open beside the editor.
SeaTable13

Update a Row

Action

In MakeUpdates a row.

Update a Row changes the values of an existing row: a new status, a corrected phone number, an amount recalculated in another app. Only the row you target changes.

When to use it
after Watch Updated Rows or Search Rows has pointed to the row that needs new values.
Watch out
the module list shows Update a Row twice, with one description and no stated difference. Pick one, test it with Run once, then reuse it everywhere.
SeaTable14

Update a Row

Action

In MakeUpdates a row.

This second Update a Row module also rewrites the values of an existing row. Make shows it next to the first one, and the directory gives both an identical description.

When to use it
a scenario you open already contains this version, and nothing in the documentation calls for swapping it for the other one.
Watch out
the documentation does not explain the difference, so avoid mixing both versions in one scenario without a reason.
SeaTable15

Upload a File/Image

Action

In MakeSaves a file or image to a specific row.

Upload a File/Image stores a file or an image in a specific row, straight from another app: an invoice from your inbox, a photo from a form, a PDF generated earlier in the scenario.

When to use it
the row is your record of reference and the document belongs next to it.
Watch out
on the Free plan Make handles files up to 5 MB, so large scans may call for a paid plan.
SeaTable16

Get Account

Search

In MakeGet account details from email, name or username.

Get Account looks up a SeaTable account from an email, a name or a username and returns its details. It turns an address typed into a form into an actual member of your workspace.

When to use it
before assigning a row to someone when all you have is their email.
Watch out
Get Collaborator has the exact same official description; run both on a known email and keep the one whose output suits your mapping.
SeaTable17

Get Collaborator

Search

In MakeGet account details from email, name or username.

Get Collaborator finds a person from an email, a name or a username and hands their account details to the next module. Get Account has the same description, so treat them as twins and keep the one you tested.

When to use it
a request arriving from a chat tool names a colleague, and SeaTable needs that colleague's account.
Watch out
a misspelled name returns no bundle and the modules after it get nothing to work with, so test with Run once on a real name.
SeaTable18

List Rows

Search

In MakeRetrieves a list of all rows in a specified table.

List Rows returns every row of a table, each one as its own bundle. Use it when you want the whole table, not a filtered slice.

When to use it
sending a complete table to a spreadsheet or a reporting tool, or reviewing all rows in one run.
Watch out
each bundle costs one operation in every module after it (an operation is one module run on one bundle, the unit Make counts on your plan). On a big table, a search keeps that count down.
SeaTable19

Search Rows

Search

In MakeSearch one or multiple rows by keyword.

Search Rows finds the rows that contain a keyword and passes each match along. Zero, one or several rows can come back, which makes it the natural step before an update, a link or a deletion.

When to use it
checking whether a customer, an email or an order number already exists in the table.
Watch out
several matches mean the next modules run several times. If you expect exactly one row, confirm it with Run once.
SeaTable20

Search with SQL-Query

Search

In MakeSearch for rows with an SQL-like syntax.

Search with SQL-Query retrieves rows with a query written in a syntax close to SQL, the language databases use. It handles combined conditions that a single keyword cannot express.

When to use it
you need rows that meet several criteria at once, such as one status and one owner together.
Watch out
the syntax is SQL-like, not full SQL. If queries are new to you, start with Search Rows and switch once it no longer covers your filter.
Need help

Need help automating SeaTable with Make?

A person reads every message.

FAQ

SeaTable and Make: common questions

01Is the SeaTable Make integration free?
Yes, on the Make side. SeaTable is a standard app, available from the Free plan. That plan gives you 2 active scenarios, at least 15 minutes between scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams, Enterprise) bring the interval down to 1 minute, lift the cap on active scenarios and allow 40 minutes of execution. Usage is counted in operations, one per module run on one bundle. Your SeaTable subscription is a separate matter, covered on SeaTable's own pricing page.
02What does it take to connect SeaTable to Make?
An active SeaTable account and a valid token. The documentation accepts an AccountToken, an APIToken or a BaseToken. The simplest route is an API token for one base: hover over the base on the SeaTable home page, open its options menu, expand Advanced, select API Tokens, enter a name, pick a permission, generate and copy. Then click Create a connection on any SeaTable module in Make, name it if you like, and paste the token. That one connection serves every SeaTable module afterwards.
03Do SeaTable triggers in Make react in real time?
No. Both SeaTable triggers, Watch New Rows and Watch Updated Rows, are scheduled: Make checks your base on the scenario's schedule instead of being notified the moment a row changes. A new scenario runs every 15 minutes by default, and that is also the shortest interval on the Free plan. Paid plans can go down to 1 minute. Plan your process around that gap: a row added just after a check waits for the next one before anything happens.
04What if a SeaTable module is missing in Make?
Use Make an API Call. It reaches any endpoint of the SeaTable API with the connection you already have, so you are not limited to the 22 listed modules. You write the request yourself, which means a look at SeaTable's API documentation. Before going that far, check the searches: Search with SQL-Query handles combined filters that Search Rows cannot. Keep in mind that Make's SeaTable documentation states it is AI-generated and may contain mistakes, so confirm critical details with SeaTable.
05Make or n8n: which one fits SeaTable better?
It depends on your setup rather than on a winner. On Make, SeaTable comes with 22 modules: 2 scheduled triggers, 15 actions and 5 searches, plus Make an API Call for anything else. SeaTable also exists as a node in n8n, with its own page on this site. List the modules your process needs, compare what each tool offers for them, and check which one already connects the other apps in that process. Then build your first scenario there.