Caspio
DatabaseRead and write data in your Caspio online database. Agents list tables and views, query records with filters, and insert, update, or delete rows to keep Caspio-built applications in sync with the rest of your stack.
What This Integration Enables
A Caspio app is a production application; the fact that nobody wrote code does not make its database less real. Orders, customers, casework, and compliance records live in those tables, and they deserve the same operational discipline a production database gets: schema-aware writes, previewed bulk operations, and an audit trail for changes. That is what FlowRunner brings. Agents read and write Caspio tables and views with SQL-style precision, and the discipline is built into the flow instead of depending on whoever happens to be careful today. - Sync form submissions, orders, and leads captured anywhere in the stack into Caspio tables as records - Read rows from tables and multi-table views to drive downstream automation and reporting - Bulk-update matching records, with the Where clause reviewed before it executes - Discover table names and field definitions at runtime to build schema-aware flows that survive app changes - Report on saved views that join data across tables, without rebuilding the joins elsewhere The connector's bulk write operations act on everything a filter matches, which is exactly the kind of leverage that belongs behind a [human-in-the-loop](/concepts/human-in-the-loop) gate.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Signups land in the app the team actually uses
A new customer registers through [Shopify](/integrations/shopify). The agent calls Query Table Records to check for an existing row keyed on email, then Insert Table Record with the customer's details mapped to the table's fields, capturing the auto-generated primary key from the returned record. A message posts to [Slack](/integrations/slack) so the sales team sees the new account inside the Caspio app they work from, not in a system they never open.
Every interaction logged against the record
When an email arrives in the shared inbox through [Gmail](/integrations/gmail-service), the agent looks up the sender with Query Table Records, then calls Update Table Records with a Where clause scoped to that customer's key to stamp the last-contact date and append the interaction. The Caspio app's activity history stays current without anyone copying emails into a form, and the Where clause is always scoped to a single verified record.
Views become the reporting layer
The operations dashboard needs data that spans three tables: customers, orders, and support tickets. Instead of rebuilding those joins in a BI tool, the agent calls Query View Records against the saved view that already joins them, applies the period filter, and writes the results to [Google Sheets](/integrations/google-sheets) for the Monday review. The logic lives in one place, in Caspio, and the report inherits every improvement the app builder makes to the view.
Human-in-Loop Highlight
Delete Table Records removes every row a Where clause matches, permanently, and Update Table Records rewrites every row it matches. The API requires a Where clause precisely because the failure mode is obvious: a filter that is one condition too loose takes a swath of production records with it, and there is no undo. So FlowRunner agents treat the Where clause itself as the thing under review. Before any bulk write, the agent runs the identical filter through Query Table Records, presents the operations owner with the match count, a sample of affected rows, and the literal clause about to execute. The person approves the filter, not the idea of cleanup. Only then do the bulk operations run, and the completion summary records what changed. Machine speed for the query and the write; human judgment for the blast radius.
Agent Capabilities
8 actionsTables
2- List Tables Lists every table in the Caspio account. The discovery step that lets flows adapt to the app as built, not as remembered.
- Describe Table Returns a table's field definitions: names, data types, and which fields are unique or primary keys. The schema check that runs before inserts, updates, and queries.
Records
4- Query Table Records Retrieves records with SQL-style filtering, column selection, sorting, grouping and aggregation, row caps, and paging. Both the lookup step in sync flows and the mandatory preview before bulk writes.
- Insert Table Record Inserts one record with field values keyed by field name, and can return the created row so flows capture auto-generated keys.
- Update Table Records Updates every record matching a required Where filter with the supplied values, optionally returning the affected rows. Runs behind the reviewed-filter gate when the scope is more than one known record.
- Delete Table Records Permanently deletes every record matching a required Where filter and returns the count removed. The operation this page's human gate exists for.
Views
2- List Views Lists the saved views in the account, including multi-table views.
- Query View Records Retrieves records from a view with the same filtering, selection, sorting, grouping, and paging controls as table queries. The reporting read that reuses joins the app already defines.
Frequently Asked Questions
What can FlowRunner do with Caspio?
FlowRunner agents can run List Tables, Describe Table, and Query Table Records in Caspio, plus 5 more actions.
Does connecting Caspio to FlowRunner require OAuth?
Yes. Caspio connects to FlowRunner with OAuth 2.0, so agents authenticate without handling raw credentials.
Can Caspio trigger a FlowRunner workflow automatically?
Caspio doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with Caspio
$100 in credits. No card required. Connect in minutes.