Data & Storage · Integration
Paperform
Add Paperform to your product for your customers, and give your AI agents governed access to it.
Paperform is a form builder, so it maps best to records and fields rather than to any form-specific category. Its API at api.paperform.co/v1 uses a bearer API key and is organised as forms, then the submissions and questions belonging to each form, addressed by the form's slug rather than a numeric id, so renaming a form's URL changes the API path. Submission answers are keyed by the internal question key, a short generated string, not by the visible question title, which means readable field mapping has to be built by first fetching the questions endpoint. Submissions include calculation and product fields, so a form used for payment carries totals and coupon effects alongside plain answers. Partial submissions exist separately from completed ones, and file uploads come back as URLs to Paperform-hosted files rather than as inline content. fastn holds each customer's Paperform key separately and keeps the mapping and credentials maintained as forms change.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let a customer connect their own Paperform account so their form submissions flow into your product
Map question keys to readable field names once and reuse the mapping across every submission
Create a record in your app for each new submission, including uploaded file links
Pull calculation and product field values so payment totals reconcile with your own records
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
Let an agent read submissions and summarise responses without being able to alter form definitions
Have an agent flag incomplete or suspicious submissions for review, audited per tenant
Scope an agent to a single form slug so other forms in the account stay out of scope
Example prompt
Summarise the responses to my Paperform customer survey from the past two weeks.
Set up Paperform in 4 steps
- 01Enable the Paperform connector from your fastn dashboard.
- 02Have each customer authorise their own Paperform 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 Paperform integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Paperform integration without building it. Your customers connect their own Paperform 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 Paperform update is not your on-call problem.
- One integration serves your product and your agents. The same governed Paperform 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 Paperform, across other categories.
Anthropic Claude
OpenAI
Azure OpenAI
Hugging FacePaperform integration FAQ
How do I add a Paperform integration to my product?
Enable the Paperform connector in your fastn dashboard, then let each customer authenticate their own Paperform account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Paperform client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Paperform account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Paperform 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 Paperform integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. Let an agent read submissions and summarise responses without being able to alter form definitions
Who maintains the Paperform integration?
fastn does. When Paperform 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 Paperform 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 Paperform 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 Paperform integration?
A common starting point: let a customer connect their own Paperform account so their form submissions flow into your product. 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 Paperform integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Paperform does not change your per-connector cost. You can start free with 3 connected accounts.
Add Paperform to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.