Resources · Make integration

Caspio Make integrationAutomate Caspio with Make.

Can Make keep your Caspio database in step with the rest of your tools? The Caspio Make integration offers 32 modules, including 21 actions and 9 searches, for teams that run their data in Caspio. This page connects your account and walks you through a first scenario.

Try the Caspio integration on Make See the 32 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Caspio Make integration automate?

The Caspio Make integration links your Caspio account to Make, a no-code tool where you build scenarios: automations made of modules, each module being one brick such as an action or a search. Once connected, a scenario can create, update or delete table records, reshape fields and put DataPages online, all driven by events in your other apps.

Records that follow your sales. When a deal closes in your CRM, Search Table Records finds the client row and Update a Table Record writes the new status, so Caspio stays the list everyone trusts.

Pages that open and close on cue. A registration form built as a DataPage goes live with Deploy a DataPage when an event is confirmed, and goes offline with Un-deploy a DataPage once seats are gone.

A structure that grows with your forms. A new project gets its own table with Create a Table, then its columns with Create a Table Field, instead of a round of manual setup.

What Make does not do here: the Make directory lists both Caspio triggers as not usable, so no working module lets a Caspio change start a scenario by itself; the event comes from another app, or from the schedule. The documentation also requires a paid Caspio account. To see how plans count usage, read Make pricing, and for a wider look at the tool, the Make review. n8n often has a node for the same app, and n8n vs Make puts the two side by side.

Connect

How do you connect Caspio to Make?

01
Add a Caspio module
In a new scenario, click the + and search for Caspio, then pick a module, Search Table Records for instance. In the module panel, click Create a connection. A connection is your Caspio account linked to Make once, then reused by every Caspio module.
02
Name it and enter your credentials
Give the connection a name you will recognize later, such as the team or account it belongs to. The Make documentation connects Caspio with client credentials that you obtain from your Caspio account: paste them in the fields Make shows.
03
Save and check the result
Click Save. The connection now sits in the module, and Make can list what your account holds in the next fields. If Make later asks you to reauthorize, its documentation describes the connection renewal steps.

First scenario

Your first Caspio scenario, step by step

GoalWhen a form in another app sends an update, Make finds the matching Caspio row and updates it.

01
Create the scenario
Open the Scenarios page, create a new scenario and click the +. Pick the app that receives your update first, a form tool for instance: its module opens the flow.
02
Add Search Table Records
Click the + on the right, search for Caspio and choose Search Table Records. Create the connection, pick the table, and use the email from the form to find the right row.
03
Add Update a Table Record
Add Update a Table Record after the search. Map the row found by the search, then map the new values from the form into the columns you want to change.
04
Test with Run once
Click Run once and send a test entry through the form. Open each module to read the bundles it received: the search should return one row, and the update should touch that row only.
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, and each new form entry reaches Caspio without anyone retyping it.

Triggers

What can start a Caspio scenario?

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

Caspio1Watch Records Created

Watch Records Created

Scheduled trigger

In Make“Module can't be implemented. Tables don't always have primary key that can be used as ID to determine their order.”

On paper, this trigger would hand your scenario one bundle for each new Caspio record. The Make directory, however, describes it as a module that cannot be implemented, because Caspio tables do not always have a primary key that sets their order.

How it fires

scheduled, Make checks the app on the scenario's schedule.

When to use it

read it as a warning rather than a plan, and open your flow with another app's trigger or with Search Table Records under a schedule.

Watch out

a scheduled search rereads the table on each run, so keep its criteria tight: every row it returns costs an operation downstream.

Caspio2Watch Records Events

Watch Records Events

Instant trigger

In Make“Module can't be implemented yet, Caspio don't have webhooks.”

An instant trigger like this one would let Caspio warn Make the moment a record changes. According to the Make directory, it is not implemented yet, because Caspio has no webhooks.

How it fires

instant, the app calls Make through a webhook as soon as it happens.

When to use it

keep the start of the flow on the other side: the app where the event happens triggers the scenario, and the Caspio modules follow it.

Watch out

do not promise your team instant updates on Caspio records through this module.

Modules

What the Caspio modules do

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

Caspio1

Create a Table

Action

In Make“Creates a new table.”

Adds a brand-new table to your Caspio account, so a scenario can prepare the storage a new project needs before any record lands in it.

