Data & Storage · Integration
Jotform
Add Jotform to your product for your customers, and give your AI agents governed access to it.
Jotform submissions come back as an answers object keyed by field id, with the question text carried alongside each answer, which makes a submission readable without a second call but still leaves the field ids as the thing your product has to map. Files are the part worth planning for: an upload arrives as a URL on the submission rather than inline, and that URL needs the account's own credentials to fetch, so a naive copy into your product stores an error page instead of a PDF. Beyond reading there is a form and question list, programmatic submission creation, and webhooks so your product is told about a submission rather than polling for one. Each customer supplies their own API key with the permissions they chose when they created it, so what your product can reach is their decision rather than yours.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let a customer connect their own Jotform account with a key they scope themselves, and list the forms that key can reach.
Read submissions with answers keyed by field id, and map those ids once per form rather than parsing visible labels.
Fetch an uploaded file using the customer's own credentials, so an attachment arrives as the document instead of a login page.
Register a webhook per form so a submission reaches your product as it lands, rather than on a poll every few minutes.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent reads recent submissions to a form and reports the pattern in what people answered.
An agent creates a submission on a customer's behalf within scoped permissions, and the form it wrote to is logged.
An agent retrieves the file attached to a submission and summarises it without anyone downloading it.
Example prompt
Pull this week's submissions to the intake form and list the ones with an attachment nobody has reviewed.
Set up Jotform in 4 steps
- 01Enable the Jotform connector in your fastn dashboard.
- 02Have each customer create their own API key with the permissions they are willing to grant, so calls run under their account.
- 03Map each form's field ids to the fields your product uses, then register the webhooks you want to react to.
- 04Call it from your product and expose the same connection to your agents through the MCP gateway.
Why teams use the Jotform integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Jotform integration without building it. Your customers connect their own Jotform 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 Jotform update is not your on-call problem.
- One integration serves your product and your agents. The same governed Jotform 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
Google Forms
Cognito FormsOften used alongside
Tools the same teams tend to run next to Jotform, across other categories.
Anthropic Claude
OpenAI
Azure OpenAI
Hugging FaceJotform integration FAQ
How do I add a Jotform integration to my product?
Enable the Jotform connector in your fastn dashboard, then let each customer authenticate their own Jotform account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Jotform client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Jotform account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Jotform 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 Jotform 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 submissions to a form and reports the pattern in what people answered.
Who maintains the Jotform integration?
fastn does. When Jotform 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 Jotform 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 Jotform 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 Jotform integration?
A common starting point: let a customer connect their own Jotform account with a key they scope themselves, and list the forms that key can reach. 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 Jotform integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Jotform does not change your per-connector cost. You can start free with 3 connected accounts.
Add Jotform to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.