Data & Storage · Integration
Cognito Forms
Add Cognito Forms to your product for your customers, and give your AI agents governed access to it.
Cognito Forms is unusual among form builders in that entries stay editable after the fact: your product can create an entry, read it, update it and delete it, which turns a form into a small workflow rather than a one-way submission. Entries carry the calculated fields and the entry status the form itself defines, so a value your product reads may have been computed on Cognito's side rather than typed by anybody, and recomputing it locally is how two systems start disagreeing. Uploaded files and generated documents are separate resources hanging off an entry, and a document is produced from a template, which is very often the artefact a customer actually wants out of the process. A form's public link can be opened or closed through the API, which is how a registration is stopped without anyone logging in. Keys are issued by an organisation owner or administrator, so each customer decides what your product may reach and every call is attributable to the key they issued.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let each customer connect their own Cognito Forms organisation with a key an owner issues, and reach only the forms it covers.
Create and update entries from your product, so a form becomes a step in a workflow rather than a one-way submission.
Read calculated fields and entry status as the form authored them, instead of recomputing values and drifting apart.
Fetch the document generated from an entry, since that is usually the artefact the customer is actually after.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent reads an entry and reports what is still missing before it is passed on.
An agent updates an entry within scoped permissions, with the form and entry id recorded.
An agent closes a form's public link once a registration limit has been reached.
Example prompt
Which entries on this form are incomplete, and has a document been generated for any of them?
Set up Cognito Forms in 4 steps
- 01Enable the Cognito Forms connector in your fastn dashboard.
- 02Have an owner or administrator on each organisation issue an API key, so calls run under credentials that customer controls.
- 03Map each form's fields, calculated values and entry statuses, and decide which generated documents your product fetches.
- 04Call it from your product and expose the same connection to your agents through the MCP gateway.
Why teams use the Cognito Forms integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Cognito Forms integration without building it. Your customers connect their own Cognito 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 Cognito Forms update is not your on-call problem.
- One integration serves your product and your agents. The same governed Cognito 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
Jotform
Wufoo
FormAssemblyOften used alongside
Tools the same teams tend to run next to Cognito Forms, across other categories.
Anthropic Claude
OpenAI
Azure OpenAI
Hugging FaceCognito Forms integration FAQ
How do I add a Cognito Forms integration to my product?
Enable the Cognito Forms connector in your fastn dashboard, then let each customer authenticate their own Cognito Forms account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Cognito 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 Cognito Forms account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Cognito 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 Cognito 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 reads an entry and reports what is still missing before it is passed on.
Who maintains the Cognito Forms integration?
fastn does. When Cognito 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 Cognito 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 Cognito 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 Cognito Forms integration?
A common starting point: let each customer connect their own Cognito Forms organisation with a key an owner issues, and reach only the forms it covers. 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 Cognito Forms integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Cognito Forms does not change your per-connector cost. You can start free with 3 connected accounts.
Add Cognito Forms to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.