Resources · Make integration

Retable Make integrationAutomate Retable with Make.

Need your Retable tables filled, updated or built without copy and paste? The Retable Make integration gives you 16 modules: 13 actions and 3 searches. This guide shows how to connect your account, build a first scenario and pick the right module.

Try the Retable integration on MakeSee the 16 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can you automate with the Retable Make integration?

The Retable Make integration links your Retable account to Make, so a scenario (the automation you build in Make, a chain of bricks called modules) can create, read, update and delete your Workspaces, Projects, tables and rows. It has no trigger: a scenario starts on its schedule or on another app, then Retable does the work.

Collect leads in one table. A form or a CRM feeds the scenario, and Insert New Row to Retable writes each contact as a line. Sales sees every new lead in the same place instead of hunting through inboxes.

Keep statuses in sync. When an order ships or a ticket closes in another tool, Update Row Data changes the matching line, and Delete Row from Retable clears the ones that no longer matter.

Set up a client space from scratch. Create a Project, Create a Retable and Create Column build the same structure for each new account, so onboarding starts from a ready table.

Retable has no trigger in Make, so nothing starts when a row changes inside Retable itself. For anything the 16 modules miss, Make an API Call reaches the Retable API with the same connection. Many apps also have an n8n node; the n8n vs Make comparison helps you choose, and the Make pricing page walks through the plans.

Connect

How do you connect Retable to Make?

  1. 01

    Copy your API key

    In Retable, click your user name at the top right, open the API tab, enable the key if it is switched off, then copy the API key shown on screen. You need an active Retable account for this.

  2. 02

    Add a Retable module

    In your Make scenario, add any Retable module and click Create a connection. The Connection name field is optional, but a clear name helps you find the right account again later.

  3. 03

    Paste the key and save

    Paste the API key you copied, or follow the instructions on screen, and confirm. The connection (your Retable account linked to Make once) is then reused by every Retable module of your scenarios.

First scenario

Build your first Retable scenario

GoalWhen a new lead arrives in another app, Make adds it as a row in your Retable.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the +. The first module is the app your leads come from, such as your form tool or CRM, since Retable has no trigger of its own.

  2. 02

    Add Insert New Row to Retable

    Click the + on the right of that first module, search for Retable and pick Insert New Row to Retable. Click Create a connection and paste your API key.

  3. 03

    Map the lead to your columns

    Choose the Retable to fill; Make lists what it can read once the connection exists. Map each column to data from the first module, such as the name or email it received.

  4. 04

    Test with Run once

    Click Run once and send a test lead. Open each module to read the bundle it received (one bundle here is one lead), then check the new line in Retable.

  5. 05

    Schedule and switch it on

    Set the schedule on the first module; a new scenario runs every 15 minutes by default. Switch the scenario on. Each module run on one bundle counts as one operation on your Make plan.

Modules

What each Retable module does

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

Retable1

Add a new row V2

Action

In Make“Add a new row v2”

Adds one fresh row to a Retable, so each bundle coming from earlier in the scenario, one form answer or one order, ends up as a line your team can sort and filter.

When to use it
a signup arrives in another tool and you want it logged in Retable without anyone copying it by hand.
Watch out
the list also offers Insert New Row to Retable; open both on a test table and keep the one whose fields match your columns.
Retable2

Create a Project

Action

In Make“Creates a project in the given Workspace.”

Opens a new Project inside the Workspace you pick, which gives a client or a department its own home for tables before any data exists.

When to use it
a deal is signed, and the account team wants a Project named after the new customer, ready before the kickoff call.
Watch out
each run creates one more Project, so run Get Projects first to check that the name is not already taken.
Retable3

Create a Retable

Action

In Make“Creates a Retable in the given Project.”

Builds a new Retable inside a given Project, so the table already exists when the next modules start filling it.

When to use it
every new event, course cohort or campaign gets its own table instead of sharing one crowded sheet.
Watch out
chain Create Column right after it when the table needs specific columns before any rows arrive.
Retable4

Create a Workspace

Action

In Make“Creates a Workspace.”

Creates a Workspace, the top level that holds your Projects; its result comes out as a bundle that the next module can map straight away.

When to use it
you set up a separate space for a new team or client account and want the scenario to build the whole structure.
Watch out
test it alone with Run once and check the result in Retable before chaining a Create a Project after it.
Retable5

Create Column

Action

In Make“Creates columns in the given Retable.”

Adds columns to a chosen Retable, which lets a scenario shape a table instead of someone clicking through the column menu.

When to use it
right after Create a Retable, when every new table must follow the same layout your team agreed on.
Watch out
try it on a test table first; a column added by mistake has to be removed by hand in Retable afterwards.
Retable6

Delete Row from Retable

Action

In Make“Deletes rows from the given Retable.”

Removes rows from a given Retable, which keeps a table limited to what is still active once a record is closed somewhere else.

When to use it
a customer unsubscribes in your email tool and their line should leave the prospect table.
Watch out
treat a deletion as final; try it with Run once on a copy of the table and check which rows it targets.
Retable7

Get One Project

Action

In Make“Retrieves information about the given Project.”

Returns the details of one Project, so later modules can reuse its information without anyone looking it up in Retable.