When to use it

a new client or event is signed in another tool and deserves its own table instead of a shared one.

Watch out

a new table has no columns you chose yet, so plan Create a Table Field right after it.

Caspio2

Create a Table Field

Action

In Make“Creates a new table field.”

Gives an existing table one more column, which saves a trip into Caspio each time a form starts asking for new information.

When to use it

right after Create a Table, or when a process adds a question the table cannot store yet.

Watch out

if the scenario may run twice on the same table, check the columns with List Table Fields before adding one.

Caspio3

Create a Table Record

Action

In Make“Creates a new table record.”

Writes one new row in a Caspio table from the data of the previous module, so a lead, an order or a sign-up lands in your database without copy and paste.

When to use it

another app collects the information, a form or a shop for instance, and Caspio holds the reference list.

Watch out

one bundle in gives one row out, so a search placed before it can multiply the rows.

Caspio4

Create a View Record

Action

In Make“Creates a new view record.”

Adds a record through a Caspio view rather than straight into a table, so new entries follow the same view your team already works from.

When to use it

your process is organized around a view, and new rows coming from another app should enter through it.

Watch out

it adds a record to a view that already exists; List Views shows which ones you can pick.

Caspio5

Delete a Table Field

Action

In Make“Deletes an existing table field.”

Removes a column from a Caspio table, which keeps a table readable once a question has left your forms for good.

When to use it

a cleanup scenario retires the fields someone flagged as obsolete after reviewing them with List Table Fields.

Watch out

treat the deletion as final and try the scenario on a test table with Run once before you switch anything on.

Caspio6

Delete a Table Record

Action

In Make“Deletes an existing table record.”

Deletes one row from a Caspio table, handy when a record is cancelled in another tool and should not survive in your database either.

When to use it

place it after Search Table Records to target the exact row, a duplicate sign-up for example.

Watch out

a search can return several bundles and this module then runs once per bundle, so check the search result with Run once first.

Caspio7

Delete a View Record

Action

In Make“Deletes an existing view record.”

Clears a row through a Caspio view, so the deletion follows the view your team uses to read and edit that data.

When to use it

the record was found with Search View Records and you want the whole flow to stay on the view side.

Watch out

Make cannot bring a deleted record back, so read the search output with Run once before this module runs for real.

Caspio8

Deploy a DataPage

Action

In Make“Deploys an existing datapage.”

Publishes one DataPage from a scenario, so a form or report goes live at the moment your process decides rather than when someone thinks of it.

When to use it

a page tied to an event, a registration form for example, should open once a record says the event is confirmed.

Watch out

add Get a DataPage Deployment Code behind it if another tool needs the code afterwards.

Caspio9

Deploy all DataPages

Action

In Make“Deploys all datapages in the application.”

Puts every DataPage of an application online in one step, which beats chaining Deploy a DataPage for each page after a release.

When to use it

an application moves from preparation to launch and all its pages should go public together.

Watch out

it acts on the whole application, so pages you meant to keep offline go live as well.

Caspio10

Get a DataPage Deployment Code

Action

In Make“Retrieves an existing datapage deployment code.”

Hands the scenario the deployment code of a DataPage, so you pass it to the next module instead of copying it out of Caspio by hand.

When to use it

after Deploy a DataPage, when a teammate or another app needs the code to place the page where visitors see it.

Watch out

Run once shows the code in the output bundle, the simplest way to see what the next module will receive.

Caspio11

Get Application Properties

Action

In Make“Retrieves existing application properties.”

Reads the properties of one Caspio application and turns them into a bundle, giving later modules a reliable reference without anyone opening Caspio.

When to use it

a scenario that works across several applications must confirm which one it is about to touch.

Watch out

this module reads a single application; List Applications is the one that returns them all.

Caspio12

Get a Table Field

Action

In Make“Retrieves an existing table field.”

Returns the definition of one table field, so the scenario can check how a column is set up before it writes anything.

When to use it

before Update a Table Field, to read the current setup and keep a trace of it in the next module.

Watch out

it reads one field only; List Table Fields covers the whole table when you do not know the field yet.

Caspio13

Get DataPage Properties

Action

In Make“Retrieves existing datapage properties.”

