Content & Documents · Integration
Ironclad
Add Ironclad to your product for your customers, and give your AI agents governed access to it.
Embed an Ironclad integration so your customers can start and track their own contract work from inside your product instead of switching into their contract system. Access runs through each customer's own grant, so their existing document permissions apply and your product cannot read an agreement the connected account could not read itself. fastn handles per-tenant authorisation, versioning concerns, and API upkeep.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let customers launch a contract workflow from your product using data it already holds.
Read contract records and their metadata into your product, mapped to each customer's fields.
Read a signed agreement's key dates so renewals surface where users work.
Trigger your product when a workflow advances, is approved, or a contract is signed.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent reads a contract record and reports the terms it contains before a question is answered.
An agent launches a workflow within governed permissions, with the action logged.
An agent reacts to a signed contract and runs the next filing or provisioning step.
Example prompt
List the contract workflows waiting on approval for more than five days and who they are waiting on.
Set up Ironclad in 4 steps
- 01Open the Ironclad connector from your fastn dashboard.
- 02Have each customer authenticate their own Ironclad account.
- 03Map the workflows, record types, and 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 Ironclad integration
What you get by embedding it with fastn instead of building it yourself.
- Ship an Ironclad integration without building it. Your customers connect their own Ironclad 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 an Ironclad update is not your on-call problem.
- One integration serves your product and your agents. The same governed Ironclad 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
AgiloftOften used alongside
Tools the same teams tend to run next to Ironclad, across other categories.
Shopify
Stripe
Jira
AsanaIronclad integration FAQ
How do I add an Ironclad integration to my product?
Enable the Ironclad connector in your fastn dashboard, then let each customer authenticate their own Ironclad account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Ironclad client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Ironclad account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Ironclad 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 Ironclad 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 record and reports the terms it contains before a question is answered.
Who maintains the Ironclad integration?
fastn does. When Ironclad 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 Ironclad integration run under?
Each customer's own Ironclad grant. Where Ironclad 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 Ironclad automatically?
Where Ironclad 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 Ironclad integration?
A common starting point: launch a contract workflow from your product using data it already holds. 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 Ironclad integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Ironclad does not change your per-connector cost. You can start free with 3 connected accounts.
Add Ironclad to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.