Integration
Connect DocuSign to Signatureapi
When something happens in DocuSign, your agent does the next thing in Signatureapi. Describe it and it is built, tested on every scenario and kept running.
What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.
Build solutions, not workarounds.
What do you want DocuSign and Signatureapi to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiAny client that takes a remote MCP server. Nothing to install. Create your free account, then sign in once in your browser.
Set it up in your client
Claude Code
Run this in the directory you want to work in.
claude mcp add --transport http -s project apiant-ai https://mcp.apiant.aiStart Claude Code there, approve the server, and sign in in the browser page it opens.
Claude Code guide (opens in a new tab)Claude, web and desktop
Open Customize, then Connectors, then Add custom connector, and paste the address. On Team and Enterprise an owner adds it first.
Setup guide (opens in a new tab)Cursor
Add the address to your MCP configuration as a server URL. Cursor signs you in in your browser.
Setup guide (opens in a new tab)Zed
Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.
Setup guide (opens in a new tab)Codex and the ChatGPT desktop app
Open Settings, then MCP servers, then Add server, and choose Streamable HTTP. From the terminal, Codex takes the address with its own add command and then signs you in.
Setup guide (opens in a new tab)Any other MCP client
Paste the address where the client asks for a remote MCP server URL, and name the server apiant-ai where it lets you. APIANT's skills reach the client over the same connection.
Setup guide (opens in a new tab)Example flows
What DocuSign can start in Signatureapi
When New envelope sent in DocuSign
then Add envelope in Signatureapi
Starting points drawn from the triggers and actions in the catalog today. Describe the flow you need, at any depth, and your agent builds it and tests every scenario before it ships.
Everything your agent can do with DocuSign and Signatureapi
Triggers and actions 1 trigger · 36 actions
- New envelope sent
Triggered when an envelope is sent from the DocuSign account.
- Add Envelope Recipients
Add one or more recipients to an existing envelope.
- Create Envelope
Create and optionally send an envelope. Pass documents, recipients, and status (created=draft, sent=send now).
- Create Envelope From Template
Create and send an envelope from an existing template using template roles.
- Create Recipient View
Generate an embedded signing URL (recipient view) for a recipient of an envelope.
- Delete Envelope Recipient
Remove a recipient from an envelope by recipient ID.
- Get Envelope
Retrieve a single envelope's status and details by envelope ID.
- Get envelope audit events
Retrieve the audit event log for an envelope.
- Get envelope document
Downloads one document from a DocuSign envelope (or all documents combined, as an archive, a portfolio, or just the certificate of completion) and returns the file content base64-encoded.
- Get Envelope Documents
List the documents contained in an envelope.
- Get Envelope Recipients
List the recipients of an envelope and their signing status.
- Get Envelope Status Changes
List envelopes whose status changed since a given date (status polling).
- Get Template
Retrieve a single template's definition by template ID.
- Get user
Retrieves the information for a DocuSign user.
- List Account Users
List the users in the DocuSign account.
- List Envelopes
List envelopes in the account, optionally filtered by status and modified date.
- List Folders
List the folders in the account.
- List Templates
List the envelope templates in the account.
- Send Envelope
Send a draft envelope by changing its status to sent.
- Update envelope
Changes an existing DocuSign envelope: send a draft, void an in-process envelope, change a draft's email subject and message, resume a paused workflow, or queue a completed envelope's documents for purging.
- Update Envelope Recipients
Update existing recipients on an envelope (e.g. correct email or name).
- Void Envelope
Void a sent envelope, providing a void reason.
- Add ceremony
Creates a new signing ceremony for a recipient. Any previous active ceremony for that recipient is revoked. Returns the ceremony, including its URL when the recipient is authenticated by email code or by your own application.
- Add deliverable
Creates an additional deliverable (signed PDF package) from a completed envelope. The envelope must be completed.
- Add envelope
Creates an envelope with documents and recipients and starts the signing process.
- Add upload
Uploads a PDF, DOCX or PNG file to SignatureAPI and returns a URL you can use as a document source when creating an envelope. Uploads expire after 24 hours.
- Cancel envelope
Cancel an in-progress envelope so remaining recipients can no longer sign.
- Delete envelope
Delete an envelope.
- Get deliverable
Retrieves a deliverable by its ID, including its status and, once generated, a download link for the signed PDF.
- Get envelope
Retrieve a single envelope by id.
- Get recipient
Retrieves a recipient's details, including status, ceremony information and completion timestamp.
- Get upload
Fetches an uploaded file's record by ID: its format, size, hash and expiry. An error occurs if the upload is not found.
- List deliverables
Returns the deliverables (signed PDFs with audit log) of an envelope, earliest first.
- List envelopes
Lists envelopes in the account, most recent first, optionally filtered by status or topic.
- Resend request
Resends the signing request to a recipient who has not yet completed their ceremony, e.g. as a reminder or after a lost or soft-bounced email.
- Update envelope
Update mutable fields (e.g. title, metadata) of an existing envelope.
- Update recipient
Replaces a recipient who has not yet completed with a new person. The original recipient is marked replaced and a new recipient is created with the same type, key, routing position and places.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.
Each app on its own
Reviews
What our customers say
More from DocuSign
DocuSign to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
DocuSign to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
DocuSign to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
DocuSign to Google SheetsGoogle Sheets
DocuSign to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
DocuSign to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into Signatureapi
Questions
DocuSign and Signatureapi, answered
What can start an automation from DocuSign?
Any of DocuSign's 1 trigger in the catalog, including New envelope sent. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Signatureapi when something happens in DocuSign?
Any of Signatureapi's 15 actions, including Update envelope, Update recipient, Add ceremony and Add deliverable. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Signatureapi to DocuSign?
Signatureapi has no triggers in the catalog today, so automations start in DocuSign. If you need the other direction, ask: your agent reads Signatureapi's API documentation and adds it.
Do I have to build a connector for DocuSign or Signatureapi?
No. Both are in the catalog with their triggers and actions. You describe the automation; your agent builds it, tests every scenario and keeps it running.
What happens when something fails?
Your agent works that out for you. It plans the failure paths along with the happy path, then tests every scenario before it ships.
Is there a free plan?
Yes. Every plan includes the agent, including free, and building from your own AI client spends no assistant credits.