Data & Storage · Integration
Tadabase
Add Tadabase to your product for your customers, and give your AI agents governed access to it.
Tadabase is a no-code builder where the database comes first: a customer defines data tables, gives them fields, and the app they assemble is a view over the records in those tables. For an integration that is unusually convenient and unusually demanding at once. Convenient, because the object model is exactly tables, fields and records and the REST API works in those terms. Demanding, because every table in every customer's app was invented by that customer, so there is no shared schema at all and field mapping is the entire integration. Credentials belong to an app rather than a user, an app id with its own key and secret, so a customer running several apps is several connections. fastn holds those credentials per tenant, pages through large tables, and keeps the mapping as configuration so a customer adding a field needs no release from you.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let each customer connect their own Tadabase app, so your product works with the tables they built themselves.
Discover a table's fields at connect time, because no two customers' apps share a schema.
Create or update records from your product, so a workflow that starts in your app finishes in theirs.
Support a customer running several Tadabase apps as several connections, each with its own app id and key.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent looks up a record in one customer's table to ground an answer, with the read logged.
An agent adds or updates a record within scoped permissions, and the fields it wrote are recorded.
An agent lists what fields a table actually has before it attempts to write to it.
Example prompt
Find the records in this table where the status field is still open and tell me how old the oldest is.
Set up Tadabase in 4 steps
- 01Enable the Tadabase connector in your fastn dashboard.
- 02Have each customer supply the app id, key and secret for their own Tadabase app, one connection per app.
- 03Read the tables and fields that app defines, then map the ones your product uses and mark which are writable.
- 04Call it from your product and expose the same connection to your agents through the MCP gateway.
Why teams use the Tadabase integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Tadabase integration without building it. Your customers connect their own Tadabase 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 Tadabase update is not your on-call problem.
- One integration serves your product and your agents. The same governed Tadabase 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
monday.comOften used alongside
Tools the same teams tend to run next to Tadabase, across other categories.
Anthropic Claude
OpenAI
Azure OpenAI
Hugging FaceTadabase integration FAQ
How do I add a Tadabase integration to my product?
Enable the Tadabase connector in your fastn dashboard, then let each customer authenticate their own Tadabase account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Tadabase client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Tadabase account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Tadabase 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 Tadabase 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 looks up a record in one customer's table to ground an answer, with the read logged.
Who maintains the Tadabase integration?
fastn does. When Tadabase 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 Tadabase 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 Tadabase 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 Tadabase integration?
A common starting point: let each customer connect their own Tadabase app, so your product works with the tables they built themselves. 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 Tadabase integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Tadabase does not change your per-connector cost. You can start free with 3 connected accounts.
Add Tadabase to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.