Resources · Make integration

Glide Make integrationAutomate Glide with Make.

What if your Glide app filled its own tables while you worked elsewhere? The Glide Make integration gives you 5 modules: 3 actions and 2 searches that work on table rows. This page shows what they do, how to link your account and how to build a first scenario step by step.

Try the Glide integration on MakeSee the 5 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Glide Make integration do for you?

The Glide Make integration lets Make read and change the rows of your Glide tables without code. You build a scenario, which is the automation Make runs, out of modules, each one a single brick such as an action or a search. Glide brings five of them, all about rows.

Feed an app from outside. A form, a CRM or a spreadsheet produces a new record, and Add Row writes it into the Glide table behind your app. Field staff see it on their phones without anyone retyping it.

Keep records current. When a status changes in another tool, Get Row or Get Rows finds the matching entry and Edit Row updates it. The same pair helps you tidy old data: search first, then Delete Row on what you no longer need.

Send Glide data somewhere else. Get Rows returns rows as bundles, one item per row, that the next module can pass to a sheet, an email or a CRM such as the one in our Airtable Make integration guide.

What Make does not offer here: Glide has no trigger module, so nothing starts on its own when a row changes in Glide. The scenario starts on a schedule or on an event in another app. There is no Make an API Call module either.

Glide may also have a node in n8n. Both tools are compared in n8n vs Make, and the Make training covers the editor from scratch.

Connect

How do you connect your Glide account to Make?

  1. 01

    Create an API key in Glide

    In your Glide account, open the Config menu, then API Keys, and create a key. Copy the key shown on screen. You need an active Glide account for this, and Make will use the key to act on your behalf.

  2. 02

    Add a Glide module in Make

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

  3. 03

    Name it and paste the key

    The Connection name field is optional, but a clear name helps when you run several workspaces. Paste the API key you copied, or follow the instructions Make shows on screen, and save the connection.

First scenario

Build your first scenario with Glide

GoalWhen a new record appears in another app, Make adds it as a row in your Glide table.

  1. 01

    Start a blank scenario

    Open the Scenarios page, create a new scenario and click the + in the middle of the canvas. Since Glide has no trigger, the first module comes from the app where your records start.

  2. 02

    Pick the source module

    Search the source app by name, choose the module that watches for new records and create its connection. Fill its fields so Make knows where to look.

  3. 03

    Add the Glide action

    Click the + on the right of the first module, search Glide and pick Add Row. Select your Glide connection, or create it as shown above, then fill the module fields.

  4. 04

    Map the incoming data

    For each field of the row, click and pick the matching value from the first module. Make offers the data it received, so a name goes to the name column, an email to the email column.

  5. 05

    Test with Run once

    Click Run once. Make runs the scenario a single time and shows the bundles each module received. Open your Glide app and check that the new row is there.

  6. 06

    Schedule and switch on

    On the first module, open Scheduling: a new scenario checks every 15 minutes by default. Adjust it if your plan allows, then switch the scenario on.

Modules

What each Glide module does

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

Glide1

Add Row

Action

In Make“Add a row to a table”

Add Row writes a brand new row into a Glide table, so the record shows up in your app for everyone who uses it.

When to use it
a sign-up, an order or a support request lands in another tool and should appear in the app your team opens on the go.
Watch out
it always creates a new row; if the record may already exist, search with Get Rows first and route matches to Edit Row.
Glide2

Delete Row

Action

In Make“Delete rows from a table”

Delete Row removes rows from a Glide table and keeps your app free of entries that no longer matter to anyone.

When to use it
a customer cancels, a task is closed elsewhere, or a record was flagged as a duplicate by an earlier search.
Watch out
a deletion cannot be undone from Make, so run the scenario with Run once on a test table before pointing it at live data.
Glide3

Edit Row

Action

In Make“Edit an existing row”

Edit Row changes the values of a row that already exists, so the app reflects the latest state without creating a copy.

When to use it
a payment clears, a delivery ships or a deal moves stage in another app, and the matching Glide entry must follow.
Watch out
it needs to know which row to change; place Get Row or Get Rows before it and map the row from that search.
Glide4

Get Row

Search

In Make“Get row from a table”

Get Row fetches one row from a Glide table and hands its values to the modules that follow in the scenario.

When to use it
you already know which entry you want and need its details to write an email, fill a document or check a status.
Watch out
a search can come back empty, so decide what the rest of the scenario should do when nothing is found.
Glide5

Get Rows

Search

In Make“Get rows from a table”

Get Rows reads several rows from a table and returns each one as a separate bundle, ready to be copied, checked or cleaned up.

When to use it
exporting a table to a sheet, building a report from app data, or listing entries before editing or deleting them.
Watch out
every returned row runs through the next modules, and each run of a module counts as an operation on your Make plan.
Need help

Need help automating Glide with Make?

A person reads every message.

FAQ

Glide and Make: frequent questions

01Is the Glide Make integration free?
Yes, on the Make side. Glide is a standard app, so its modules are available from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, 5 minutes per run and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute and remove the cap on active scenarios. Usage is counted in operations, one per module run on one bundle. You still need an active Glide account, whose own pricing is set by Glide.
02What do you need to connect Glide to Make?
An active Glide account and an API key. In Glide, open the Config menu, go to API Keys, create a key and copy it. In Make, add a Glide module, click Create a connection, optionally name it, and paste the key. The connection is then shared by every Glide module in your scenarios, so this setup happens once. If Make refuses the key, create a new one and paste it again, making sure it comes from the right Glide account.
03Can a Glide scenario react in real time?
Not from Glide itself. The app has no trigger module in Make, so no change in a Glide table can start a scenario on its own. There are two ways around it. Start the scenario with a trigger from another app, such as a form or a CRM, and let Glide modules run after it. Or start it on a schedule: a new scenario runs every 15 minutes by default, and Get Rows can then read the table on each run. On the Free plan, 15 minutes is also the shortest interval.
04What if a Glide module you need is missing in Make?
It depends on what you need. Make offers five Glide modules: Add Row, Edit Row, Delete Row, Get Row and Get Rows, all about table rows. Glide has no Make an API Call module, so you cannot reach other parts of Glide from this app. When a gap blocks you, check whether the data can come from another app already connected to Make, or ask a Make agency for help designing a workaround. The documentation lists no numeric limit for these modules.
05Should you use Make or n8n for Glide?
It depends on the tool your team already uses. Make gives Glide five ready modules for rows, a visual editor and a Free plan to test with. Glide may also have a node in n8n, so the useful comparison is practical: which editor your team knows, which other apps the scenario touches and where your existing automations run. Neither choice changes what Glide exposes. The n8n vs Make comparison on this site covers the two tools side by side, without ranking them for this app.
Same platform

Other docs you might need on this stack.

Browse all integrations