Adobe PDF Split and Route

Overview

When a multi-document PDF (a batch scan or merged report) arrives in a SharePoint intake library, this flow splits it into smaller PDFs with Adobe PDF Services, files each part into the correct SharePoint folder using a configurable naming/routing rule, and emails the destination owner.

Why it matters: Batch scans and merged exports must be separated before they are useful. Automated split + content-routing removes manual page-chopping and misfiling. Adobe is called via the built-in HTTP action (token -> assets -> PUT upload -> operation/splitpdf -> poll -> download), so no Adobe connection reference is needed — credentials come from environment variables.

Use Case

Operations, mailroom, and records teams that receive combined PDFs and need each embedded document split out, filed to the right library folder, and the owner notified — without manual handling.

Flow Architecture

Environment Variables

Connectors & Connections

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

Split mode

This build splits by pages-per-file (splitoption.pageCount). Switch to page ranges (pageRanges) or a fixed file count (fileCount) by editing the Start Split Job body. (split-by-bookmark is not a native Adobe REST option.)

Content-based routing

Add an OCR/extract step (Adobe extractpdf) to derive the routing key from document content instead of the filename prefix.

Routing & owners

Edit flowlibs_SplitRoutingMap to add prefixes, folders, and owners; unmatched parts fall back to flowlibs_SplitDefaultFolder + flowlibs_OwnerNotificationEmail.

Lineage logging

Add a Dataverse table + CreateRecord inside the loop to record split lineage (source -> parts) with the correlation id.

Quarantine

Add a branch to hold parts whose prefix has no routing rule for manual review.

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.

@toUpper(first(split(variables('varSourceFileName'),'-')))

@coalesce(json(variables('varRoutingMap'))?[variables('varRoutePrefix')]?['folder'], variables('varDefaultFolder'))

@coalesce(json(variables('varRoutingMap'))?[variables('varRoutePrefix')]?['owner'], variables('varDefaultOwner'))

@concat(variables('varRoutePrefix'),'-',formatDateTime(utcNow(),'yyyyMMddHHmmss'),'-part',string(variables('varPartIndex')),'.pdf')

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

@int(variables('varSplitPageCount'))

@outputs('Start_Split_Job')?['headers']?['location']

@coalesce(outputs('Get_Split_Job_Status')?['body']?['assetList'], json('[]'))

Customize & download