Resources · Zapier integration

Caspio Zapier integrationAutomate Caspio with Zapier.

The Caspio Zapier integration gives you 7 triggers, 3 actions and 1 search to react to records in your Caspio tables and write back into them. All seven triggers are instant, and the app runs on the free plan as long as each Zap stays at two steps.

See the 11 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Caspio Zapier integration does with your tables

Caspio lets you build database apps in the cloud without writing code. Wired to Zapier, a table can start an automation the moment a record is added, changed or deleted, and other steps can create, update, delete or look up records for you.

Every trigger here is instant, which matters on a free plan.

Tables that keep each other in sync. A new application lands in your intake table and New Record fires at once. Update Record then sets the matching row in your tracking table, with no admin copying values across.

A clean-up that follows the user. When an operations manager deletes a client in one table, Deleted Record reacts, and Delete Record removes what belonged to that client in another table or view.

Lookups before writes. Find Record fetches one or more records with a filter, so the next step works on the right row instead of guessing.

What Zapier does not do for Caspio: anything outside the eleven operations described below, all of which work on records in a table or view. No setting adds another one. If your need is not on that list, look at the Caspio Make integration before you build, and read our Zapier review.

One more thing to keep in mind: every action works on a table or a view you name, so plan your tables before your Zaps.

Vocabulary

Zapier words you will meet on this page

Eight terms in plain English. Each one comes back further down without a second explanation.

Zap
The automation you build on Zapier: one trigger, then one or more actions that run every time the trigger event happens.
Trigger
The event in an app that starts the Zap. Once the Zap is on, Zapier waits for that event and nothing else.
Action
What the Zap does once started: the step that writes, sends or changes something for you in an app.
Task
The unit Zapier bills. One task equals one action your Zap completes successfully, and your plan counts those.
Polling vs instant
Zapier checks a polling trigger on a timer. An instant trigger is reported by the app itself as soon as the event happens.
Filter
A step that lets the Zap go on only when what arrived meets your condition, and stops it otherwise.
Search step
A step that looks up something that already exists in an app, so later steps can use what it found.
Connection
Your Caspio account linked to Zapier once, then reused by every Caspio step in every Zap you build.
Cost

What a Caspio Zap costs you in tasks

Zapier bills completed actions, not waiting time. Caspio is not a premium app, so it runs on the free plan (operations read on 1 October 2026, integration version CaspioCloudDatabaseCLIAPI@2.0.11).

  • TriggerFree, never counted
  • Each successful action1 task
  • Free plan100 tasks a month, two-step Zaps only
  • Premium appNo, Caspio works on the free plan

The trigger never costs a task, however many records change. Each action that succeeds counts once, so a Zap with three actions uses three times what a one-action Zap uses. A failed action is not counted. The free plan gives you 100 tasks a month and unlimited Zaps, but each Zap stops at two steps: one trigger, one action. Add a filter, a Find Record search or a second action, and you have a multi-step Zap, which needs a paid plan. A few apps and actions take more than one task, so check your usage after the first runs.

Connect

Connect Caspio to Zapier in three steps

  1. 01

    Open the Apps page

    In your Zapier account, open Apps and click + Add connection. In the dialog, type Caspio in the search box and select it from the results that show up.

  2. 02

    Sign in to Caspio

    Click Add connection. A new tab opens on Caspio: sign in with the account your Zaps should act as. It needs read or write access on every table and view you want to automate, including the ones a colleague owns.

  3. 03

    Grant access

    Allow Zapier to use the account. From then on, every Caspio step in every Zap reuses this connection, so you set it up once and simply pick it while building.

First Zap

Your first Zap: an intake table that updates a tracker

GoalWhen a new record arrives in your intake table, Caspio updates the matching record in your tracking table, but only for the records that carry the value you choose.

  1. 01

    Build: pick the trigger

    Start a new Zap, choose Caspio and the New Record event, then your connection. Pick the intake table and its event sources. A lightning bolt shows the trigger is instant.

  2. 02

    Test the trigger

    Run the test. Zapier brings back the three most recent records of that table, so you map the next steps on real data rather than on an empty sample.

  3. 03

    Add the filter

    Click the plus icon and add Filter. Set the field of your own table to look at, a text rule and the value entered when the record is created. A number rule on a text field never passes.

  4. 04

    Add the action

    Choose Update Record, set the data source type to a table and pick your tracking table, then the filter field and operator that point to the one row to change. Map the new values.

  5. 05

    Test, then publish

    Test the action and check the tracker in Caspio. Click Publish. With a filter, this is a multi-step Zap, so it needs a paid plan.

