Resources · Make integration

AppSheet Make integrationAutomate AppSheet with Make.

Your AppSheet tables can be filled, updated and cleaned by other tools, with no one retyping a row. The AppSheet Make integration offers 7 modules: 6 actions and 1 search. This page shows how to link your app, then walks you through a first working scenario.

Try the AppSheet integration on MakeSee the 7 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the AppSheet Make integration do for you?

The AppSheet Make integration lets a Make scenario (the automation you build in Make, a chain of modules) read and write the tables behind your AppSheet app. Each module is one brick of that chain: here, adding a row, changing it, finding it, deleting it or running one of your app actions.

Keep the table fed from elsewhere. A lead comes in through another tool, and Create a Record adds it as a new row, so your field team sees it in the app. Every row that passes between modules is a bundle, one item at a time.

Keep status in sync. When a job is closed in another system, Edit a Record updates the matching row by its key fields, and Delete a Record removes rows that should no longer exist.

Reuse the logic you already built. Search Records pulls the rows that match, and Invoke an Action runs a custom action of your table on them, so the rules stay inside AppSheet.

There is no trigger in this app: nothing in AppSheet starts a scenario by itself. You start it with a schedule or with another app. Anything the modules do not cover goes through Make an API Call. If you are weighing tools, read n8n vs Make, and check Make pricing before you plan several scenarios. Stuck on a run? Make troubleshooting covers the usual errors.

Connect

How do you connect AppSheet to Make?

  1. 01

    Copy your key and App ID

    In AppSheet, open the app editor dashboard, go to the Manage tab, then Integrations. Copy the key shown under Application Access Keys, and the App ID shown on the same page.

  2. 02

    Add a module and create the connection

    In your Make scenario, add any AppSheet module and click Create a connection. A connection is your AppSheet account linked to Make once; every AppSheet module reuses it. The Connection name field is optional.

  3. 03

    Paste the credentials

    Paste the access key and the App ID you copied, then save. Make now knows which app to talk to, and the module can list what it reads from your tables.

First scenario

Build your first AppSheet scenario

GoalWhen a row in your AppSheet table matches a search, Make runs one of your table actions on it.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the + to add the first module. Type AppSheet in the search box.

  2. 02

    Start with Search Records

    Pick Search Records, then Create a connection with your key and App ID. Choose the table and the rows you want, or let it list them all.

  3. 03

    Add Invoke an Action

    Click the + on the right of the search, add Invoke an Action and pick the custom action. Map each found row from the search. Tip: search for rows the action changes, so they stop matching next run.

  4. 04

    Test with Run once

    Click Run once. Open the bubbles above each module to read the bundles it received: one bundle per row the search returned.

  5. 05

    Schedule and switch it on

    Set the clock on the first module (every 15 minutes by default) and switch the scenario on. On the Free plan, 15 minutes is also the shortest interval.

Modules

Every AppSheet module, and when to pick it

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

AppSheet1

Create a Record

Action

In Make“Adds a new record.”

Adds a fresh row to the AppSheet table you pick, filled with data coming from earlier modules, so new entries show up in the app without anyone typing them.

When to use it
a request arrives in another tool and should land in the list your team works from.
Watch out
it always adds, never updates; if the row may already exist, search first and use Edit a Record instead.
AppSheet2

Delete a Record

Action

In Make“Deletes a record specified by key fields.”

Removes one row from your table, found through its key fields, which keeps the app free of entries that no longer matter to anyone.

When to use it
a record got cancelled in the system that owns it.
Watch out
a deleted row does not come back from Make, so point your first Run once at a copy of the table before touching the real one.
AppSheet3

Edit a Record

Action

In Make“Updates a record specified by key fields.”

Updates a row that already exists. Make finds it through its key fields, and the app then shows the latest status set in another tool.

When to use it
an order ships, a job closes or a contact changes phone number elsewhere, and the matching row must follow.
Watch out
without the right key the module has nothing to update; map the key from a search or from the source data.
AppSheet4

Get a Record

Action

In Make“Retrieves a single record specified by the number of the row.”

Brings back exactly one row, picked by its row number, so later modules can reuse its values in an email, a document or another app.

When to use it
you already know which row you need and want its full content, not a list.
Watch out
it reads by row number, not by a value; to find rows by content, Search Records is the better fit.
AppSheet5

Invoke an Action

Action

In Make“Invokes a custom action available for your table.”

Runs one of the custom actions defined on your table, so the business logic you already set up in AppSheet does the work instead of Make rebuilding it.

When to use it
your app already has an action such as marking an item approved, and you want another tool to fire it.
Watch out
the action must exist on that table first; Make only calls what AppSheet exposes.
AppSheet6

Make an API Call

Action

In Make“Performs an arbitary authorized API call.”

Sends a request of your choice to the AppSheet API, reusing the same connection, for the cases the six other modules leave out.

When to use it
you need an endpoint that no listed module covers and you are comfortable reading the AppSheet API docs.
Watch out
you write the request yourself, so a wrong path or body simply returns an error; test it with Run once.
AppSheet7

Search Records

Search

In Make“Searches for records at the table or lists them all.”

Looks through a table and hands back the rows that match, or lists every row when you set no search, one bundle per row.

When to use it
you need to find which rows to update, delete or pass to an action before doing anything else.
Watch out
it can return zero, one or many rows, and each following module runs once per row, which counts as operations on your plan.
Need help

Need help automating AppSheet with Make?

A person reads every message.

FAQ

Questions people ask next

01Is the AppSheet Make integration free?
Yes, on the Make side. AppSheet is a standard app, available from the Free plan, which gives you 2 active scenarios, a minimum of 15 minutes between scheduled runs, 5 minutes per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams, Enterprise) drop the interval to 1 minute and count usage in credits. The catch sits on the AppSheet side: the Make doc says your AppSheet account needs an Enterprise plan and a valid access key. Check the AppSheet pricing page for that part.
02What do you need to connect AppSheet to Make?
Three things: an AppSheet account on an Enterprise plan, an Application Access Key that has not expired, and the App ID of the app you want to automate. You find both values in the app editor, under the Manage tab, then Integrations. In Make, add an AppSheet module, click Create a connection, give it a name if you like, and paste the key and the App ID. That connection is then shared by every AppSheet module in your scenarios, so you only set it up once.
03Can AppSheet start a Make scenario in real time?
No, not through this app. The AppSheet app in Make has no trigger module, scheduled or instant, so nothing in AppSheet starts a scenario on its own. You have two ways to begin anyway. Put a schedule on the first module, for example Search Records, and Make runs the scenario every 15 minutes by default, or every minute at best on a paid plan. Or start the scenario with a trigger from another app, then write to AppSheet with Create a Record or Edit a Record.
04What if the AppSheet module you need is missing in Make?
Use Make an API Call. It sends any request to the AppSheet API with the same connection you already created, so you can reach what the six other modules do not cover. You write the request yourself from the AppSheet API documentation, then test it with Run once and read the returned bundle. Keep in mind that the Make doc for this app is flagged as AI-generated and may contain mistakes, so verify key details, such as plan requirements, directly with AppSheet.
05Should you use Make or n8n for AppSheet?
It depends on what you need from the tool. In Make, AppSheet comes with 7 ready modules covering rows and custom actions, plus Make an API Call for the rest, and every step is visible in the editor. The same app often has an n8n node too, so check what that node offers before choosing. Compare the modules each side gives you for your case, the way you prefer to build, and your plan limits, rather than looking for a winner.
Same platform

Other docs you might need on this stack.

Browse all integrations