docusign.createEnvelope()excel.writeRow()sharepoint.upload(pdf)slack.postMessage()sms.send(reminder)graph.api/files
← Back to projects
Case study

Digital signature lifecycle · DocuSign · Multi-region tracking

3
Delivery channels
Full
Document lifecycle
Auto
Reminder system
PDF
SharePoint archive
n8nDocuSignMicrosoft ExcelMicrosoft SharePointMicrosoft OutlookMicrosoft GraphSlackJavaScript
Jump to proof of work

Overview

I designed and built an automation workflow for the full lifecycle of digital signature documents: preparing customer data, sending the certificate through DocuSign, tracking envelope status, monitoring unsigned documents, and storing completed PDFs in the correct SharePoint customer folder.

The workflow connects n8n, DocuSign, Microsoft Excel, SharePoint, Outlook, Slack, and SMS communication into one document-tracking process.

The goal was not only to send a document for signature, but to create a reliable process around it: validation before sending, tracking after sending, reminders when signatures are missing, and automatic archiving when the signed document is completed.

01 / Problem

The challenge

The dispatch process required customers to receive, sign, and return digital signature documents before operational work could be completed safely and consistently.

The challenge was to automate the certificate delivery, tracking, reminder, and storage process while keeping it connected to existing dispatch data, regional records, and Microsoft 365 document storage.

Without a structured tracking layer, it would be difficult to see which certificates were sent, which were still unsigned, which needed follow-up, and where completed PDFs should be stored.

02 / Role

What I did

I designed, built, tested, and maintained the automation layer for the digital signature workflow.

My work included preparing and validating customer data, building the DocuSign sending workflow, creating tracking logic, connecting Microsoft Excel and SharePoint, processing completed DocuSign emails, matching completed envelopes to the correct customer records, and adding Slack notifications for operational visibility.

03 / Architecture

System flow

01Pre-Dispatch Workflow
02Customer + Appointment Data
03Data Validation + Normalization
04DocuSign Envelope Preparation
05Certificate Delivery: Email / SMS / Email + SMS
06DocuSign Tracking Excel Record
07Reminder Monitoring
08Completed DocuSign Email Detection
09Envelope ID Matching
10Region + Customer Lookup
11Signed PDF Upload to SharePoint
12Tracking Update: COMPLETED
13Slack Team Notification
04 / Modules

Core modules

01

Data validation and normalization

Before sending the certificate, the workflow validates and normalizes the required customer and appointment data. This includes customer name, phone number, email address, appointment data, certificate-related fields, and internal tracking references. The purpose is to avoid sending incomplete or inconsistent certificate requests.

02

DocuSign envelope preparation

The workflow prepares the DocuSign envelope using structured data from the dispatch process. It maps the required customer and certificate fields into the signature process and sends the document through the available delivery channel: Email, SMS, or Email + SMS.

03

Certificate tracking

Every sent certificate is written into a tracking table. The tracking layer stores the relevant operational state: certificate sent, envelope reference, customer reference, sent timestamp, reminder status, and completion status. This makes the document lifecycle traceable after the certificate has been sent.

04

Reminder monitoring

A follow-up workflow monitors certificates that were sent but remain unsigned. It checks whether a reminder has already been sent, whether the certificate is still open, and whether the appointment timing requires additional attention.

05

Daily summaries and warnings

The system generates daily summaries for open or risky certificate cases. Slack notifications inform the team when action may be required, such as an upcoming appointment with an unsigned certificate.

06

Completed certificate processing

When DocuSign sends a completed email, a separate workflow processes the completion event. It extracts the envelope ID, matches it against tracking records, detects the correct region, finds the customer record, and prepares the signed PDF for upload.

07

SharePoint archiving

After the completed certificate is identified, the signed PDF is uploaded into the correct SharePoint customer folder. The workflow uses the matched customer and region data to build the correct document path. After upload, the tracking status is updated to completed and the team receives a Slack confirmation.

05 / Decisions

Technical decisions

Separate sending and completion workflows

Sending a certificate and processing the completed certificate are handled by separate workflows. This makes the process easier to debug and reduces the risk of mixing active sending logic with completed document storage logic.

Tracking-first design

The system does not rely only on DocuSign emails. It writes sent certificates into a tracking table so the automation can later monitor status, reminders, and completed documents.

Microsoft 365 integration

Excel and SharePoint are used because they already fit into the operational environment. The workflow stores tracking data in Excel and archives completed PDFs in SharePoint instead of forcing the team into a separate system.

Slack visibility

Slack notifications are used for operational visibility: completed uploads, reminder situations, daily summaries, and cases that require attention.

Region-aware processing

The completed document workflow checks tracking data across multiple operational regions and uses the matched envelope/customer record to decide where the signed PDF belongs.

