Connect Docusign to Hermes
Give Hermes governed access to Docusign’s 30 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Docusign to Hermes in four steps
Admins approve the server once. Everyone in Hermes then gets it through the same governed connection.
- 1
Approve Docusign in Runlayer
Add Docusign from the catalog and choose who can use it and which of its tools are allowed.
- 2
Connect Hermes to Runlayer
Users add the Runlayer Plugin to Hermes by following Runlayer’s setup guide. Hermes reaches Docusign’s 30 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.
Hermes setup guide - 3
Sign in to Docusign
Each user signs in to Docusign with OAuth. Runlayer keeps the tokens out of the client’s configuration.
- 4
Use Docusign from Hermes
Docusign’s approved tools appear in Hermes. Every call is checked against policy and recorded.
Tools
30 Docusign tools in Hermes
Runlayer policy decides which of these Hermes users can call. 14 read data only and 6 can change or delete data.
Cancel workflow instance
Cancel a running workflow instance.
Create envelope
Creates a new Docusign envelope from an EXISTING Docusign template or from documents provided via a remote URL.
Create envelope from template
PRIMARY TOOL for sending Docusign agreements or envelopes for signature using templates.
Get account
Retrieve account information for a specific eSign account.
Get agreement details
Retrieve detailed information about a specific agreement
Get agreement filter skill
REQUIRED BEFORE A FILTERED getAllAgreements CALL: Call this skill before constructing the filter.
Get all agreements
Retrieves agreements for a Docusign account.
Get clm workflow definitions
Retrieve workflow definitions for a CLM account.
Control
What Runlayer can see and stop in Hermes
Some controls apply to every client at the gateway. Others depend on what Hermes exposes to Runlayer.
Gateway policy (available)
Every Docusign call from Hermes passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, Hermes as the client, the tool, and the policy and scanner decisions.
Client hooks (available)
Capture supported prompts, reasoning, local and MCP tool calls, responses, and scanner decisions in real time.
Stop a call before it runs (available)
Runlayer can deny a tool call before Hermes runs it.
Block output after it runs (available)
Runlayer can block a tool’s output in Hermes and show a message in its place.
Redact output in place (not available)
Hermes cannot take masked output, so Runlayer can block a tool’s output but not mask it. The gateway still applies policy to the call.
In Hermes
- Hermes can replace blocked tool output with a message, but its after-call event is for monitoring only.
Frequently asked questions
Connect more
