Use the CLM API to locate the contract record by ID or by querying the CLM repository with filter parameters; retrieve the document ID of the final negotiated version
Create an eSignature envelope via the DocuSign eSignature REST API, attaching the CLM document by reference or by uploading it as a document payload; define recipients with their roles, routing order, and tab positions
Send the envelope; poll the envelope status endpoint or use a DocuSign Connect webhook (configured separately in the DocuSign admin console) to receive the voided, declined, or completed status event
On envelope completion, retrieve the signed PDF and the Certificate of Completion from the eSignature API
Write the signed document back to the CLM repository using the CLM Content API upload or update endpoint; update the contract record's lifecycle stage attribute to reflect executed status via the CLM record update endpoint
Trigger any post-execution CLM workflow steps (e.g., obligation extraction, renewal date tagging) using CLM workflow APIs or webhooks configured in your CLM workflow designer
Known gotchas
CLM and eSignature are separate DocuSign products with separate APIs and separate OAuth scopes; a token with only eSignature scope cannot access CLM repository endpoints and vice versa
Sending the CLM document into an eSignature envelope creates a copy of the document in the envelope at that point in time; late changes to the CLM document record do not update an already-sent envelope
CLM workflow stages and attribute names are account-specific and configured by your CLM administrator; do not hard-code stage names — retrieve the workflow schema from the CLM API at runtime
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp