Resources · Make integration

Botsheets Make integrationAutomate Botsheets with Make.

Can Make read and update your Botsheets data without code? Yes: the Botsheets Make integration gives you 4 modules, 2 searches and 2 actions, and no trigger. This guide is for people who know Botsheets but are new to Make, and it walks you from connection to a first working scenario.

Try the Botsheets integration on MakeSee the 4 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Botsheets Make integration do for you?

The Botsheets Make integration lets a Make scenario (the automation you build, a chain of steps) look up rows and gallery items in Botsheets and change a cell, with no code. Each step is a module, one brick of the scenario. Botsheets has no trigger in Make, so something else starts the run: another app or a schedule.

Keep a status column up to date. When a deal closes in your CRM, a scenario runs Search Rows to find the matching row in Botsheets, then Edit a Cell writes the new status. Nobody has to open the sheet to change it by hand.

Feed another tool with your gallery. List Gallery Items pulls the items of a gallery so the next module, from any app, can post them, file them or send them in a message. Each item travels as one bundle, meaning one item passed from a module to the next.

Reach what the menu does not show. Make an API Call uses the same connection to call any endpoint of the Botsheets API, which is handy since the list of modules is short.

Know the limits before you build: Make itself says its Botsheets documentation is incomplete, because little public information exists about the app. Test every module with real data before relying on it, and keep the Make troubleshooting guide close. If you are still weighing tools, the n8n vs Make comparison helps, and the Make training covers scenario basics step by step.

Connect

How do you connect Botsheets to Make?

  1. 01

    Add a Botsheets module

    Open any Botsheets module in your scenario and click Create a connection. A connection is your Botsheets account linked to Make once, then reused by every Botsheets module you add later.

  2. 02

    Name the connection

    Give the connection a name if you like, for example the workspace or client it belongs to. It is optional, but a clear name saves you from guessing when several accounts sit side by side in Make.

  3. 03

    Authorize and save

    Either approve Make on the Botsheets page that opens, or paste the key Botsheets gives you, depending on what the window asks for. Then click Save and the module is ready to fill in.

First scenario

Your first scenario with Botsheets and Make

GoalWhen another app sends a new piece of data, Make finds the matching row in Botsheets and updates one of its cells.

  1. 01

    Create the scenario

    Go to the Scenarios page, create a new scenario and click the +. Since Botsheets has no trigger, pick the module of the app that should start the run, like a form or a CRM.

  2. 02

    Add Search Rows

    Click the + on the right of that first module, search for Botsheets and pick Search Rows. Click Create a connection if this is your first Botsheets module, then fill in its fields.

  3. 03

    Add Edit a Cell

    Add Edit a Cell after the search. Map the row found by Search Rows into it, then map the value that came from the first app. Make shows the data from earlier modules as you click each field.

  4. 04

    Test with Run once

    Click Run once and trigger the first app with a test record. Open each module to read the bundles it received, and check the cell in Botsheets. A search that finds nothing sends nothing downstream.

  5. 05

    Schedule and switch on

    Set the schedule on the first module, which is every 15 minutes by default, and switch the scenario on. On the Free plan, 15 minutes is also the shortest interval between two scheduled runs.

Modules

The 4 Botsheets modules in Make

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

Botsheets1

Edit a Cell

ActionIn the docs only

Writes a new value into one cell, so your Botsheets data reflects what just happened in another tool without anyone typing it in.

When to use it
after a search has pointed to the right row, to update a single status, owner or score rather than rewriting the whole record.
Watch out
it overwrites what was there, so run it once on a test row and check the result before you switch the scenario on.
Botsheets3

Make an API Call

ActionIn the docs only

Opens the whole Botsheets API to your scenario, using the connection you already created, so a missing module no longer blocks you.

When to use it
the three other modules do not cover your case and you know which Botsheets endpoint does the job.
Watch out
you write the request yourself and Make's Botsheets documentation is incomplete, so test each request with Run once before you rely on it.
Botsheets4

Search Rows

SearchIn the docs only

Finds the rows that match what you are looking for and hands each one on as its own bundle, ready for the next module to read or change.

When to use it
just before Edit a Cell, to locate the row tied to a customer, an order or a ticket coming from another app.
Watch out
a search can return zero, one or several rows; with several, the next module runs once per row, and with zero, nothing after it runs at all.
Need help

Need help automating Botsheets with Make?

A person reads every message.

FAQ

Botsheets and Make: common questions

01Is the Botsheets Make integration free?
Yes. Botsheets is a standard app in Make, so you can use it from the Free plan. That plan gives you 2 active scenarios, a minimum of 15 minutes between two scheduled runs, 5 minutes of run time per execution and files up to 5 MB. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute, remove the cap on active scenarios and count usage in credits each month. Your Botsheets subscription is a separate matter that this page does not cover.
02What do you need to connect Botsheets to Make?
A Botsheets account and a Make account. Make's documentation for Botsheets lists no specific prerequisite and no official connection steps, so you follow the standard flow: add a Botsheets module, click Create a connection, optionally name it, then either authorize Make on the Botsheets page or paste the key Botsheets provides, and click Save. After that, every Botsheets module in your scenarios reuses the same connection, so you only do this once per account.
03Can Botsheets trigger a Make scenario in real time?
No. Botsheets has no trigger module in Make, neither scheduled nor instant, so it cannot start a scenario on its own. You start the run another way: with a trigger from another app, such as a form or a CRM, or with a schedule on the first module, which is every 15 minutes by default. Make also offers a webhook as a starting point, which another tool can call when something happens. Botsheets modules then come in as the second or third step.
04What if a Botsheets module you need is missing in Make?
Use Make an API Call. It reuses your Botsheets connection and lets the scenario call any endpoint of the Botsheets API, which covers what Edit a Cell, Search Rows and List Gallery Items do not. Keep in mind that Make states its Botsheets documentation is incomplete because little public information exists about the app, so check the request against what Botsheets tells you about its API and test it with Run once before switching the scenario on.
05Should you use Make or n8n for Botsheets?
It depends on the tool your team already knows. On Make, Botsheets comes with 4 modules: two searches, one cell edit and a generic API call, plus a visual editor where each step is a module you drag in. The same app often has an n8n node as well, so check both catalogs for the actions you need before choosing. Pick the platform where the rest of your automations already live, since keeping them in one place makes them easier to maintain.
Same platform

Other docs you might need on this stack.

Browse all integrations