Contract Signature Lifecycle Tracker

Overview

This solution (FlowLibs - Contract Signature Lifecycle Tracker) automates the full e-signature lifecycle with DocuSign, SharePoint, Outlook, and a Dataverse mirror table. When a finalized contract lands in a SharePoint library, the solution creates and sends a DocuSign envelope (uploading the actual document), tracks status changes (sent → delivered → signed → completed), files the completed signed PDF back into a SharePoint "Signed" library, notifies stakeholders at each milestone, and escalates envelopes that stall past a configurable SLA.

It is built as three cloud flows + one Dataverse table in a single solution, so the send, track, and escalate concerns are each driven by their natural trigger (SharePoint event, DocuSign event, schedule). A correlationId is minted at send time and carried through the mirror row and every notification for end-to-end tracing.

Why it matters: Signature chases are pure overhead. Automating send, status tracking, completed-doc filing, and SLA escalation closes contracts faster and keeps a clean, auditable record in SharePoint and Dataverse.

State: All three flows ship Off (demo). Going live requires only authorizing the four connections, setting a real DocuSign Account ID env var, and pointing the SharePoint/email env vars at real targets.

Use Case

Ops/legal teams route contracts for signature and then lose track of them in inboxes. They want one governed pipeline that sends, watches, files the signed copy, and nudges late signers — with stakeholders informed automatically and a Dataverse record for reporting.

Flow Architecture

Environment Variables

Connectors & Connections

Connector	API name	Actions used
DocuSign	shared_docusign	CreateBlankEnvelope AddDocumentsToEnvelope AddRecipientToEnvelope SendDraftEnvelope OnEnvelopeStatusChanges GetDocumentsV2 AddReminders
SharePoint	shared_sharepointonline	GetOnNewFileItems GetFileContent CreateFile
Office 365 Outlook	shared_office365	SendEmailV2

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.

Signing tabs / templates

For production, route signers via a DocuSign template (with pre-placed signature tabs) by swapping the CreateBlankEnvelope → AddDocumentsToEnvelope → AddRecipientToEnvelope → SendDraftEnvelope chain for SendEnvelope with a templateId, or add signHere anchor tabs to the recipient.

Trigger filter

Add a SharePoint column filter (e.g. a Ready for Signature choice) so only flagged contracts send, instead of every new file.

Real-time status

Replace Flow 2's polling trigger with the DocuSign Connect webhook (CreateHookEnvelopeV3) for instant status events (requires a DocuSign Connect configuration on the account).

Multiple signers

Extend AddRecipientToEnvelope's newRecipient/signers array with additional ordered recipients for counter-signatures.

Reporting

The flowlibs_contractenvelope table already mirrors every envelope; point a Power BI report at it for cycle-time and completion-rate dashboards.

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.

@body('Get_File_Content')?['$content']

@{toLower(last(split(triggerOutputs()?['body/{FilenameWithExtension}'],'.')))}

@{concat('flowlibs_envelopeid eq ''', triggerOutputs()?['body/envelopeId'], '''')}

@equals(toLower(triggerOutputs()?['body/status']), variables('varCompletedStatus'))

@greater(div(sub(ticks(variables('varNow')), ticks(items('For_Each_Outstanding')?['flowlibs_senton'])), 36000000000), variables('varSlaHours'))

Customize & download