Content & Documents · Integration
RightSignature
Add RightSignature to your product for your customers, and give your AI agents governed access to it.
Embed a RightSignature integration so your customers can send documents for electronic signature and track completion from inside your product, with governed agent access to the same records. fastn handles per-customer authentication and API upkeep, so e-signature is configuration rather than a per-customer build.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let customers send a document for signature directly from your product.
Read signature status so your product can gate the next step on completion.
Pull the signed document and file it against the right record.
Trigger your product when a document is signed, declined, or expires.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent checks whether a document has been signed before proceeding.
An agent sends a document for signature within governed permissions.
An agent reacts to a completed signature and advances the workflow.
Example prompt
List documents sent more than a week ago that are still awaiting signature, with the recipient for each.
Set up RightSignature in 4 steps
- 01Open the RightSignature connector from your fastn dashboard.
- 02Have each customer authenticate their RightSignature account.
- 03Map the document templates 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 RightSignature integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a RightSignature integration without building it. Your customers connect their own RightSignature 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 RightSignature update is not your on-call problem.
- One integration serves your product and your agents. The same governed RightSignature 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
Adobe Acrobat Sign
ShareFile
BoxOften used alongside
Tools the same teams tend to run next to RightSignature, across other categories.
Shopify
Stripe
Jira
AsanaRightSignature integration FAQ
How do I add a RightSignature integration to my product?
Enable the RightSignature connector in your fastn dashboard, then let each customer authenticate their own RightSignature account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no RightSignature client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own RightSignature account?
Yes. Every connection is scoped to the individual customer, so each authorises their own RightSignature 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 RightSignature 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 checks whether a document has been signed before proceeding.
Who maintains the RightSignature integration?
fastn does. When RightSignature 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 RightSignature integration run under?
Each customer's own RightSignature grant. Where RightSignature 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 RightSignature automatically?
Where RightSignature 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 RightSignature integration?
A common starting point: send a document for signature directly from 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 RightSignature integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding RightSignature does not change your per-connector cost. You can start free with 3 connected accounts.
Add RightSignature to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.