Pulls the properties of a DataPage into the scenario, the quickest way to see what Make knows about a page before you publish or retire it.

When to use it

a later step, Deploy a DataPage or Un-deploy a DataPage, needs details of the page to pick the right one.

Watch out

start with List DataPages if you do not have the page at hand yet.

Caspio14

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Opens the rest of the Caspio API to your scenario with the connection you already set up, so a need that no listed module covers does not stall the project.

When to use it

none of the other Caspio modules offers the operation you need on applications, tables or records.

Watch out

you describe the request yourself, so keep the Caspio API reference open next to the module.

Caspio15

Reset a Password Field

Action

In Make“Resets a password filed value.”

Resets the value of a password field in a Caspio table, so a support request is handled by the scenario rather than by an admin clicking through the table.

When to use it

a user asks for a reset through a form in another app, and the matching record was found with Search Table Records.

Watch out

List Password Fields shows which fields hold passwords before you point this module at one.

Caspio16

Un-deploy a DataPage

Action

In Make“Un-deploys an existing datapage.”

Takes one DataPage offline from a scenario, closing a form or report at the moment your process says so.

When to use it

registrations are full or an offer has ended in another tool, and the matching page should stop welcoming visitors.

Watch out

Deploy a DataPage brings it back, so the two modules make a clean pair for pages that open and close.

Caspio17

Un-deploy all DataPages

Action

In Make“Un-deploys all datapages in the application.”

Pulls every DataPage of one application offline in a single step, useful when the whole application has to go quiet.

When to use it

a project closes or a maintenance phase starts, and no page of that application should stay public.

Watch out

nothing is spared, so if some pages must stay online, list them with List DataPages and use Un-deploy a DataPage instead.

Caspio18

Update a Table Field

Action

In Make“Updates an existing table field definition.”

Changes the definition of an existing table field, so a column evolves with your process without anyone editing the table by hand.

When to use it

the same change has to reach several tables found with List Tables, instead of being repeated screen after screen.

Watch out

read the current setup with Get a Table Field first, so the scenario keeps a record of what was there before.

Caspio19

Update a Table Record

Action

In Make“Updates an existing table record.”

Edits a row that already exists in a Caspio table, which keeps your database in step with what changes in your other tools.

When to use it

a status moves in your CRM or helpdesk and the matching Caspio row should carry the same status.

Watch out

the usual pattern puts Search Table Records before it, so the update knows which row to touch.

Caspio20

Update a View Record

Action

In Make“Updates an existing view record.”

Changes a record through a Caspio view, so the edit goes through the same view your team works from.

When to use it

the row was found with Search View Records and the flow should not leave the view for the update.

Watch out

for edits made directly in a table, Update a Table Record is the matching module, not this one.

Caspio21

Update Password Field's Value

Action

In Make“Updates an existing password field's value.”

Sets a new value in a password field, letting a scenario deliver a password chosen elsewhere straight into the right Caspio record.

When to use it

an onboarding flow in another app produces the password and Caspio must store it for the new user.

Watch out

Reset a Password Field is the module to pick when you want a reset rather than a value you supply.

Caspio22

List Applications

In Make“Retrieves a list of all applications.”

Returns every application of your Caspio account as separate bundles, a good starting point for a scenario that must work on more than one.

When to use it

an inventory sheet in another tool should list your applications, with Get Application Properties behind each one.

Watch out

each bundle feeds the next module once, and each of those runs is an operation, the unit Make counts on your plan.

Caspio23

List DataPages

In Make“Retrieves a list of all datapages.”

Brings back all DataPages as a list of bundles, so the scenario can act on each page without you naming them one by one.

When to use it

before Deploy a DataPage or Un-deploy a DataPage, when only some pages of the application should change state.

Watch out

the list covers every page, so read it with Run once before you connect an action behind it.

Caspio24

List Password Fields

In Make“Retrieves a list of all password fields.”

Shows which fields of your tables store passwords, which keeps the scenario from pointing a reset at the wrong column.

When to use it

you set up Reset a Password Field or Update Password Field's Value and want to pick the field from what Caspio really holds.

Watch out

it lists fields, not users, so the account itself still comes from Search Table Records.

Caspio25

List Table Fields

In Make“Retrieves a list of all table fields.”

Lists the fields of a table, so the scenario knows which columns it can fill or check before any write.

