Data & Storage · Integration
NocoDB
Add NocoDB to your product for your customers, and give your AI agents governed access to it.
NocoDB puts a spreadsheet interface over a real database, which means the schema is genuinely relational underneath even though customers edit it like a grid. Links between tables are first-class rather than a text field convention, so an integration that ignores them will return an identifier where a user expects a name. Reading through a view carries the customer's filters and sort order, which saves reimplementing their logic and keeps your product consistent with what they see. There is a hosted cloud alongside the widely self-hosted build, and per-account API tokens make per-tenant connections straightforward. fastn absorbs the schema drift when a customer renames a field.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let a customer connect their own NocoDB base so your product works with tables they already maintain.
Read through a view so the customer's own filters and ordering come along.
Resolve linked records so your product shows a name rather than a row identifier.
Create or update records, with field mapping handled as configuration rather than code.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent reads records through a view and answers without the whole base being exported.
An agent writes a record within governed permissions, with the change audited per tenant.
An agent follows a link between tables to answer a question spanning both.
Example prompt
Which records in this view are missing a linked owner, and when were they last updated?
Set up NocoDB in 4 steps
- 01Enable the NocoDB connector from your fastn dashboard.
- 02Have each customer authorise their own NocoDB account, so calls run under their credentials rather than a shared key.
- 03Decide which records, datasets and fields your product needs, map those fields, then enable the actions and triggers you want.
- 04Call it from your product and expose it to your agents through the same governed connection.
Why teams use the NocoDB integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a NocoDB integration without building it. Your customers connect their own NocoDB 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 NocoDB update is not your on-call problem.
- One integration serves your product and your agents. The same governed NocoDB 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
Baserow
GristOften used alongside
Tools the same teams tend to run next to NocoDB, across other categories.
Anthropic Claude
OpenAI
Azure OpenAI
Hugging FaceNocoDB integration FAQ
How do I add a NocoDB integration to my product?
Enable the NocoDB connector in your fastn dashboard, then let each customer authenticate their own NocoDB account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no NocoDB client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own NocoDB account?
Yes. Every connection is scoped to the individual customer, so each authorises their own NocoDB 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 NocoDB 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 reads records through a view and answers without the whole base being exported.
Who maintains the NocoDB integration?
fastn does. When NocoDB 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 NocoDB 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 NocoDB 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 NocoDB integration?
A common starting point: let a customer connect their own NocoDB base so your product works with tables they already maintain. 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 NocoDB integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding NocoDB does not change your per-connector cost. You can start free with 3 connected accounts.
Add NocoDB to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.