Data & Storage · Integration
Fillout Forms
Add Fillout Forms to your product for your customers, and give your AI agents governed access to it.
Fillout builds long, conditional forms, the kind where the questions somebody sees depend on the answers they already gave, and it can take payments and bookings inside the same flow. That conditional design is the thing an integration has to respect: two people completing the same form can return different sets of answers, and answers come back keyed to question identifiers rather than to labels, so reading the form definition first is what stops your mapping from breaking the moment a customer edits a question. Submissions can be listed with filters or delivered as they happen, and a form's URL parameters can be prefilled, which is how a link from your product arrives with the account already filled in. fastn keeps each customer's credentials per tenant, and pagination on a large submission history is handled for you.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let each customer connect their own Fillout account so responses arrive in your product instead of waiting in an export.
Read the form definition at runtime so a conditional question added by a customer maps itself instead of breaking your import.
Receive a submission as it is completed and start the work it implies, from an approval to an onboarding step.
Prefill a form from your product so the person completing it is not retyping what you already know about them.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent summarises what a batch of submissions said and highlights the responses that need a person.
An agent finds submissions matching a condition and reports how they differ from the rest.
An agent checks a submission for missing answers and drafts the follow-up question, with the read logged.
Example prompt
Summarise this week's Fillout submissions for the onboarding form and flag anyone who selected enterprise.
Set up Fillout Forms in 4 steps
- 01Enable the Fillout Forms connector in your fastn dashboard.
- 02Have each customer authorise their own Fillout account so their forms and submissions stay theirs.
- 03Read each form's questions and map them to the fields your product stores, then enable submission events.
- 04Call it from your product and expose the same governed connection to your agents.
Why teams use the Fillout Forms integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Fillout Forms integration without building it. Your customers connect their own Fillout Forms 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 Fillout Forms update is not your on-call problem.
- One integration serves your product and your agents. The same governed Fillout Forms 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
Typeform
Airtable
Zoho FormsOften used alongside
Tools the same teams tend to run next to Fillout Forms, across other categories.
Anthropic Claude
OpenAI
Azure OpenAI
Hugging FaceFillout Forms integration FAQ
How do I add a Fillout Forms integration to my product?
Enable the Fillout Forms connector in your fastn dashboard, then let each customer authenticate their own Fillout Forms account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Fillout Forms client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Fillout Forms account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Fillout Forms 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 Fillout Forms 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 summarises what a batch of submissions said and highlights the responses that need a person.
Who maintains the Fillout Forms integration?
fastn does. When Fillout Forms 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 Fillout Forms 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 Fillout Forms 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 Fillout Forms integration?
A common starting point: let each customer connect their own Fillout account so responses arrive in your product instead of waiting in an export. 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 Fillout Forms integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Fillout Forms does not change your per-connector cost. You can start free with 3 connected accounts.
Add Fillout Forms to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.