Data & Storage · Integration
Formsite
Add Formsite to your product for your customers, and give your AI agents governed access to it.
Formsite's REST API v2 is not served from a single api host: the base URL includes the server your account sits on and your user directory, in the shape https://fsN.formsite.com/api/v2/{user_directory}/forms, so a connection needs both values captured at setup or every call returns a 404 that reads like a dead API. Authentication is a bearer token created per user in the account, and that token inherits the user's form permissions, so a limited sub-user simply sees fewer forms rather than an authorisation error. Result rows return answers keyed by control id, so /forms/{id}/items has to be read first to recover the question labels and the option lists for dropdowns and checkboxes. File upload questions come back as URLs into the account's file store rather than inline data, and results paginate with a results_per_page limit plus after_id style cursors, which matters because busy forms accumulate large historic result sets. fastn stores each customer's server host, directory and token, and keeps the per-form permission scope tied to that tenant.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let a customer connect their own Formsite account so submissions to their forms arrive in your product as structured records.
Map control ids to readable question labels once, then present a customer's results with proper column headings.
Pull uploaded files attached to a submission and store them against the matching case or order in your app.
Poll for new results since the last id so a customer's back office sees submissions without manual export.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
Ask an agent to summarise the last week of submissions for one form, audited per tenant.
Have an agent find results missing a required follow-up field and list them for a human to chase.
Let an agent report submission volume by form so a customer can retire unused forms.
Example prompt
How many contact requests came through the support form yesterday, and which ones have no phone number?
Set up Formsite in 4 steps
- 01Enable the Formsite connector from your fastn dashboard.
- 02Have each customer authorise their own Formsite 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 Formsite integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Formsite integration without building it. Your customers connect their own Formsite 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 Formsite update is not your on-call problem.
- One integration serves your product and your agents. The same governed Formsite 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 Formsite, across other categories.
Anthropic Claude
OpenAI
Azure OpenAI
Hugging FaceFormsite integration FAQ
How do I add a Formsite integration to my product?
Enable the Formsite connector in your fastn dashboard, then let each customer authenticate their own Formsite account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Formsite client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Formsite account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Formsite 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 Formsite 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 the last week of submissions for one form, audited per tenant.
Who maintains the Formsite integration?
fastn does. When Formsite 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 Formsite 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 Formsite 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 Formsite integration?
A common starting point: let a customer connect their own Formsite account so submissions to their forms arrive in your product as structured records. 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 Formsite integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Formsite does not change your per-connector cost. You can start free with 3 connected accounts.
Add Formsite to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.