> For the complete documentation index, see [llms.txt](https://www.cakewalk.security/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.cakewalk.security/docs/ai-agent-access/connections-and-integrations/agent-connections/docusign.md). # Docusign Connect your company's Docusign account to Cakewalk so agents can read envelopes, send signature requests and manage workflows through the gateway. Connect your company's Docusign account to Cakewalk's MCP Gateway. Every agent tool call against Docusign passes through the gateway and is evaluated against your Policies. ## Requirements * Docusign admin who can access **Apps and Keys** in eSignature Admin. ## About Scopes Docusign surfaces required scopes on the OAuth consent screen at connect time, rather than on the app's configuration page. You will approve the scope set in the Docusign consent flow; nothing is preselected on the integration. Scopes limited to read access constrain agent actions; scopes that include envelope creation enable sending. ## Step 1: Create an Integration 1. Open (developer account). For production, use `https://apps.docusign.com/admin/apps-and-keys`. 2. In the **INTEGRATIONS** sidebar, click **Apps and Keys**. 3. Click **Add App and Integration Key**. 4. Add a name for your app, then click **ADD**. You land on the integration's configuration page. The top section shows the **Integration Key**, a GUID that Cakewalk uses as the Client ID. ## Step 2: Pick the Authentication Method Docusign ships two versions of this flow. Pick the confidential one. 1. Under the authentication method picker, select **Authorization Code Grant**. 2. Keep the confidential version, the one that pairs the Integration Key with a Secret Key. You create that Secret Key in Step 5. The public version has no Secret Key, and Cakewalk's gateway authenticates with one. 3. If Docusign asks whether the app is for your own account or for distribution to other Docusign customers, choose your own account. Docusign treats PKCE as an optional extra layer on the confidential flow, not a replacement for the Secret Key. Leaving it on does not remove the Secret Key field. ## Step 3: Configure the Redirect URI 1. Scroll to the **Redirect URIs** section. 2. Click **ADD URI**. 3. Enter: ``` https://mcp-gateway.getcakewalk.io/api/v1/Auth/Callback ``` 4. Click **SAVE**. ## Step 4: Allow Cakewalk's Origin Docusign checks the origin a connect request comes from separately from the redirect URI. Without this entry the consent screen completes and the Connection still fails. 1. Stay on the integration's configuration page. 2. Find the CORS settings, where Docusign lists the origins it accepts requests from. 3. Add: ``` https://app.getcakewalk.io ``` 4. Click **SAVE**. {% hint style="warning" %} Match the protocol exactly. Docusign reads `https://app.getcakewalk.io` and `http://app.getcakewalk.io` as two different origins, and a non default port makes a third. {% endhint %} ## Step 5: Generate a Secret Key 1. Scroll to the **Secret Keys** section. 2. Click **+ Add Secret Key**. 3. Copy the secret value immediately. Docusign shows it once. The secret is Cakewalk's Client Secret. ## Step 6: Paste Credentials Into Cakewalk 1. Open . 2. Go to All Connections. 3. Find Docusign. 4. Click Edit credentials. 5. Paste the Integration Key as **Client ID** and the Secret Key as **Client Secret**. 6. Save. ## Step 7: Approve Scopes on Consent When you trigger the OAuth flow from Cakewalk, Docusign presents a consent screen listing the scopes the MCP server requests. Review and approve. If you grant only read scopes, agents cannot send envelopes; pick the scope set that matches the agent actions you want to allow. ## Verifying It Works The Docusign Connection card flips to Active on All Connections. From an agent platform connected to Cakewalk, ask the agent to list your recent Docusign envelopes. If Docusign returns results, the Connection is live. ## Troubleshooting * Invalid redirect URI on consent: confirm the **Redirect URIs** entry matches `https://mcp-gateway.getcakewalk.io/api/v1/Auth/Callback` exactly. Docusign supports multiple URIs on one integration; only the matched one applies. * Consent succeeds but the Connection stays inactive: the redirect URI matched and the origin did not. Check the allowed origins entry from Step 4. Protocol and port both count. * No Secret Keys section on the configuration page: the integration is set to the public version of Authorization Code Grant, which does not use one. Switch it back to the confidential version, per Step 2. * Lost Secret Key: Docusign displays secrets only at creation. If you missed the copy, generate a new Secret Key and reconnect. * Production vs developer: integration keys do not transfer between developer (`apps-d.docusign.com`) and production (`apps.docusign.com`). For a production Connection, repeat these steps on the production admin URL. ## Learn More * [Docusign MCP server](https://developers.docusign.com/platform/mcp-server/) * [Configure an OAuth app in Docusign](https://developers.docusign.com/platform/auth/authcode/) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://www.cakewalk.security/docs/ai-agent-access/connections-and-integrations/agent-connections/docusign.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.