DocuSign integration

Quick start

Call DocuSign from your generated app's worker code via the OverSkill composio client. The toolkit slug below maps to DocuSign's public Composio identifier — your app references it by name and OverSkill handles the OAuth round-trip.

// In your generated app's worker handler:
const composio = composioClient(env);

const result = await composio.execute(
  "DOCUSIGN_ACTION_NAME",
  { /* action parameters — see Actions section below */ }
);

return new Response(JSON.stringify(result), {
  headers: { "Content-Type": "application/json" }
});

Replace ACTION_NAME with one of the slugs listed in the Actions section below. The composio client handles auth + rate limits automatically — no API key is exposed to user code.

Setup

This integration uses OAuth, but the platform credentials for DocuSign haven't been registered yet. Reach out to the OverSkill team so we can register the OAuth client_id / client_secret — until then the "Connect" button won't work.

Available actions

338 actions exposed via the DocuSign integration. Each maps to a callable slug — pass it to composio.execute(...) in your worker code.

• DOCUSIGN_ADD_CONTACTS_TO_CONTACTS_LIST
• DOCUSIGN_ADD_EMAIL_OVERRIDES_TO_ENVELOPE
• DOCUSIGN_ADD_ENVELOPE_ATTACHMENTS
• DOCUSIGN_ADD_EXISTING_BRAND_TO_GROUP
• DOCUSIGN_ADD_FILE_TO_WORKSPACE
• DOCUSIGN_ADD_MEMBERS_TO_SIGNING_GROUP
• DOCUSIGN_ADD_NEW_USERS_TO_A_SPECIFIED_ACCOUNT
• DOCUSIGN_ADD_OR_UPDATE_ACCOUNT_STAMPS
• DOCUSIGN_ADD_OR_UPDATE_USER_CUSTOM_SETTINGS
• DOCUSIGN_ADD_OR_UPDATE_USER_SIGNATURE
• DOCUSIGN_ADD_PART_TO_CHUNKED_UPLOAD
• DOCUSIGN_ADD_STEP_TO_ENVELOPE_WORKFLOW