When to use it
a scenario already points to a Project and needs its details before writing into it.
Watch out
it reads a single Project; to go through all of them, Get Projects is the right pick.
Retable8

Get One Retable

Action

In Make“Retrieves information about the given Retable.”

Fetches information about a single Retable, handy when a later step needs to know about the table itself rather than its rows.

When to use it
before adding columns or rows, to confirm that the scenario is pointing at the right table.
Watch out
it describes the table, not its content; for the rows, Get Retable Data is the module to add.
Retable9

Get One Workspace

Action

In Make“Retrieves information about given Workspace.”

Brings back information about one Workspace, a quick way to give the rest of the scenario the context of the space it works in.

When to use it
a scenario that builds Projects for several teams checks the target Workspace first.
Watch out
if you are unsure which Workspace to pick in the module, Get Workspaces lists every one of them.
Retable10

Get Retable Data

Action

In Make“Retrieves data of the given Retable.”

Reads the data stored in a Retable and passes it on to the next modules, so a table can feed a report, an email or another tool.

When to use it
a sales lead wants the content of the pipeline table sent to the team as a summary message.
Watch out
check with Run once how many bundles come out before adding steps after it; each module run counts as one operation.
Retable11

Insert New Row to Retable

Action

In Make“Inserts new rows to the given Retable.”

Inserts new rows into the Retable you choose, turning data from another app into lines of the table as soon as the scenario runs.

When to use it
orders, form entries or tickets collected in different tools should sit side by side in one table.
Watch out
after Run once, open the test row in Retable to confirm that each value landed in the right column.
Retable12

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Calls any part (endpoint) of the Retable API with the connection you already set up, which covers whatever the other modules leave out.

When to use it
the action you need is missing from the list of 16 modules on this page.
Watch out
you write the request yourself, so keep the Retable API documentation open while you fill in the module.
Retable13

Update Row Data

Action

In Make“Updates rows in the given Retable.”

Updates rows in a given Retable, so a status, an amount or an owner changes in the table when it changes elsewhere.

When to use it
a deal moves forward in your CRM and the matching line in Retable should follow.
Watch out
the scenario needs to know which row to change; read the table with Get Retable Data first when that row is not already in a bundle.
Retable14

Get Projects

Search

In Make“Gets all Projects in the given Workspace.”

Lists all Projects of a given Workspace, and each Project comes out as its own bundle for the modules that follow.

When to use it
you need to loop over every client Project, or check that a name exists before Create a Project.
Watch out
a search can return zero, one or many bundles; the next module runs once per bundle and uses one operation each time.
Retable15

Get Retables

Search

In Make“Gets all Retables in the given Project.”

Returns every Retable found in a given Project, a simple way to reach all the tables of one client or one campaign in a single step.

When to use it
a Project holds one table per event and the scenario must read or update each of them.
Watch out
an empty Project gives zero bundles, so the modules placed after it have nothing to work on; check this with Run once.
Retable16

Get Workspaces

Search

In Make“Gets all Workspaces.”

Gets all the Workspaces of your account, the starting point when a scenario has to walk down from Workspace to Project to Retable.

When to use it
an agency keeps one Workspace per client and wants a scenario that touches each of them.
Watch out
every Workspace becomes a bundle, so the modules placed after this search run once for each one.
Need help

Need help automating Retable with Make?

A person reads every message.

FAQ

Retable and Make: common questions

01Is the Retable Make integration free?
Yes, Retable is a standard app in Make, available from the Free plan. That plan lets you keep 2 active scenarios, with at least 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 and allow unlimited active scenarios. You still need an active Retable account with an API key; the Retable pricing page covers its own subscription.
02What do you need to connect Retable to Make?
An active Retable account and its API key. You find the key in Retable by clicking your user name at the top right and opening the API tab, where you enable it if needed and copy it. In Make, add any Retable module, click Create a connection, give it a name if you like and paste the key. The same connection then serves all 16 Retable modules, so you only set it up once per account.
03Can a Retable scenario start without a trigger?
Yes. Retable has no trigger module in Make, so the scenario starts another way. The first option is the schedule: set it on the first module, every 15 minutes by default or down to 1 minute on a paid plan, and let a module such as Get Retable Data open the flow. The second option is to place the trigger of another app first, a form or a CRM for example, and add the Retable modules after it. Either way, Make only acts on Retable when the scenario runs.
04What if a Retable module is missing in Make?
Use Make an API Call. It calls any endpoint of the Retable API with the connection you already created, so an action missing from the 13 actions and 3 searches can still happen inside the same scenario. You write the request yourself, which means keeping the Retable API documentation at hand. The Make documentation for Retable lists no specific limit, so test each call with Run once and read the bundle it returns before switching the scenario on.
05Make or n8n for Retable?
It depends on what your team already runs. In Make, Retable comes with 16 modules and a connection built on your API key, and this page covers that setup step by step. Many apps also have an n8n node, so check whether Retable is one of them before comparing. Then weigh concrete criteria: whether each tool offers the actions you need, which tool your colleagues already know, and where your other automations live. Neither choice is wrong in itself; pick the one that covers your use case today.
Same platform

Other docs you might need on this stack.

Browse all integrations