DocuSign

Productivity OAuth

Send envelopes for signature, and track their status, with Docusign from any Windmill script, flow or app.

Set up in 3 steps

1

Connect from the Resources page

Open Resources, click Add a resource/API and pick docusign from the OAuth APIs list — there is a separate tile for demo accounts. Sign in and allow access, then name the resource and save it.

2

Fill in the account context

account_id and base_uri pin every call to one Docusign account. Both are on your account's Apps and Keys page, and a demo account uses a different base URI from production.

3

Run your first script

Fork any script below and list envelopes before sending anything.

Scripts

Building blocks, if none of the projects above fit. Fork one, run it, or call it as a step inside your own flow.

Resource type

docusign — the shape of the credential every script on this page expects.

View raw schema →
FieldTypeRequiredWhat it is
account_idstringYesAPI Account ID (GUID). Visible at https://admindemo.docusign.com/apps-and-keys under 'My Account Information'.
base_uristringYesAccount base URI without trailing /restapi, e.g. https://demo.docusign.net (sandbox) or https://na3.docusign.net (production).
tokenstringYesOAuth access token. Populated by Windmill's OAuth flow.

Questions

Why an account id and a base URI?

A Docusign login can span several accounts, each served from a different host. The token alone does not say which one, so both are stored on the resource.

Demo or production?

Separate tiles and separate hosts. A demo envelope is never legally binding, which is what you want while building a flow.

There is no Connect button on my instance

Self-hosted instances need a Docusign OAuth client configured once by an admin before the tile appears.

Is my credential stored on the hub?

Never. It lives only in your own Windmill workspace, encrypted at rest.