Data & Storage · Integration
FormAssembly
Add FormAssembly to your product for your customers, and give your AI agents governed access to it.
Embed a FormAssembly integration so your customers can pull their own forms and collected responses into your product without exporting spreadsheets. Every form has a different field structure, so field mapping is configuration per customer rather than code, and a form that changes on their side is a mapping update rather than a release on yours. fastn handles per-customer authorisation, pagination, and API upkeep.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let customers read responses from their own forms into your product, mapped to their fields.
Read a form's field structure at runtime so your product adapts to each customer's form design.
Pull historical responses on a backfill so a new customer sees their existing data on day one.
Trigger your product when a new response is submitted so downstream work starts immediately.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent reads recent responses before summarising what respondents said.
An agent looks up a single response to ground an answer in the customer's own collected data.
An agent reacts to a new submission and runs the next step of a workflow within governed permissions.
Example prompt
Pull this week's responses from the intake form and list the ones missing a contact email.
Set up FormAssembly in 4 steps
- 01Open the FormAssembly connector from your fastn dashboard.
- 02Have each customer authenticate their own FormAssembly account.
- 03Map the forms and fields your product reads, then enable actions and triggers.
- 04Call them from your product, or expose them to an agent through the MCP server.
Why teams use the FormAssembly integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a FormAssembly integration without building it. Your customers connect their own FormAssembly 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 FormAssembly update is not your on-call problem.
- One integration serves your product and your agents. The same governed FormAssembly 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
Google SheetsWorks well with
Salesforce
Formstack DocumentsOften used alongside
Tools the same teams tend to run next to FormAssembly, across other categories.
Anthropic Claude
OpenAI
Azure OpenAI
Hugging FaceFormAssembly integration FAQ
How do I add a FormAssembly integration to my product?
Enable the FormAssembly connector in your fastn dashboard, then let each customer authenticate their own FormAssembly account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no FormAssembly client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own FormAssembly account?
Yes. Every connection is scoped to the individual customer, so each authorises their own FormAssembly 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 FormAssembly 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 recent responses before summarising what respondents said.
Who maintains the FormAssembly integration?
fastn does. When FormAssembly 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 FormAssembly 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 FormAssembly 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 FormAssembly integration?
A common starting point: read responses from their own forms into your product, mapped to their fields. 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 FormAssembly integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding FormAssembly does not change your per-connector cost. You can start free with 3 connected accounts.
Add FormAssembly to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.