DocuSign Declined or Voided Recovery

Overview

This flow turns failed DocuSign signatures into a structured recovery workflow instead of a dead end. On a daily schedule it scans DocuSign for envelopes that were declined or voided, captures the recipient's reason, logs each one as a recovery record in Dataverse (carrying the CRM pipeline stage so the deal is re-engaged, not lost), and alerts the owner channel in Microsoft Teams so a human can act immediately.

Why it matters: a declined or voided envelope usually ends silently. Surfacing it with the reason, a follow-up record, and a stage change keeps the opportunity alive.

Ships Off (demo).

Use Case

A sales/operations team wants immediate, actionable handling of declined or voided agreements. Rather than discovering a dead deal weeks later, the team gets a same-day Teams alert plus a Dataverse recovery record with the decline reason and a re-engage stage, so the opportunity can be saved.

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.

Real CRM stage update

Add a Dataverse or Salesforce UpdateRecord keyed on the opportunity tied to the envelope to push the Re-engage stage onto the deal.

Auto-resend

Chain DocuSign CreateEnvelopeFromTemplate / SendEnvelope to offer a corrected envelope automatically.

Escalation

Add a condition on envelope value/custom field to involve a manager (Approvals) for large deals.

Reason analytics

Point Power BI at the recoveries table to trend decline reasons over time.

Scan cadence

Raise the recurrence frequency and lower the lookback days together for near-real-time recovery.

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.

addDays(utcNow(), sub(0, int(variables('varLookbackDays'))))

coalesce(first(body('Get_Recipient_Decline_Reason')?['signers'])?['declinedReason'], first(body('Get_Recipient_Decline_Reason')?['recipients']?['signers'])?['declinedReason'], 'No reason recorded')

outputs('Search_Declined_or_Voided_Envelopes')?['body/value']

guid()