Triggers

Caspio triggers: seven record events, all instant

7 events start a Zap when something happens in Caspio, and 7 of them are instant: the app calls Zapier straight away, whatever your plan.

1

Deleted Record

Instant trigger

In Zapier“Triggers when a record is deleted in a table.”

Starts your Zap when a record is removed from the table you pick. Other tools learn that something is gone without anyone having to tell them.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a compliance officer wants a trace each time a case file disappears from the case table.
Watch out
the table and its event sources are both required, so the account you connect has to see that table.
2

New or Deleted Record

Instant trigger

In Zapier“Triggers when a record is added or deleted in a table.”

Reacts to both ends of a record's life: it fires when a row is added and again when one is removed. One Zap covers arrivals and departures in the same table.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a membership coordinator keeps a headcount in another system that must go up and down with the members table.
Watch out
the next steps have to tell a new row from a deleted one, usually with a filter, which needs a paid plan.
3

New Record

Instant trigger

In Zapier“Triggers when a record is added into a table.”

Fires each time a row is added to the table you choose. It is the classic starting point for any intake process.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a training provider sends each new enrollment straight into the scheduling process.
Watch out
rows that were in the table before you publish the Zap are never picked up.
4

New, Updated or Deleted Record

Instant trigger

In Zapier“Triggers when a record is added, updated or deleted in a table.”

Catches every event on a table: additions, edits and deletions alike. It is the broadest Caspio trigger, built for a full audit trail rather than one precise workflow.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
an IT lead logs every change to a sensitive table in a separate place for review.
Watch out
each edit counts as an event, so never let this trigger create records, or you will collect duplicates.
5

New or Updated Record

Instant trigger

In Zapier“Triggers when a record is added or updated in a table.”

Starts the Zap when a row is added and again every time it is edited. Use it when the latest version of a record matters more than the moment it was first saved.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a field service manager mirrors the current state of each job to the dispatch tool.
Watch out
it fires on every save, so pair it with Update Record, never with Create Record, to avoid duplicates.
6

Updated or Deleted Record

Instant trigger

In Zapier“Triggers when a record is updated or deleted in a table.”

Reacts to changes to existing rows and to their removal, but ignores brand new ones. It suits tables where creation is handled elsewhere and only later changes need to travel.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a property manager keeps listings elsewhere in line when a unit is edited or taken off the table.
Watch out
an action that updates the same table sets the Zap off again, in a loop.
7

Updated Record

Instant trigger

In Zapier“Triggers when a record is updated in a table.”

Fires when someone edits a row in the chosen table, and only then. It is the trigger for status changes, approvals and any field that moves a record to its next stage.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
an HR assistant acts as soon as a leave request is marked approved.
Watch out
every edit fires it, not just the one you care about, so a filter on the right field is usually needed.
Actions

Caspio actions: what your Zap can write

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

1

Create Record

Action

In Zapier“Creates a record in a table or view”

Adds a new row to the table or view you pick, filled with the values you map from earlier steps.

When to use it
a payment confirmed elsewhere becomes an order line in your Caspio orders table, with no retyping.
Watch out
the data source type is required, and only a trigger that fires once per item should feed it.
2

Delete Record

Action

In Zapier“Deletes one or more records in a table or view”

Removes one or more rows from a table or view, again picked by a filter field and an operator.

When to use it
a cancelled booking in another tool clears its reservation row so the slot opens up.
Watch out
test it on a copy of the table first, since a broad filter can wipe more rows than you meant.
3

Update Record

Action

In Zapier“Updates one or more records in a table or view”

Changes the values of one or more existing rows, chosen by a filter field and an operator you set.

When to use it
when a job is marked done in your field tool, the matching row in Caspio switches to closed.
Watch out
a loose filter matches several rows, and all of them get the new values.
Searches

The Caspio search step

1 search step looks for data that already exists in Caspio, so a later step can use it.

Caspio has one search. It sits at the bottom of the action event list, under the SEARCH heading, and hands the records it finds to the steps that follow.

1

Find Record

Search

In Zapier“Retrieves one or more records from a table or view”

Retrieves one or more rows from a table or view, matched on a filter field and an operator, so later steps can read them.

