DocuSign connector

Send envelopes for signature and read status, recipients and completed documents

Contracts and e-signatureProvided by DocuSignOAuth 2.0 (authorization code)

Authentication

OAuth 2.0 (authorization code)

A named user signs in to the vendor and grants VeroTX access. Refresh tokens are rotated and stored in the platform credential vault.

Requires an interactive sign-in and consent screen from an authorized user of the vendor account.

Credentials are held in the platform credential vault. Agents never see them.
Every call runs as a step in a versioned WorkStream Playbook, so the rules that apply are the rules that were published.
Actions that cross a policy threshold stop at a tollgate and wait for the named approver.
Each call is written to the Execution Ledger with the inputs, the result and the Playbook version in force.

1
Credential resolved
OAuth 2.0 (authorization code) credential released from the vault to the connector runtime. The step never sees the secret.
2
Action called
A WorkStream step called DocuSign with the inputs recorded on the step, under the Playbook version in force.
3
Policy evaluated
Thresholds on the step were checked. Anything over the limit stops at a tollgate and waits for the named approver.
4
Result written
The response from DocuSign, the timing and the Playbook version were written to the Execution Ledger.

Where agreements are drafted, redlined, signed and stored.

Send agreements for signature and read agreement status and signed files

Adobe

Generate, route and track contract documents and approvals

Conga

Send documents for signature and track signing status

Dropbox

Work with contract records, clauses, obligations and approvals

Icertis

Create and track contract workflows, records and approvals

Ironclad

Create documents and quotes, send for signature, track status

PandaDoc

Connectors only matter inside a WorkStream. The product tour walks a request from intake through a tollgate to a recorded result.