Resources · Make integration

Stackby Make integrationAutomate Stackby with Make.

Can Make fill and update your Stackby tables while you do something else? Yes. The Stackby Make integration gives you 5 modules: 2 triggers, 2 actions and 1 search. This page explains each one, then walks you through your first scenario.

Try the Stackby integration on MakeSee the 5 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Stackby Make integration do for you?

The Stackby Make integration links your Stackby account to Make so rows move without copy and paste. You build a scenario (the automation itself, a chain of bricks called modules) that notices new or changed rows, creates rows, edits them by ID or looks them up, and runs without you.

Route new requests to the right team. An agency collects client briefs in one Stackby table. Watch Records picks up each new row in a chosen view, and Create a row writes a copy into the production team's table, so nobody retypes the brief.

Keep two tables in step. When someone edits a record, Watch Updated Records hands it to the scenario, Search rows finds the matching row elsewhere, and Update a row writes the new values into it by its ID.

Collect data from other apps. Start the scenario with a module from another app, such as a form tool, then let Create a row turn every entry into a clean Stackby row.

Know the limits before you start. Both triggers are scheduled, so Make checks Stackby on a timer instead of hearing from it the moment a row changes. The list has no module to delete a row and no universal API call module. If you also work with n8n, read the Stackby n8n integration page or the n8n vs Make comparison. New to the editor? The Make training covers the basics.

Connect

How do you connect Stackby to Make?

  1. 01

    Create an API key in Stackby

    In Stackby, click your profile icon at the top right, open Account, and scroll to the API key section. Click Create API key and copy the key shown on screen. Make needs it to act on your behalf.

  2. 02

    Add a Stackby module in Make

    Open your scenario, add any Stackby module and click Create a connection. A connection is your Stackby account linked to Make once; every Stackby module in your scenarios reuses it afterwards.

  3. 03

    Paste the key and save

    Give the connection a name in Connection name if you like (handy with several accounts), paste the API key and confirm. Make can now list the tables and views your account can reach.

First scenario

Build your first scenario with Stackby

GoalWhen a new row appears in a Stackby view, Make copies it into another Stackby table.

  1. 01

    Start a new scenario

    Go to the Scenarios page, create a new scenario and click the big + to place the first module.

  2. 02

    Add Watch Records

    Search for Stackby, pick Watch Records and click Create a connection if you have not linked your account yet. Then choose the table and the view to watch.

  3. 03

    Add Create a row

    Click the + on the right of the trigger, pick Create a row and select the destination table. Map each column to a value from the row the trigger found.

  4. 04

    Test with Run once

    Add a test row to the watched view, then click Run once. Open the bubble above each module to read the bundles it received, one bundle per row.

  5. 05

    Schedule it and switch it on

    Open the clock on the first module to set the schedule (every 15 minutes by default) and turn the scenario on. From then on, Make checks the view at each run.

Triggers

What starts a Stackby scenario

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

Stackby1Watch Records

Watch Records

Scheduled trigger

In Make“Returns all newly created rows in a view.”

Watch Records gives your scenario every row newly added to a Stackby view, so each fresh entry can travel on to another table or app. Each row arrives as its own bundle, the item passed from one module to the next.

How it fires
scheduled. Make checks Stackby on the scenario's schedule, every 15 minutes by default, and collects the rows added since the last check.
When to use it
an intake table where new leads, briefs or requests land and need to reach someone else.
Watch out
it reads a view, so a filter on that view decides which rows the scenario ever sees.
Stackby2Watch Updated Records

Watch Updated Records

Scheduled trigger

In Make“Returns updated records”

This trigger reacts to edits rather than additions: it returns the records someone changed, so a new status or a corrected value can flow into the rest of your setup.

How it fires
scheduled. On every scenario run, Make asks Stackby which records were updated since the previous check.
When to use it
a project tracker where a changed status should update a copy of the row in a client-facing table.
Watch out
if the same scenario writes back into the watched table, those edits count as updates too, and the scenario can keep picking up its own changes.
Modules

What Make can do in Stackby

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

Stackby1

Create a row

Action

In Make“Creates a new row in any table in Stackby.”

Adds a fresh row to the Stackby table of your choice, filled with data from earlier modules, so no one has to type it by hand.

When to use it
a form reply, a new order or a row from another table must become a new line in Stackby.
Watch out
each run creates a new row, so a test repeated with Run once leaves duplicates to clean up.
Stackby2

Update a row

Action

In Make“Updates a row by its ID.”

Changes the values of one existing row, which Make locates by its ID. Pick it over Create a row whenever the record already exists and only a few columns need new content.

When to use it
marking a request as handled once a later step in the scenario succeeds.
Watch out
without the row ID you have nothing to point at, so place Search rows or a trigger before it.
Stackby3

Search rows

Search

In Make“Searches for any specific row or returns all rows.”

Looks up the rows that match what you are after, or returns every row of the table, and hands them to the next module one by one.

When to use it
checking whether a contact already has a row before you decide between creating and updating it.
Watch out
the result can be zero, one or many bundles, and each bundle runs the modules after it, which adds operations (Make's unit of usage on your plan).
Need help

Need help automating Stackby with Make?

A person reads every message.

FAQ

Stackby and Make: common questions

01Is the Stackby Make integration free?
Yes, on the Make side. Stackby is a standard app, so it works on the Free plan. That plan allows 2 active scenarios, a minimum of 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 and Enterprise) lower the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes of execution. You still need an active Stackby account, whose pricing Stackby sets.
02What do you need to connect Stackby to Make?
An active Stackby account and an API key. In Stackby, click your profile icon, open Account, scroll to the API key section, click Create API key and copy the key. In Make, add a Stackby module, click Create a connection, optionally name it, then paste the key. The connection is saved once and every Stackby module you add later can reuse it, in this scenario or any other. Without an active Stackby account, you cannot create the key at all.
03Do the Stackby triggers in Make fire instantly?
No. Both Watch Records and Watch Updated Records are scheduled triggers: Make checks Stackby at each run of the scenario instead of receiving a signal from Stackby. A new scenario runs every 15 minutes by default. On the Free plan, 15 minutes is also the shortest interval; paid plans go down to 1 minute. If you need a faster reaction, shortening the schedule on a paid plan is the lever that Make offers here.
04What if a Stackby module is missing in Make?
It depends on what is missing. The Stackby app in Make has 5 modules and no Make an API Call module, so you cannot fall back on a raw request inside the app. Deleting a row, for instance, is not in the list. Search rows can return all rows when you need to review a whole table. For anything beyond that, the way forward is another app that covers the need, or help from the team at Hack'celeration to design the workaround.
05Should you use Make or n8n for Stackby?
It depends on your setup rather than on Stackby. Make offers the 5 modules described here, with two scheduled triggers, and a Free plan to start. Stackby also appears among n8n integrations, with its own page on this site. A practical criterion: build in the tool where your other automations already live, so connections, runs and errors sit in one place. Compare each option against the exact modules your scenario needs.
Same platform

Other docs you might need on this stack.

Browse all integrations