Skip to main content
Book a demo

Connect Docusign to Claude

Give Claude governed access to Docusign’s 30 tools through Runlayer, with identity, policy, scanning, and audit on every call.

Book a demo Claude setup guide

Set up

Add Docusign to Claude in four steps

Admins approve the server once. Everyone in Claude then gets it through the same governed connection.

  1. 1

    Approve Docusign in Runlayer

    Add Docusign from the catalog and choose who can use it and which of its tools are allowed.

  2. 2

    Connect Claude to Runlayer

    Admins install the Runlayer Plugin for everyone from Claude’s admin plugin settings, or users add it themselves. With direct tool listing turned on for your deployment, Docusign’s 30 tools show up in Claude’s own tool list.

    Claude setup guide
  3. 3

    Sign in to Docusign

    Each user signs in to Docusign with OAuth. Runlayer keeps the tokens out of the client’s configuration.

  4. 4

    Use Docusign from Claude

    Docusign’s approved tools appear in Claude. Every call is checked against policy and recorded.

Tools

30 Docusign tools in Claude

Runlayer policy decides which of these Claude 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.

See all 30 Docusign tools

Control

What Runlayer can see and stop in Claude

Some controls apply to every client at the gateway. Others depend on what Claude exposes to Runlayer.

  • Gateway policy (available)

    Every Docusign call from Claude passes through Runlayer, where your policies can allow, alert, mask, or block it.

  • Audit trail (available)

    Each call is recorded with the user, Claude as the client, the tool, and the policy and scanner decisions.

  • Anthropic inference hooks (available)

    With Claude Enterprise, Anthropic sends each governed Claude prompt to Runlayer before inference, with nothing installed on devices (Anthropic beta).

  • Compliance API import (available)

    Anthropic Compliance API imports Claude web and desktop chats for review.

  • Managed browser extension (available)

    Managed Chrome, Edge, and Firefox deployments can monitor supported web-chat activity and apply prompt-time controls where the surface permits it.

  • Stop a call before it runs (available)

    Runlayer can reject a Claude prompt before Anthropic runs it, which stops the whole request rather than one tool call.

  • Block output after it runs (available)

    Because Runlayer checks the full prompt, tool results in it can be blocked before the model sees them.

  • Redact output in place (not available)

    Anthropic Inference hooks cannot return a rewritten prompt, so Runlayer cannot mask content in Claude. The gateway still applies policy to the call.

Frequently asked questions

Connect more

Find another combination