When to use it

several teams share a table and the scenario should confirm a column exists before Create a Table Field adds it.

Watch out

it describes the columns, not the rows; the data itself comes from Search Table Records.

Caspio26

List Tables

In Make“Retrieves a list of all tables.”

Gives you every table of the account, one bundle each, the starting point of any scenario that audits or reshapes your structure.

When to use it

a change such as a new column has to reach many tables, handled by Create a Table Field right after the list.

Watch out

every table found leads to one run of the next module, so add the action only once Run once shows the right tables.

Caspio27

List Tasks

In Make“Retrieves a list of all tasks.”

Retrieves the tasks of your Caspio account in a list, so their state can travel to the tool where your team follows its work.

When to use it

a spreadsheet or project tool should mirror the Caspio tasks instead of relying on a manual export.

Watch out

the Make documentation does not describe what a task contains, so look at the output bundles with Run once before mapping anything.

Caspio28

List Views

In Make“Retrieves a list of all views.”

Lists the views available in your account, which lets the scenario choose the right view before it reads or edits records through it.

When to use it

a flow built on Search View Records must work across several views without typing each name by hand.

Watch out

it returns the views themselves, not their records; those come from Search View Records.

Caspio29

Search Table Records

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

Finds the table rows that match your criteria, or all of them when you leave the search open, and passes each one on as a bundle.

When to use it

before any update or deletion, to find the row that matches an email or an order number coming from another app.

Watch out

an open search can return the whole table, and each row then costs an operation in every module that follows.

Caspio30

Search View Records

In Make“Searches for view records or lists them all.”

Looks up records through a view, or lists everything the view shows, so the scenario works on the same data your team sees in Caspio.

When to use it

the view already narrows the data to what matters, active members for example, and the scenario should stay within it.

Watch out

it feeds Update a View Record and Delete a View Record; for raw tables, Search Table Records is the right pick.

Need help

Need help automating Caspio with Make?

A person reads every message.

FAQ

Caspio and Make: common questions

01Is the Caspio Make integration free?

Yes on the Make side: Caspio is a standard app, available from the Free plan. That plan allows 2 active scenarios, at least 15 minutes between two scheduled runs, 5 minutes of execution per run and files up to 5 MB. Paid plans (Core, Pro, Teams and Enterprise) bring the interval down to 1 minute and count usage in credits per month. On the Caspio side, the documentation requires a paid Caspio account, so the free part stops at Make.

02What do you need to connect Caspio to Make?

A paid Caspio account, a Make account and the client credentials you obtain from Caspio. In a scenario, add any Caspio module, click Create a connection, name it, enter the credentials and save. Every Caspio module of your scenarios then reuses that connection. If it asks for reauthorization later, the Make documentation describes the renewal steps. The exact Caspio screens that give the credentials are covered in that documentation, not on this page.

03Does the Caspio trigger in Make work in real time?

No, not today. Watch Records Events is typed as an instant trigger, yet the Make directory says it cannot be implemented yet because Caspio has no webhooks. Watch Records Created, the scheduled one, is described as not implementable either, since Caspio tables do not always have a primary key to order them. To start a Caspio scenario anyway, open the flow with a trigger from another app, or put Search Table Records first and let the schedule run it, every 15 minutes by default.

04What if a Caspio module is missing in Make?

Use Make an API Call. It sends a request to any endpoint of the Caspio API with the connection you already have, so there is no second login to set up. It covers what the other listed modules leave out, on applications, tables, records or DataPages. The documentation gives no numbered limit for Caspio in Make, so test each request with Run once rather than planning around a quota. If the need sits outside Caspio altogether, another app from the Make catalog can take over that step.

05Make or n8n for Caspio?

It depends on the tool your team already knows and on the modules you need. On Make, Caspio comes with 32 modules: 21 actions including Make an API Call, 9 searches, and 2 triggers that the directory marks as not usable. n8n often has a node for the same app, so check its catalog for Caspio before you decide. List the operations your process really needs, compare what each side offers for them, and pick the tool where your first scenario is clearest to build and to read.

Add a Caspio module

Name it and enter your credentials

Save and check the result

Create the scenario

Add Search Table Records

Add Update a Table Record

Test with Run once

Schedule and switch it on

Need help automating Caspio with Make?