> For the complete documentation index, see [llms.txt](https://help.filed.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.filed.com/reference/plugins/integrations/documents-and-signatures/docusign.md).

# DocuSign

With this integration connected, you can use Filed **Chat** and **Routines** to retrieve information from Docusign and, when **Write** access is enabled, perform approved actions in Docusign. This integration to Filed is connected via our integration provider [Composio](https://composio.dev/)

## Connect DocuSign

1. Name the connection for the correct DocuSign account or environment.
2. Sign in with a user who can access the required envelopes and templates.
3. Approve authorization and return to Filed for verification.
4. Confirm whether you are using production or demo before enabling write access.

If Filed asks for organization-specific app credentials, get them from your DocuSign administrator. Do not use production credentials in a demo environment.

## Verify the connection

After the connection becomes **Active**, open a known item that the authorized account should be able to access. Confirm account environment, envelopes, and templates. For a new connection, test against a non-production or non-client-sensitive item before relying on it in a deadline-driven workflow.

## Manage permissions

Read access is always enabled. Turn off **Write** in the connection settings to prevent Filed from creating or modifying DocuSign data while keeping the connection available for read-only workflows. Re-enable it only after the firm approves the change.

## Troubleshooting

**The authorization screen will not complete.** Sign out of the wrong provider account, restart the connection, and use the firm-managed account that has account environment, envelopes, and templates.

**The connection is active but data is missing.** The provider only exposes content available to the authorized user. Review account environment, envelopes, and templates, then reconnect if the account or environment was wrong.

**The connection is pending or failed.** Open the connection in Filed, correct the provider-side issue, and select **Reconnect**. Do not create duplicate connections to work around a permissions problem.

## Using this integration with Filed Chat and Routines

Use **Chat** for one-off questions and guided work on a client, such as finding DocuSign information, summarizing it, or preparing an approved next step. Use **Routines** to automate repeatable work with DocuSign data on a schedule or in response to a trigger.

Both experiences respect the connection's access: they can only use data the authorized account can reach, and they can only perform changes when **Write** is enabled. Review changes in the connected application before you finalize them.

## Example prompts

Use these as starting points and replace the bracketed details with the client, date range, folder, record, or task you need. Filed will only run write actions when this connection's **Write** access is enabled.

* “Summarize the Docusign information for \[client name] for \[date range].”
* “Find records in Docusign that need review before \[deadline].”
* “With write access enabled, prepare the approved Docusign update and show the proposed changes first.”

## Capabilities

### Review document and signature status

Use Filed to retrieve the documents, templates, envelopes, or signature requests available to the connected account. This helps identify what is ready, pending, completed, or needs attention.

### Prepare approved documents

When **Write** access is enabled, Filed can support the approved creation or update of provider records. Use it only when your firm has defined who may send, edit, or finalize client-facing documents.

### Keep signing authority with your firm

The provider’s own workspace, template, and user permissions remain the source of truth. Use those controls to limit which documents the connected account can access.


---

# 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://help.filed.com/reference/plugins/integrations/documents-and-signatures/docusign.md?ask=<question>&goal=<endgoal>
```

`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.