Content & Documents · Integration
Conga Composer
Add Conga Composer to your product for your customers, and give your AI agents governed access to it.
Embed a Conga Composer integration so your customers can generate documents from their own templates and record data inside your product, with governed agent access to the same output. Each customer's templates and merge fields differ, so mapping is configuration rather than code.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let customers generate a document from their own template and record data.
Read available templates so your product only offers what exists.
File generated output against the right record automatically.
Trigger your product when generation completes or fails.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent generates a document from the correct template within governed permissions.
An agent reads which templates exist before choosing one.
An agent reacts to a completed document and routes it for signature.
Example prompt
Generate the renewal summary for these accounts and file each against its opportunity.
Set up Conga Composer in 4 steps
- 01Open the Conga Composer connector from your fastn dashboard.
- 02Have each customer authenticate their Conga 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 Conga Composer integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Conga Composer integration without building it. Your customers connect their own Conga Composer 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 Conga Composer update is not your on-call problem.
- One integration serves your product and your agents. The same governed Conga Composer 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
Conga Contracts
CarboneWorks well with
SalesforceOften used alongside
Tools the same teams tend to run next to Conga Composer, across other categories.
Shopify
Stripe
Jira
AsanaConga Composer integration FAQ
How do I add a Conga Composer integration to my product?
Enable the Conga Composer connector in your fastn dashboard, then let each customer authenticate their own Conga Composer account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Conga Composer client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Conga Composer account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Conga Composer 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 Conga Composer 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 generates a document from the correct template within governed permissions.
Who maintains the Conga Composer integration?
fastn does. When Conga Composer 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 Conga Composer integration run under?
Each customer's own Conga Composer grant. Where Conga Composer 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 Conga Composer automatically?
Where Conga Composer 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 Conga Composer integration?
A common starting point: generate a document from their own template and record data. 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 Conga Composer integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Conga Composer does not change your per-connector cost. You can start free with 3 connected accounts.
Add Conga Composer to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.