At a glance
- Availability: Experimental (how to enable).
- Auth: OAuth 2.0.
- Connection: A user authorizes the connection in the provider’s consent screen.
- Scopes:
signature. - Optional scopes:
extended. - Docs: https://developers.docusign.com/platform/auth/authcode/
Credentials
Set these per environment. See Connect an integration. With a managed OAuth app, Connect works without these variables; set them to use your own OAuth app instead.Setup
- Create a free developer account: Sign up at https://developers.docusign.com (free developer sandbox). Developer accounts authenticate via https://account-d.docusign.com and use the demo API host https://demo.docusign.net; production uses https://account.docusign.com and your account’s own base host. This connector is configured for production - for sandbox testing, swap the auth URLs to account-d.docusign.com.
- Create an app and integration key: In the developer account, open Settings (Admin), then Apps and Keys, and create a new app. Copy the integration key (this is DOCUSIGN_CLIENT_ID), generate a secret key (DOCUSIGN_CLIENT_SECRET), and add your redirect URI ending in /oauth/callback/docusign.
- Find your account server and account ID: After connecting, call GET https://account.docusign.com/oauth/userinfo (or account-d.docusign.com for developer accounts) with your access token. The response lists your accounts, each with an account_id (GUID) and a base_uri such as https://na3.docusign.net. Use the base_uri host as the accountServer parameter (e.g. na3.docusign.net, or demo.docusign.net for developer accounts) and account_id as accountId. Admins can also see the API Account ID under Settings, then Apps and Keys.
- Verify access: Run the List Envelopes tool with your accountServer, accountId, and a from_date such as the first day of last month.
- Go live for production: Apps built in the developer sandbox must pass DocuSign’s go-live review before they can use production accounts. Until then, keep using the developer environment.
- The eSignature REST base URL is account-specific: https://{base_uri host}/restapi/v2.1/accounts/{accountId}/… - both values come from /oauth/userinfo
- The signature scope covers sending and tracking envelopes; the optional extended scope lets refresh tokens be renewed beyond 30 days
- List Envelopes requires from_date (or specific envelope IDs); Download Envelope Documents returns raw PDF bytes
Tools
| Tool | Access | Description |
|---|---|---|
| Get User Info | Read | Get the connected user’s accounts from the OAuth userinfo endpoint - the source of the accountServer (base_uri host) and accountId values every other tool needs |
| List Envelopes | Read | List envelope status changes in an account to track what is sent, delivered, or completed |
| Get Envelope | Read | Get the status and details of a single envelope by ID |
| List Envelope Recipients | Read | List the recipients of an envelope and their signing status |
| Create and Send Envelope | Write | Create an envelope with documents and recipients and send it for signature |
| Resend Envelope | Write | Resend the signing request email to an in-progress envelope’s pending recipients, e.g. to chase outstanding signers |
| List Templates | Read | List the reusable envelope templates in an account, e.g. to find a template before sending from it |
| Download Envelope Documents | Read | Download all documents of an envelope as a single combined PDF |
Example prompts
- List my recent DocuSign envelopes and summarize which are completed, awaiting signature, declined, or voided.
- Send a document I provide for signature via DocuSign to a recipient I specify, then confirm the envelope was sent.
- Find DocuSign envelopes still awaiting signature, list who has not signed yet, and draft follow-up messages.