When to use it
before you update a customer row, pull it with a field that identifies it to check it really exists.
Watch out
several rows can match, so decide what happens then, and remember a search makes the Zap multi-step.

The three settings every search exposes

  1. Successful if no search results are found?
    Left on its default, a search that finds nothing stops the Zap there. Switch it on and the Zap goes on without a record.
  2. Create X if it doesn't exist yet?
    This box turns a search into find-or-create. Find Record does not offer it on Caspio, so create the row with Create Record.
  3. If multiple search results are found?
    Three ways out: keep the first match, which is the default, stop the Zap, or pass all matches on.
When it breaks

When a Caspio Zap breaks

Zapier attaches no help article to Caspio, so the cases below come from how Zaps behave in general and from what the Caspio steps require.

On a database app, the costly mistakes are quiet ones: a Zap that loops, or one that edits more rows than planned. If a run fails and the reason is not obvious, the Zapier troubleshooting guide walks through the next checks.

  • Existing rows are never processed

    A Zap only reacts to what happens after you publish it. Records already sitting in the table stay untouched, and moving that backlog is a separate job.

  • An update Zap that triggers itself

    Updated Record watching a table, then Update Record writing into the same table, sets the Zap off again on every run and burns through your tasks.

  • A bulk import that gets held back

    Importing a large batch of rows at once can fire a flood of runs. Zapier's flood protection may hold them back rather than process them all.

  • A filter that matches too many rows

    Update Record and Delete Record act on every row their filter matches. A filter on a shared value, like a status, can change or delete far more than one record.
Need help

Need help automating Caspio with Zapier?

A person reads every message.

FAQ

Caspio Zapier integration: frequent questions

01Is the Caspio Zapier integration free?
Yes, as long as your Zap stays at two steps. Caspio is not a premium app, so it runs on the free plan, which comes with 100 tasks a month and unlimited Zaps. The limit is the shape of the Zap: one trigger and one action, nothing more. Add a filter, a Find Record search or a second action and it becomes a multi-step Zap, which needs a paid plan. For a first test of a single trigger and action, the free plan is enough.
02How many tasks does a Caspio Zap use?
One task per action that completes. The trigger is free, so Caspio reporting a new, updated or deleted record costs nothing on its own. A Zap that runs Update Record and then Create Record uses two tasks per successful run. An action that fails is not counted. Be careful with the broad triggers, such as New, Updated or Deleted Record, since every edit on a busy table can start a run and every run that reaches an action costs a task.
03Is Caspio on Zapier real time?
Yes, for all seven triggers. Every Caspio trigger is instant: Caspio tells Zapier as soon as a record is added, updated or deleted, and the Zap starts right away whatever your plan. The plan interval grid, 15 minutes on the free plan, does not apply to them. In the editor, an instant trigger shows a lightning bolt. There is nothing to set on your side, because whether a trigger is instant is decided by the app itself.
04What does it take to connect Caspio to Zapier?
A Caspio account and a Zapier account. Sign in with a Caspio user that can read or write every table and view you plan to automate, including those owned by colleagues. Then know which table each step targets: triggers ask for a table and its event sources, and every action and the search ask for a data source type, either a table or a view. Those boxes are required, so it helps to list them before you open the editor.
05Can a Caspio Zap update or delete the wrong records?
Yes, if the filter is too loose. Update Record and Delete Record both act on one or more records, picked by a filter field and an operator. Point the filter at a value many rows share, such as a status, and every one of them changes or disappears. Use a field that identifies a single row, test on a copy of the table first, and check the result in Caspio before you publish the Zap.
06What if the Caspio operation you need is not listed?
Then Zapier cannot do it with Caspio directly. The visible list is seven triggers, three actions and one search, read on 1 October 2026. All of them work on records in a table or view, and anything outside that list is out of reach from the editor. Combining Find Record with Update Record or Create Record covers many needs. If yours is outside that, compare with the Make integration of Caspio before building a workaround, and keep in mind the list can change with new versions.
07Zapier, Make or n8n for Caspio?
It depends on where your other tools live and on who will maintain the workflows. On Zapier, Caspio gives you seven instant record triggers and record actions, which covers most syncing between tables and other apps. If your project needs an operation missing from the list, compare what each tool offers for Caspio before choosing. Price your volume too, since Zapier bills every completed action, and a busy table can produce many runs. No single tool wins for every team.
Same platform

Other docs you might need on this stack.

Browse all integrations