Data & Storage · Integration
Basin
Add Basin to your product for your customers, and give your AI agents governed access to it.
Basin is a hosted form backend, so the data model is deliberately loose: a form has an endpoint that accepts any POST body, and each submission stores whatever field names the HTML actually sent. The API lives under usebasin.com/api/v1 with forms and their submissions as the main collections, and requests without a key are rejected with a clear body rather than a redirect, so key problems are easy to spot. Because fields are user-defined and can change whenever someone edits the markup, a submissions reader has to treat the payload as an open map instead of a fixed schema, and historical rows will not share keys with recent ones. Submissions also carry spam classification and file attachments, so a naive consumer that treats every row as a real lead will import junk. Note the API paths are strict about the trailing form of the URL: some paths answer with a 301 that curl will not follow by default. fastn stores each customer's key, handles the per-form scoping and keeps the connection working as forms are added or renamed.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let a customer connect their own Basin account so their website form submissions appear in your app as leads
Create and configure a form in Basin from your onboarding flow so the customer never leaves your product
Filter incoming submissions on the spam flag before they reach a customer's inbox or CRM
Attach uploaded files from a submission to the matching record in your own system
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
Ask an agent to summarise this week's submissions for one form and flag the ones classed as spam
Have an agent report which fields a form has actually received, so a mapping can be updated
Let an agent create a new form for a tenant, with the creation audited per tenant against that tenant's own key
Example prompt
How many genuine submissions did our contact form get this week, and what did people ask about?
Set up Basin in 4 steps
- 01Enable the Basin connector from your fastn dashboard.
- 02Have each customer authorise their own Basin 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 Basin integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Basin integration without building it. Your customers connect their own Basin 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 Basin update is not your on-call problem.
- One integration serves your product and your agents. The same governed Basin 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 Basin, across other categories.
Anthropic Claude
OpenAI
Azure OpenAI
Hugging FaceBasin integration FAQ
How do I add a Basin integration to my product?
Enable the Basin connector in your fastn dashboard, then let each customer authenticate their own Basin account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Basin client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Basin account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Basin 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 Basin integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. Ask an agent to summarise this week's submissions for one form and flag the ones classed as spam
Who maintains the Basin integration?
fastn does. When Basin 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 Basin 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 Basin 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 Basin integration?
A common starting point: let a customer connect their own Basin account so their website form submissions appear in your app as leads. 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 Basin integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Basin does not change your per-connector cost. You can start free with 3 connected accounts.
Add Basin to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.