Data & Storage · Integration
Ninox
Add Ninox to your product for your customers, and give your AI agents governed access to it.
Ninox is a low-code database, and its API at api.ninox.com/v1 nests everything under teams, then databases, then tables, then records, so every call needs three identifiers before you reach any data. Authentication is a bearer API key generated in the account, and customers on private or on-premise Ninox Cloud instances use their own host rather than api.ninox.com, which is easy to miss when onboarding. Field identifiers in record payloads are the field names as defined in the schema, so renaming a field in the Ninox editor breaks integrations that wrote against the old name. Relationship fields return referenced record ids rather than nested objects, so following a link means a second call to the related table. Ninox also runs server-side scripts and triggers on record changes, meaning a write through the API can cause further changes you did not send. fastn keeps each customer's key and host separate and handles the per-tenant auth and upkeep as schemas change.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let a customer connect their own Ninox team so their databases become readable from your product
Create and update records in a customer's Ninox table when something happens in your app
Read a Ninox table as a reference source for dropdowns and lookups in your own interface
Detect schema changes so your mapping breaks loudly rather than silently writing to the wrong field
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
Let an agent query records across a customer's tables while writes stay behind human approval
Have an agent explain a table's schema and relationships before proposing a change, audited per tenant
Scope an agent to named databases so other databases in the same team stay out of reach
Example prompt
How many records in our Ninox inventory table are below the reorder level?
Set up Ninox in 4 steps
- 01Enable the Ninox connector from your fastn dashboard.
- 02Have each customer authorise their own Ninox 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 Ninox integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Ninox integration without building it. Your customers connect their own Ninox 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 Ninox update is not your on-call problem.
- One integration serves your product and your agents. The same governed Ninox 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
Snowflake
Airtable
PostgreSQLOften used alongside
Tools the same teams tend to run next to Ninox, across other categories.
Anthropic Claude
OpenAI
Azure OpenAI
Hugging FaceNinox integration FAQ
How do I add a Ninox integration to my product?
Enable the Ninox connector in your fastn dashboard, then let each customer authenticate their own Ninox account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Ninox client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Ninox account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Ninox 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 Ninox integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. Let an agent query records across a customer's tables while writes stay behind human approval
Who maintains the Ninox integration?
fastn does. When Ninox 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 Ninox 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 Ninox 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 Ninox integration?
A common starting point: let a customer connect their own Ninox team so their databases become readable from your product. 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 Ninox integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Ninox does not change your per-connector cost. You can start free with 3 connected accounts.
Add Ninox to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.