Content & Documents · Integration
Conga Contracts
Add Conga Contracts to your product for your customers, and give your AI agents governed access to it.
Embed a Conga Contracts integration so your customers can work their contracts, clauses, and approval state from inside your product, with governed agent access to the same records. Each deployment defines its own contract types and fields, so mapping is configuration per customer.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let customers read contracts and their key dates into your product.
Create or update contract records from an event in your product.
Read approval state so your product can gate the next step on sign-off.
Trigger your product when a contract is approved, executed, or nears renewal.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent reads a contract's terms and key dates before answering.
An agent creates a contract record within governed permissions.
An agent reacts to an upcoming renewal and notifies the owner.
Example prompt
List contracts renewing in the next 60 days with no owner assigned.
Set up Conga Contracts in 4 steps
- 01Open the Conga Contracts connector from your fastn dashboard.
- 02Have each customer authenticate their Conga account.
- 03Map the contract types, clauses, and approval 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 Contracts integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Conga Contracts integration without building it. Your customers connect their own Conga Contracts 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 Contracts update is not your on-call problem.
- One integration serves your product and your agents. The same governed Conga Contracts 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 Composer
Agiloft
Adobe Acrobat SignOften used alongside
Tools the same teams tend to run next to Conga Contracts, across other categories.
Shopify
Stripe
Jira
AsanaConga Contracts integration FAQ
How do I add a Conga Contracts integration to my product?
Enable the Conga Contracts connector in your fastn dashboard, then let each customer authenticate their own Conga Contracts account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Conga Contracts 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 Contracts account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Conga Contracts 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 Contracts 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 a contract's terms and key dates before answering.
Who maintains the Conga Contracts integration?
fastn does. When Conga Contracts 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 Contracts integration run under?
Each customer's own Conga Contracts grant. Where Conga Contracts 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 Contracts automatically?
Where Conga Contracts 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 Contracts integration?
A common starting point: read contracts and their key dates 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 Conga Contracts integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Conga Contracts does not change your per-connector cost. You can start free with 3 connected accounts.
Add Conga Contracts to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.