Content & Documents · Integration
Formstack Documents
Add Formstack Documents to your product for your customers, and give your AI agents governed access to it.
Embed a Formstack Documents integration so your customers can turn data in your product into finished documents using their own templates, without you building a document engine. Each customer connects their own account, so their templates, merge fields, and delivery settings apply and your product cannot touch templates the connected account could not touch itself. fastn handles per-customer credentials and API upkeep.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let customers generate a document from one of their own templates using data held in your product.
Read the merge fields a template expects so your product can map its data to them per customer.
List a customer's templates so users pick the right one inside your product instead of switching tools.
Trigger your product when a document has been generated so the next step can run.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent picks the right template and generates a document within governed permissions, with the action logged.
An agent reads a template's merge fields before deciding what data it still needs.
An agent reacts to a completed document and starts the next delivery or filing step.
Example prompt
Generate the customer agreement from the standard template using this account's details, then tell me where the file was delivered.
Set up Formstack Documents in 4 steps
- 01Open the Formstack Documents connector from your fastn dashboard.
- 02Have each customer authenticate their own Formstack Documents account.
- 03Map the templates and merge fields your product uses, then enable actions and triggers.
- 04Call them from your product, or expose them to an agent through the MCP server.
Why teams use the Formstack Documents integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Formstack Documents integration without building it. Your customers connect their own Formstack Documents account inside your product and work their files, documents and versions there, with no per-customer code on your side.
- Handle the part that actually costs time: permissions and versioning are easy to get subtly wrong, and mistakes expose content. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a Formstack Documents update is not your on-call problem.
- One integration serves your product and your agents. The same governed Formstack Documents connection powers in-product features and gives AI agents scoped, audited access, so you let your product work with your customers' documents in place without wiring it twice.
Used by these teams
Compare with
Docusign
Google DocsWorks well with
FormAssemblyOften used alongside
Tools the same teams tend to run next to Formstack Documents, across other categories.
Shopify
Stripe
Jira
AsanaFormstack Documents integration FAQ
How do I add a Formstack Documents integration to my product?
Enable the Formstack Documents connector in your fastn dashboard, then let each customer authenticate their own Formstack Documents account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Formstack Documents client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Formstack Documents account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Formstack Documents account and only ever sees their own files, documents and versions. 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 Formstack Documents 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 picks the right template and generates a document within governed permissions, with the action logged.
Who maintains the Formstack Documents integration?
fastn does. When Formstack Documents 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.
Whose permissions does the Formstack Documents integration run under?
Each customer's own Formstack Documents grant. Where Formstack Documents holds a library, their existing folder and item permissions apply and your product cannot reach content the connected account could not reach itself. Where it processes content you supply rather than storing it, the call runs under that customer's own credentials and is logged per tenant.
Can my product create or update content in Formstack Documents automatically?
Where Formstack Documents supports writes, documents, entries and assets can be created, updated and filed from your product or by an agent within scoped permissions, with each action logged. Where it is a read surface, the same connection serves reads only.
What can I build with the Formstack Documents integration?
A common starting point: generate a document from one of their own templates using data held in 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 Formstack Documents integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Formstack Documents does not change your per-connector cost. You can start free with 3 connected accounts.
Add Formstack Documents to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.