Stackby n8n integrationAutomate Stackby with n8n.
Your Stackby tables should not be the place where automation stops. The Stackby n8n integration gives you one node, 4 operations and a single API key: append rows, read a record, list a table, delete a record. There is no Stackby trigger, so a schedule or a webhook starts the run.
Verified Trustpilot reviews · AI, automation & growth agency
What does the Stackby n8n integration actually do?
The Stackby node plugs an n8n workflow into a Stackby stack, the spreadsheet database where your tables live. It carries 4 operations on a single resource: default.append writes new rows, default.read pulls one record by its ID, default.list returns the records of a table, and default.delete removes one record. Authentication rests on a Stackby API key you store once in n8n and reuse everywhere.
Start with the intake path, the shortest one. A webhook, meaning a URL n8n exposes so an outside service can push data into the workflow, lands on the node with Append selected. You name the stack, the table, and the columns that will receive the values. The official template 934, "Insert and retrieve data from a table in Stackby", walks through that same pair of steps.
Second scenario, the morning export. A Schedule Trigger runs at a fixed time, List returns the records of the table, and the rows go where people already work: a Google Sheets tab for the sales team, a Postgres table for whoever builds the reports. Keep Return All on when the export has to be complete.
Third, the review loop. Read fetches one record from its ID, a condition checks what came back, and Delete takes the row out when it no longer belongs in the table. Post a line to Slack just before the deletion and the team keeps a written trace of what left the stack.
Anything you need from the Stackby API that sits outside this node's catalogue has a clean answer: the HTTP Request node calls any endpoint of the API and reuses the same credential through its predefined authentication. Nothing to install, nothing to code around.
Two habits keep these workflows honest. Table names are typed by hand, so renaming a table in Stackby breaks the node until you update the field. And Read and Delete both expect the record ID, not the visible content of the row. If the n8n side is what feels unfamiliar, the n8n training covers expressions and error handling, and teams coming from Airtable will recognize most of the shape already.
How do you connect Stackby to n8n?
- 01
Create the API key in Stackby
You need a Stackby account first. Once you have one, open Account Settings and go to the API section, where you create an API Key. That key is the only thing n8n asks for on this node. Stackby documents the same path in its own help article on getting an API key, so copy the value straight from that screen instead of retyping it.
- 02
Store the credential once in n8n
In n8n, open the Credentials menu and create a Stackby credential, which is the saved login n8n reuses on your behalf. Paste the API Key, give the credential a name that says which Stackby account it belongs to, and save. Every workflow you build later picks it from a dropdown, so the key never gets copied into a node by hand.
- 03
Point the node at a stack and a table
Add the Stackby node to a canvas, select the credential, then pick one of the 4 operations. Two fields follow you across all of them: Stack ID, the ID of the stack to access, and Table, where you enter the table name in full, like
Stories. Run the node once on real data before you wire anything downstream.
What can the Stackby node do?
The Stackby node exposes 4 operations. For each one: the node as you configure it in n8n, the required fields, and our field notes.
Append
appendWhat you see in n8n
Notes & use cases
Append writes new rows into a Stackby table from the items running through the workflow.
Key parameters
- Stack ID: the ID of the stack to access, so the node knows which Stackby stack receives the write.
- Table: the table name, entered in full, such as
Stories. - Columns: a comma-separated list of the properties which should be used as columns for the new rows, for example
id,name,description.
Delete
deleteWhat you see in n8n
Notes & use cases
Delete takes one record out of a Stackby table. The row is picked by its ID, not by anything you can read in it.
Key parameters
- Stack ID: identifies the stack the node opens.
- Table: the table holding the record, typed as its name.
- ID: the ID of the record, usually carried over from an earlier node with an expression such as
{{ $json.field }}.
List
listWhat you see in n8n
Notes & use cases
List returns the records of a table and hands them to the rest of the workflow, one item per row.
Key parameters
- Stack ID and Table: which stack to open, and the name of the table to read.
- Return All: on, n8n walks the API pages and brings back every record; off, Limit sets the maximum number of results returned.
- View, under Additional Fields: the name or ID of a view in the table. Set it and only that view's records come back, sorted in the view's order.
Read
readWhat you see in n8n
Notes & use cases
Read fetches a single record and puts its content into the run, which is what you want before deciding anything.
Key parameters
- Stack ID: the ID of the stack to access.
- Table: the name of the table the record sits in.
- ID: the ID of the record to return, typically
{{ $json.field }}coming from the node just before.
Need help automating Stackby with n8n?
A person reads every message.
