Overview
Docusign is an electronic signature and agreement management platform for sending documents for signature, tracking agreements, and embedding signing in your own applications.
Persona’s Docusign integration lets a Workflow create and send envelopes, check an envelope’s status, list envelopes whose status has changed, and generate a one-time signing link for a signer inside your own application. For example, a Workflow can send an agreement for signature once an individual has passed verification, then check whether it has been completed.
Integration features
The Docusign integration supports these Workflow actions:
- Create and send envelope: Create an envelope from documents or a Docusign template, and send it or save it as a draft.
- List envelope status changes: List envelopes whose status changed in a date range, with optional filters.
- Get envelope status: Return the current status and timestamps of one envelope.
- Create embedded signing view: Return a one-time signing URL for an embedded signer.
Prerequisites
Before configuring the integration, you need:
- A Docusign account. A free Docusign developer account works against Docusign’s demo environment, which is useful for testing.
- Your Docusign API Account ID. In Docusign, go to Admin > Integrations > Apps and Keys to find it. Every action asks for it as the Account ID.
- The Docusign server your account is hosted on. The Apps and Keys page shows it as the Account Base URI, for example
https://na4.docusign.netfor a production account orhttps://demo.docusign.netfor a developer account.
Set up Docusign credentials
Docusign connects through OAuth, so you sign in to Docusign rather than pasting a key.
- In the Persona Dashboard, go to Integrations > Marketplace and select Docusign.
- Click Add Credential and enter a nickname for the credential.
- Select the server that matches your Docusign account: the developer (demo) environment, or the production region your account is hosted on (North America 1 to 4, Europe, Australia, or Canada).
- Sign in to Docusign and approve the requested access.
- Save the credential.
Credentials for the demo environment and for production are separate. A credential connected to one does not work against the other.
Use Docusign in a Workflow
- Create a Workflow, or open the Workflow you want to update.
- Add an Action step and select Integrations.
- Select Docusign, choose the saved credential, and select an action.
- Enter your Account ID and map Persona data to the action’s other input fields.
- Save and publish the Workflow.
Docusign actions
Create and send envelope
Creates an envelope and, by default, sends it to its recipients for signature.
Required fields: Account ID.
Provide the envelope’s content in one of two ways:
- From documents: Set Documents (each with its content as base64, a name, a file extension such as
pdf, and a Document ID such as1) and Recipients (signers, each with an email address, name, Recipient ID, and routing order). - From a template: Set Template ID and Template Roles instead.
Optional fields include:
- Email Subject and Email Message
- Status: Sent sends the envelope immediately, which is the default. Created saves it as a draft.
- Client User ID on a signer: Set it to any unique value to make that signer an embedded signer, who signs through Create embedded signing view instead of receiving a Docusign email. Leave it empty for standard email signing.
The action returns the envelope’s Envelope ID, which the other actions use.
List envelope status changes
Returns envelopes whose status changed within a date range. Use it to find Envelope IDs.
Required fields: Account ID, plus at least one of From Date or Envelope IDs.
Optional fields: To Date, Status, Search Text, Count, Start Position, Order By, Order.
Get envelope status
Returns the current status of one envelope and when it was created, sent, delivered, completed, declined, or voided.
Required fields: Account ID, Envelope ID.
Optional fields: Include, for example to also return recipient details.
Create embedded signing view
Returns a one-time signing URL so a signer can sign inside your own application rather than through a Docusign email.
Required fields: Account ID, Envelope ID, Return URL, Authentication Method.
Optional fields include: Email, Name, Client User ID, Recipient ID, Frame Ancestors, Message Origins.
The signer must have been added to the envelope with a Client User ID, and the Email, Name, and Client User ID you send here must exactly match that signer. After signing, Docusign redirects the signer to the Return URL with an event query parameter, such as event=signing_complete.
The signing URL expires after 5 minutes and can be used only once. Create it immediately before you send the signer to it, and create a new one if it expires.
FAQs
How often can a Workflow check an envelope’s status?
Docusign’s API terms do not allow polling the same envelope’s status more than once every 15 minutes, and frequent polling can get API access suspended. Prefer List envelope status changes over a wide date range to checking one envelope repeatedly.
Are envelopes sent from a developer account legally binding?
No. Documents sent from a Docusign developer account carry a demonstration watermark and are not legally binding. Use a production Docusign account for real agreements.
Plans Explained
Docusign Integration by plan
| Startup Program | Essential Plan | Growth Plan | Enterprise Plan | |
|---|---|---|---|---|
| Docusign Integration | Not Available | Not Available | Limited | Available |