Data & Storage · Integration
Caspio
Add Caspio to your product for your customers, and give your AI agents governed access to it.
Embed a Caspio integration so your customers can read and write their own tables and records from inside your product, with governed agent access to the same data. Because every Caspio app has its own schema, table and field mapping is configuration per customer rather than code, so a schema change on their side does not mean a release on yours. Pagination and throttling are handled for you, and initial backfills are rate-limited so a large import does not exhaust a customer's allowance.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let customers read records from their own Caspio tables into your product, mapped to their fields.
Create and update records from your product so users do not switch between apps.
Read table schemas at runtime so your product adapts to each customer's own structure.
Trigger your product when a record is created or updated so downstream steps run immediately.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent queries a customer's tables before answering a question grounded in their own data.
An agent creates or updates a record within governed permissions, with the action audited.
An agent reacts to a record change and runs the next workflow step.
Example prompt
Find records in the requests table with no status set and created in the last week.
Set up Caspio in 4 steps
- 01Open the Caspio connector from your fastn dashboard.
- 02Have each customer authenticate their Caspio account with least-privilege credentials.
- 03Map the tables and fields your product uses, then enable actions and triggers.
- 04Call them from your product, or expose them to an agent through the MCP server.
Why teams use the Caspio integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Caspio integration without building it. Your customers connect their own Caspio account inside your product and work their records, datasets and fields there, with no per-customer code on your side.
- Handle the part that actually costs time: schemas differ per customer and change without notice, and volumes can be large. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a Caspio update is not your on-call problem.
- One integration serves your product and your agents. The same governed Caspio connection powers in-product features and gives AI agents scoped, audited access, so you read and write your customers' data where it already lives without wiring it twice.
Used by these teams
Compare with
Airtable
PostgreSQLWorks well with
NotionOften used alongside
Tools the same teams tend to run next to Caspio, across other categories.
Anthropic Claude
OpenAI
Azure OpenAI
Hugging FaceCaspio integration FAQ
How do I add a Caspio integration to my product?
Enable the Caspio connector in your fastn dashboard, then let each customer authenticate their own Caspio account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Caspio client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Caspio account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Caspio account and only ever sees their own records, datasets and fields. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this Caspio integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent queries a customer's tables before answering a question grounded in their own data.
Who maintains the Caspio integration?
fastn does. When Caspio changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Does the Caspio integration adapt when a customer's schema changes?
Schema and field mapping is configuration per customer, so a change on their side is a mapping update rather than a code change and a release on yours.
How are large Caspio reads handled?
Pagination and throttling are handled for you, and initial backfills are rate-limited so a large import does not exhaust a customer's API allowance.
What can I build with the Caspio integration?
A common starting point: read records from their own Caspio tables into your product, mapped to their fields. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the Caspio integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Caspio does not change your per-connector cost. You can start free with 3 connected accounts.
Add Caspio to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.