AI & Models · Integration
Instabase
Add Instabase to your product for your customers, and give your AI agents governed access to it.
Embed an Instabase integration so your customers can run their own document processing from inside your product instead of building an extraction pipeline into it. Access runs through each customer's own grant, so their existing permissions apply and your product cannot reach documents the connected account could not reach itself. fastn handles per-tenant authorisation, large file handling, and API upkeep, so onboarding another account is configuration rather than a release.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let customers submit a document from your product for processing under their own account.
Read extracted fields back and map them into your own schema per customer.
Read confidence or validation output so your product can route low-confidence results for review.
Trigger your product when processing finishes so the next step runs without polling.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent submits a document and reads the extracted fields before answering a question about it.
An agent flags a low-confidence extraction for human review within governed permissions.
An agent reacts to a completed extraction and files the result in the right place, with the action logged.
Example prompt
Process this invoice and tell me the extracted totals, flagging any field that came back low confidence.
Set up Instabase in 4 steps
- 01Open the Instabase connector from your fastn dashboard.
- 02Have each customer authenticate their own Instabase account.
- 03Map the document types and extracted 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 Instabase integration
What you get by embedding it with fastn instead of building it yourself.
- Ship an Instabase integration without building it. Your customers connect their own Instabase account inside your product and work their models, requests and outputs there, with no per-customer code on your side.
- Handle the part that actually costs time: per-customer keys, quotas and cost attribution matter more than schema here, because every call is billed. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so an Instabase update is not your on-call problem.
- One integration serves your product and your agents. The same governed Instabase connection powers in-product features and gives AI agents scoped, audited access, so you give your product and your agents a model call each customer pays for themselves without wiring it twice.
Used by these teams
Compare with
ABBYY Vantage
Azure AI Document Intelligence
Google Document AIOften used alongside
Tools the same teams tend to run next to Instabase, across other categories.
Snowflake
Airtable
PostgreSQL
AmplitudeInstabase integration FAQ
How do I add an Instabase integration to my product?
Enable the Instabase connector in your fastn dashboard, then let each customer authenticate their own Instabase account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Instabase client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Instabase account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Instabase account and only ever sees their own models, requests and outputs. 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 Instabase 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 submits a document and reads the extracted fields before answering a question about it.
Who maintains the Instabase integration?
fastn does. When Instabase 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.
Whose Instabase API key and quota does each call use?
Each customer authorises their own Instabase account, so usage, rate limits and cost land on the customer that caused them. You are not metering a shared key and re-billing it, and one heavy customer cannot exhaust another's quota.
Are inputs and outputs auditable?
Yes. Every call is logged per tenant with the call, the input and the result, so an output can be traced back to what produced it. That matters more here than in most integrations, because a generated answer or an extracted field cannot be reconstructed from the request alone.
What can I build with the Instabase integration?
A common starting point: submit a document from your product for processing under their own account. 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 Instabase integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Instabase does not change your per-connector cost. You can start free with 3 connected accounts.
Add Instabase to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.