DocuSign Send-for-Signature from Dataverse

Overview

Automates outbound e-signature requests directly from the system of record. When a Signature Request row in Dataverse reaches the Ready to Sign status, a send flow creates and dispatches a DocuSign envelope from a template, writes the envelope id (and a correlation id) back to the row, and notifies operations. A companion tracker flow polls DocuSign hourly for completed envelopes and reconciles each one back to its source row.

Why it matters: Manually preparing and sending agreements is slow and error-prone. Driving DocuSign from Dataverse keeps signature requests accurate and timely, and the completion write-back keeps the system of record in sync without anyone watching the DocuSign console.

Built as: one solution, two flows + one Dataverse table (event-driven send + scheduled completion reconciliation). Both flows ship Off.

Use Case

A sales/operations team manages agreements (quotes, contracts, NDAs) as Dataverse rows. When a row is marked Ready to Sign, the agreement should be sent for signature automatically, the envelope id captured against the row, and the row flipped to Completed once everyone has signed - all without manual DocuSign steps.

Flow Architecture

Environment Variables

Connectors & Connections

Connector	API name	Actions used
DocuSign	shared_docusign	CreateEnvelopeFromTemplateNoRecipients SearchListEnvelopes
Microsoft Dataverse	shared_commondataserviceforapps	SubscribeWebhookTrigger UpdateRecord ListRecords
Office 365 Outlook	shared_office365	SendEmailV2

Note — All connections are referenced as solution connection references; the flow is portable between environments as long as a connection is mapped at import time.

Customization Guide

Almost every realistic variant of this flow can be implemented by changing environment variable values. A few cases require small edits inside the flow definition — those are called out explicitly below.

Conditional template

Branch on a deal-type column to pick a different templateId per agreement.

Multi-signer routing

Define signer roles and routing order on the DocuSign template; the flow sends without changing.

Reminders / expiry

Add a DocuSign AddReminders call after the send to enable nudges.

CC parties

Add observer roles on the template.

Real-time completion

Replace Flow B's hourly poll with a DocuSign Connect webhook (CreateHookEnvelopeV3) trigger for instant reconciliation.

Tune the poll window

Flow B searches the last 7 days; widen for low-volume, narrow for high-volume.

Key Expressions

The flow is intentionally light on Power Fx / WDL gymnastics — the heaviest expressions are the branch-name concatenation and the approval outcome check. They are listed below in the order they appear in the flow.

@equals(triggerOutputs()?['body/flowlibs_signingstatus'], variables('varReadyStatus'))

@{body('Send_DocuSign_Envelope')?['envelopeId']}

@{guid()}

from_date = @{addDays(utcNow(),-7)}

$filter = flowlibs_envelopeid eq '@{items('For_Each_Completed_Envelope')?['envelopeId']}'

@{first(outputs('Find_Request_By_Envelope')?['body/value'])?['flowlibs_signaturerequestid']}

Customize & download