Integration · Legal
AI agents for BoldSign
Send documents for e-signature with BoldSign, from a template or from PDF links, list and read documents and their signers' status, list templates, remind signers and revoke documents.
- Actions
- 8
- Read
- 4
- Write
- 4
Actions
What your agents can do in BoldSign
8 actions. Each one is a tool your agents can call and a step your workflows can run.
Read 4
Look things up. Nothing changes.
List documents
Lists the documents sent or received, newest first, optionally with one status (WaitingForOthers, Completed, Declined, Revoked, Expired, Draft ...)
Get a document
Reads one document's details: title, status, senderDetail, signerDetails (each signer's name, email, status, lastActivityDate), ccDetails, documentHistory, labels, created and expiry dates.
List templates
Lists the templates the account can use, optionally matching a search.
Get a template
Reads a template: title, description, documentTitle, documentMessage and roles (each role's index, name and default signer), so you know which roleIndex to fill when sending from it.
Write 4
Create, change or send.
Send from a template
Sends a document for signature from a template, filling each role.
Send a document for signature
Sends one or more files (PDF, Word, Excel, PowerPoint, PNG or JPG at public links) for signature.
Remind signers
Emails a reminder to a document's signers who have not signed yet, or only to the emails given, with an optional message.
Revoke a documentDeletes data
Withdraws a document that is out for signature, so nobody can sign it any more, with a message telling the signers why.
A person can approve first
Any write action can be set to wait for a person's approval before it runs, so an agent asks before it changes anything. Actions that delete data ask first by default.
Connection
How it connects
Connect it once in the console, then give it to the agents and workflows that need it.
Paste an API key from your BoldSign account.
What you enter
- API key
Settings
- Region
Kept safe
- Credentials are stored encrypted with your organization's own keys.
- They are opened only by the process that makes the call, at the moment it runs, and never go into a prompt or the browser.
- Calls go only to the tool's own servers.
Ideas
Ideas to start with
Starting points made only from the actions above. Mix them with any other tool your agents can use.
- 01
Ask about your BoldSign data
Ask a question in plain words. The agent can list documents, get a document or list templates in BoldSign, then answers with what it found.
- 02
Let an agent update BoldSign
Have the agent send from a template or send a document for signature in BoldSign as part of a larger task. Turn on approval and a person signs off on each change first.
- 03
Share what it finds in Slack
Give one agent BoldSign and Slack: it can list documents in BoldSign and post a summary to a Slack channel in the same run.
FAQ
BoldSign and MyDeepAgents
Can MyDeepAgents connect to BoldSign?
Yes. The BoldSign connector has 8 actions: 4 read and 4 make changes. Your agents can call them as tools, and your workflows can run them as steps.
How do I connect BoldSign?
Paste an API key from your BoldSign account. You'll need: API key. The connection also asks for: Region. Credentials are stored encrypted with your organization's own keys and are opened only at the moment of a call.
Can an agent change data in BoldSign without asking?
Only if you let it. Each of the 4 actions that change data can be set to wait for a person's approval before it runs, and the one that deletes data asks first by default.
Can I use BoldSign in workflows as well as agents?
Yes. Every BoldSign action also works as a step in a workflow, and the same connection serves your agents and your workflows.
Early access
Put BoldSign to work
Connect it in a few minutes, give an agent the actions it needs, and decide which changes wait for a person.