Adobe PDF Contract Assembly and Merge

Overview

FlowLibs - Adobe PDF Contract Assembly and Merge stitches a multi-part contract into a single, correctly ordered PDF using Adobe PDF Services Combine. On request it receives the ordered list of part files (cover letter, main agreement, terms, exhibits), uploads each to Adobe, combines them in order, files the assembled PDF back to SharePoint, and emails it to the reviewer/signer with the PDF attached.

Why it matters: Manually stitching cover letters, agreements, terms, and exhibits is slow and inconsistent. This flow guarantees the parts always combine in the correct order and the finished contract is filed and delivered automatically.

Status: Built — ships Off (demo). Going live requires only authorizing the SharePoint and Office 365 Outlook connections, setting the Adobe ClientId/ClientSecret environment variable values, and invoking the trigger URL from the upstream Power App / approval / button.

Use Case

Legal and operations teams assemble contracts from standard parts kept in a SharePoint library. When a contract is ready, an upstream app, approval, or button posts the ordered list of part paths to this flow. It returns a single assembled PDF — filed in SharePoint and emailed for review or signature — removing manual PDF stitching and guaranteeing correct ordering every time.

Flow Architecture

Environment Variables

Connectors & Connections

Connector	API name	Actions used
HHTTP	http	POST /token POST /assets PUT (upload) POST /operation/combinepdf GET (status/download)
SharePoint	shared_sharepointonline	GetFileContentByPath CreateFile
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.

e-signature

Route the assembled PDF to DocuSign / Adobe Sign instead of (or alongside) the review email.

Library auto-gathering

Replace the partPaths input with a SharePoint GetFileItems on a folder plus an ordering rule, if you prefer the flow to enumerate the parts itself rather than receiving an explicit ordered list.

Office parts

Combine requires PDFs. Convert any Word/Excel/PowerPoint parts first with Adobe createpdf before assembly.

Page ranges

The Combine body supports a per-asset pageRanges array ({start,end}) to include only specific pages of a source file.

Cover page / bookmarks

Prepend a generated cover (Adobe Document Generation) or add a post-combine bookmarking step for navigation.

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.

@{concat('client_id=',encodeUriComponent(variables('varAdobeClientId')),'&client_secret=',encodeUriComponent(variables('varAdobeClientSecret')))}

@json(concat('{"assetID":"',body('Create_Adobe_Upload_Asset')?['assetID'],'"}'))

{ "assets": @variables('varAssetList') }

@{coalesce(outputs('Start_Combine_Job')?['headers']?['location'],outputs('Start_Combine_Job')?['headers']?['Location'])}

@base64ToBinary(body('Get_Part_File_Content')?['$content'])

Customize & download