06 / Reliability

Reliability patterns

Required-field validationPhone number normalizationEnvelope trackingReminder status checksRegion detectionCustomer record lookupCompleted PDF uploadTracking status updateSlack success notificationsError awareness for missing or unmatched records

The workflow is designed around traceability: each document should move through a clear lifecycle from sent, to reminded if needed, to completed, to archived.

07 / Impact

The outcome

The automation made the digital signature workflow more structured and traceable.

It connected certificate sending, status tracking, reminder monitoring, completed document handling, SharePoint archiving, and Slack visibility into one coordinated workflow.

The main impact was traceable document handling: the team could see which certificates were sent, which remained unsigned, where follow-up was needed, and when completed PDFs were stored successfully.

08 / Stack

Tech stack

n8nWorkflow orchestration, data preparation, routing, tracking, and sub-workflows
DocuSignDigital signature workflow for operational documents
Microsoft ExcelTracking tables for sent, reminded, and completed certificate states
Microsoft SharePointStorage of completed signed PDF documents in customer folders
Microsoft OutlookCompleted DocuSign email detection and attachment processing
Microsoft GraphSharePoint folder and file upload operations
SlackTeam notifications, warnings, summaries, and upload confirmations
JavaScriptData validation, normalization, envelope matching, region detection, date handling
09 / Proof

Proof / Evidence

This case study is based on a DocuSign certificate automation workflow. The architecture is documented openly. Customer data, phone numbers, email addresses, DocuSign envelope IDs, internal SharePoint paths, Excel workbook IDs, credentials, webhook URLs, and workflow exports are not part of the public material.

Public proof shown on this page

Dispatch DataPrepare & ValidateCertificate DataSend DocuSignCertificateWrite Tracking RecordReminder MonitoringDocuSign CompletedEventMatch Envelope toRecordUpload Signed PDF toSharePointUpdate Status:COMPLETEDSlack Notification

Lifecycle diagram showing the digital signature document flow from dispatch data to DocuSign sending, tracking, reminders, completion handling, signed PDF storage in SharePoint, and Slack team notification.

Live system

The actual n8n workflow canvas for the digital signature workflow automation — the same flow the architecture diagram above abstracts.

Public code & documentation

Valentino-Veljanovski / multi-region-dispatch-automation-snippetsPublic

DocuSign signing and completion-handling module inside the multi-region dispatch automation. The repository includes the dispatch architecture, DocuSign integration notes, and JavaScript helper snippets for envelope extraction and SharePoint upload routing.

n8nautomationworkflow-automationazure-openaimicrosoft-365docusignslack-integrationarchitecture-patternscase-study
View on GitHub

Code excerpt: DocuSign envelope completion handler

When DocuSign reports a completed envelope (via webhook or completed-email detection), this node extracts the envelope details, looks up the matching tracking record by envelope ID, and prepares the SharePoint upload path. The full handler continues with the PDF download and tracking-row update.

docusign-envelope-extractor.jsjavascript
// After detecting a completed DocuSign envelope (via webhook
// or completed-email detection), extract the envelope details
// and find the matching tracking record in the regional sheet.

const envelope = $input.first().json;

const envelopeId = envelope.envelopeId;
const recipientName = envelope.recipients?.signers?.[0]?.name || "";
const completedAt =
  envelope.completedDateTime || new Date().toISOString();

if (!envelopeId) {
  throw new Error("Missing envelopeId on completed envelope");
}

// Find the tracking row whose envelope_id column matches.
const trackingRows = $("Read Tracking Sheet").first().json.value || [];
const matchingRow = trackingRows.find(
  (row) => row.values?.[0]?.[ENVELOPE_ID_COL] === envelopeId
);

if (!matchingRow) {
  // Not all completion events are ours. Log and exit cleanly.
  return [{ json: { skip: true, envelopeId } }];
}

// Build the SharePoint upload path from the row's fields.
const customer = matchingRow.values[0][CUSTOMER_NAME_COL];
const region = matchingRow.values[0][REGION_COL];
const uploadPath = buildHaftungPath(region, customer, envelopeId);

// ... continues with PDF download from DocuSign and SharePoint upload.
// See snippets/docusign-envelope-extractor.js for the full handler.

Full handler in snippets/docusign-envelope-extractor.js. The integration flow is documented in docs/docusign-integration.md.

Confidentiality & Publication Note

This case study describes a document-signing and tracking workflow in anonymized form. The public material does not publish customer names, phone numbers, email addresses, DocuSign account IDs, envelope IDs, template IDs, internal SharePoint URLs, Excel workbook IDs, webhook URLs, credentials, or raw workflow exports. The workflow is presented as a technical case study of document lifecycle automation, not as a legal compliance guarantee.

← Back to all projects