# How to Orchestrate Secure DocuSign API Workflows with Claude AI and Kong

This walkthrough shows how a natural-language request in Claude can trigger a governed DocuSign workflow that updates a customer address by calling enterprise APIs through Kong. Rather than letting an AI agent directly and dynamically decide every backend step, the approach separates responsibilities: Claude captures intent and gathers required inputs, DocuSign MCP exposes approved workflow capabilities, and Workflow Builder runs a deterministic, auditable sequence that can include data lookup, validation, approval routing, identity checks, eSignature, and only then a write-back to the system of record. To reach data stored outside DocuSign, a custom extension app sends requests through a Kong gateway to backend services such as databases, CRMs, or ERPs. Kong also supports development and production needs with mocked responses from an OpenAPI spec, scoped identity and access control, plus rate limiting, traffic management, logging, observability, and easier debugging when API calls fail.