DocuSign eSignature
Put DocuSign eSignature to work on your own records, inside your rules, with a person approving what it changes.
24 ways to read, 5 ways to write, each write switched on by you.
Quality checks
Built and tested with example responses.
- Ready to connect: doneEvery listed action is built in.
- Built and tested with example responses: doneEach action is built from the provider’s published API and tested against example responses, errors, rate limits and paging.
Connected, approved, proven.
The things teams do most with DocuSign eSignature, an example flow with a person in the loop, and what Nexra keeps as proof.
Top actions
- Add envelope custom fieldApproval by rule
- Create draft envelope from documentsApproval by rule
- List brandsRead
Example flow
- Dynamics 365 Sales · Read opportunitiesDone
- DocuSign eSignature · Create draft envelope from templateNeeds approval
- Nexra · Record the decision and result in the evidence chainProven
Example workflow. Routine runs go through on their own. Only a change your rules flag, such as one over a limit you set, waits for the right person, who sees the exact change and the rule before it reaches DocuSign eSignature.
What gets logged
- Whether it ran on its own or who approved it, and under which rule
- A fingerprint of the exact request sent to DocuSign eSignature
- DocuSign eSignature's reply: what it created or changed
- One entry in the evidence chain, linked to the one before
Try this in the sandbox
Run the whole flow with test data in your sandbox, then connect a Docusign test account before you go live.
For developers
Technical detail
DocuSign envelopes, recipients, fields, documents, audit events, templates, users, groups, folders, brands, PowerForms and Connect settings; draft envelopes from templates or documents.
Docusign API docs- Source actions
- 24
- Destination actions
- 5
- Data types
- 20
What you can map
Reads are always available. Writes are off until you switch them on for a connection, and governed writes follow your policies.
Account1
- Get accountSource
Account name, plan and envelope usage for the billing period.
Brands2
- Get brandSource
One brand with its languages and colours.
- List brandsSource
Sending and signing brands configured on the account.
Connect configurations2
- Get Connect configurationSource
One Connect webhook configuration (secrets and URL queries removed).
- List Connect configurationsSource
Account-level Connect webhook configurations (secrets and URL queries removed).
Envelope audit events1
- List envelope audit eventsSource
The envelope history: who did what and when.
Envelope custom fields3
- Add envelope custom fieldDestinationNot retried automaticallyApproval before production
Adds a text custom field (for example a CRM or deal ID) to an envelope.
- List envelope custom fieldsSource
Text and list custom fields on an envelope.
- Update envelope custom fieldDestinationProvider duplicate protectionApproval before production
Changes the value of an existing text custom field.
Envelope documents1
- List envelope documentsSource
Document metadata for an envelope; contents are not downloaded.
Envelope drafts1
- Create draft envelope from documentsDestinationNot retried automaticallyApproval before production
Creates a draft (status created) envelope from uploaded documents with signers and carbon copies. Nothing is emailed.
Envelope form data1
- Get envelope form dataSource
Values recipients entered in the envelope's fields (tabs).
Envelope recipients1
- List envelope recipientsSource
Every recipient on an envelope with routing order and signing status.
Envelopes4
- Create draft envelope from templateDestinationNot retried automaticallyApproval before production
Creates a draft (status created) envelope from a server template with recipients for each role. Nothing is emailed.
- Get envelopeSource
Envelope status with recipients and custom fields.
- List envelopesSourceIncremental
Envelopes whose status changed since a date, optionally filtered by status.
- Send envelopeDestinationNot retried automaticallyApproval before production
High risk: sends a draft envelope, emailing every recipient a legally binding signature request.
Folder items1
- List folder itemsSourceIncremental
Envelopes in a folder, optionally by status and date range.
Folders1
- List foldersSource
Envelope folders (inbox, sent items, drafts and custom folders).
Groups1
- List groupsSource
Permission groups in the account with their user counts.
Powerforms1
- List PowerFormsSourceIncremental
Self-service signing forms with their usage.
Recipient tabs1
- List recipient fieldsSource
The fields (tabs) assigned to one recipient, with their values.
Signing groups1
- List signing groupsSource
Signing groups whose members can sign on behalf of the group.
Template documents1
- List template documentsSource
Document metadata for a template; contents are not downloaded.
Template recipients1
- List template recipientsSource
Recipient roles defined on a template with routing order.
Templates2
- Get templateSource
A template with its recipient roles, for mapping Create draft envelope.
- List templatesSource
Server templates available to the user.
Users2
- Get userSource
One user in the account.
- List usersSource
Users in the account, optionally filtered by status, email or group.
Access and limits
- Authentication
- DocuSign integration key, secret and refresh token (Authorization Code Grant)
- Plans and access
- eSignature plans with API access; the free developer account covers the demo environment. Integration keys must pass Go-Live review before they work in production. Calls are limited per account per hour.
- Test environment
- Free developer accounts use demo.docusign.net with account-d.docusign.com.
- Rate limits
- 3,000 API calls per hour per account (burst 500 per 30 seconds); poll an envelope's status at most once every 15 minutes. HTTP 429.
- Pagination
- start_position and count with totalSetSize for envelopes and templates.
- Provider events
- DocuSign Connect and envelope-level eventNotification webhooks, signed with X-DocuSign-Signature-1 (base64 HMAC-SHA256 of the body) when HMAC is turned on. Flows can start the moment something happens: when every recipient has signed; when an envelope is sent; when a recipient declines to sign; when an envelope is voided.
Before you build a flow
- Draft envelopes are created from server templates or from inline base64 documents (about 3 MB in total); new drafts are always status created.
- Envelope creation and sending have no idempotency key; uncertain writes are not repeated automatically.
- Voiding, correcting recipients, resending, deleting, purging and document downloads are intentionally not implemented.
- Connect configuration reads drop passwords, Salesforce credentials and the listener URL's query string.
- Older DocuSign API responses report hourly or burst limits as HTTP 400 with errorCode HOURLY_APIINVOCATION_LIMIT_EXCEEDED or BURST_APIINVOCATION_LIMIT_EXCEEDED; Nexra classifies those as rate limits.
- Polling is subject to DocuSign's polling rules; prefer Connect for status updates once triggers are available.
- Nexra has no separate risk flag; sending is marked as a send action and described as high risk.
Developer reference
- Create the Docusign credentials described above with the narrowest permissions your flows need.
- In Nexra, open Connect, then Connections, then New connection, choose DocuSign eSignature, enter its settings and credentials, and tick only the write actions you need. Connection guide
- Test the connection, then use its actions as flow sources and destinations. Flow guide
Machine-readable detail: GET /api/public/connect/connectors/docusign and the Connections API.