DocuSign Bulk Send Campaign

Overview

This flow runs a DocuSign bulk signature campaign from a Dataverse recipient list. On a schedule it reads every recipient still marked Pending for the active campaign, sends each one a personalized envelope built from a shared DocuSign template, writes the per-recipient status (and envelope id) back to Dataverse, retries failures up to a configurable limit, and posts a completion-rate report to a Microsoft Teams channel.

Why it matters: sending the same document (policy acknowledgement, NDA, renewal) to many people one-by-one is impractical. This turns a recipient table into an automated, trackable signature drive - every recipient gets their own envelope id so progress is auditable and nothing is sent twice.

Ships Off (demo).

Use Case

HR/Operations needs everyone in a group to sign a document and wants progress tracked. Load the recipients into the Dataverse table, set the campaign name + DocuSign template, turn the flow on, and watch the completion rate climb in Teams. Failed sends are retried automatically until the retry cap is reached.

Flow Architecture

Environment Variables

Connectors & Connections

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.

Schedule

Change the recurrence frequency (hourly during a drive, weekly for renewals).

Segment by template

Run multiple campaigns by Campaign Name, each pointing at a different template and signer role.

Reminders

Add a parallel scheduled flow using DocuSign AddReminders to nudge non-signers on Sent envelopes.

Compliance report

Add a Dataverse ListRecords filtered to Sent/Pending and email a who-has-not-signed digest.

Status sync

Pair with a DocuSign OnEnvelopeStatusChanges trigger flow to update the row to Completed when the recipient signs.

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.

flowlibs_sendstatus eq 'Pending' and flowlibs_campaignname eq '<Campaign Name>'

if(greaterOrEquals(add(coalesce(items('Apply_to_each_Recipient')?['flowlibs_retrycount'],0),1), int(variables('varMaxRetries'))), 'Failed', 'Pending')

div(mul(variables('varSentCount'),100), max(variables('varTotalCount'),1))

coalesce(items('Apply_to_each_Recipient')?['flowlibs_signerrole'], variables('varSignerRole'))