Document workflow automation is the practice of moving a document from intake to signed delivery without manual steps. A TurboDocx Pipeline watches a source location, resolves signer details, places signature fields, sends the document for e-signature, and returns the signed file and its audit trail to the destination you choose. The team configures it once. After that, it runs unattended.
This is a composite case study drawn from how TurboDocx professional services sets these workflows up for enterprise operations teams. The persona here is a national field-service retailer that still runs a legacy back-office ERP as its system of record, alongside SharePoint for day-to-day files. The goal was simple to state and historically painful to build: a document dropped in SharePoint should come back signed, with the correct signer resolved automatically from the ERP, and someone in the field should be able to kick it off and watch it from an iPad. We call the result the tailored suit without the tailor price: enterprise-grade automation across old and new systems, with no custom glue code to maintain.
The challenge: old system of record, modern workflow
The operations team had two hard constraints. First, the signer for any given agreement lived in the back-office ERP, not in a spreadsheet and not in SharePoint. Whoever built the workflow had to read from that ERP reliably. Second, the ERP sat behind the corporate firewall, and security would not open an inbound hole to reach it. Any integration had to respect that boundary.
On top of that, the people starting these agreements were rarely at a desk. They were on a store floor or at a job site with a tablet. The workflow could not depend on a technician logging into a back-end console. It had to begin with something as ordinary as saving a file, and it had to be observable from the field.
In the past, stitching those requirements together meant a custom integration project: a middleware service, credentials to rotate, a queue to babysit, and a maintenance burden that outlived the person who built it. The team wanted the outcome without owning that code.
How the pipeline works, end to end
1.A document lands in SharePoint
A field team member or a back-office user saves the agreement into a watched SharePoint library. Nothing else is required to start the workflow. The pipeline is already listening for new files.
2.The pipeline picks it up
TurboDocx detects the new file, reads it, and places the signature and data fields using the rules an administrator defined in the wizard. No one has to open the document or prepare it by hand.
3.Signer details resolve from the legacy ERP
A Cloud connector running inside the network looks up the correct signer for that document from the back-office system of record, then returns the details over outbound HTTPS. No inbound firewall access is opened.
4.The document goes out for signature
The signer receives a professional request with a clean document name and message, not a raw system filename. They open the link and sign from any device, including a phone in the field.
5.Signed document and audit trail return to SharePoint
The completed file and its audit trail come back as a single ZIP to the destination library, and a customizable completion email confirms it. The right team is notified per store or destination.
6.The source file moves to Sent
After submission, the original file relocates to a Sent folder, so the intake library only ever shows what still needs to go out. The queue stays clean on its own.
The full walkthrough of the wizard, from connecting a source library to choosing signers and a destination, is in the docs for Creating an E-Signature Pipeline.
Reaching the legacy ERP without opening the firewall
The part that used to require a custom project is the signer lookup, and it is handled by a Cloud connector. The connector runs inside the customer network, next to the systems it needs to read. It makes only outbound HTTPS calls to TurboDocx, so there is no inbound firewall access to grant and no public endpoint to expose. Security keeps its boundary intact, and the ERP data stays in place.
When a pipeline needs a signer, the connector resolves the details from the private system of record and hands them back to the workflow. From the operations team point of view, the signer simply appears on the right document, and the mechanism behind it is one setting configured during onboarding rather than a service they have to run.
Everything an administrator sets in the wizard
Each of these is a configuration choice, not a coding task. Together they turn a raw file drop into a polished, monitored workflow:
Started and monitored from the field
Because intake is just a file landing in SharePoint, the workflow begins with an action anyone can take from a tablet. A field user saves the agreement, and the pipeline takes over. The same user can watch progress from the same device, since the source library shows only what is still pending and the Sent folder shows what has gone out.
That is the quiet payoff of moving the source file to Sent after submission. The intake queue never fills up with things that are already handled, so the view from the field stays honest. Per-destination notifications close the loop: the right store or team hears about a success or a failure without anyone watching a dashboard.
The tailored suit without the tailor price
A workflow that spans SharePoint, a firewalled legacy ERP, e-signature, and a field-facing tablet used to be the definition of a bespoke integration. It is exactly the kind of project that gets quoted in months and staffed with engineers who then have to maintain it. The tailored fit was real, and so was the tailor price.
Pipelines change the economics because the tailoring happens in configuration. TurboDocx professional services connects the source library, stands up the Cloud connector, and sets the extraction, routing, signer, and destination rules. The customer gets a workflow shaped to their systems and their process, without a custom codebase to own. If you are weighing this against building it yourself, our breakdown of how long it takes to build an e-signature app is a useful reality check, and the no-code e-signature stack shows the same philosophy applied to a smaller footprint.
The signing itself is powered by TurboSign, so every completed document carries the audit trail teams need for compliance. For the wider picture of what these workflows replace, see our complete guide to document automation.
Frequently asked questions
What is a document workflow automation pipeline?
A document workflow automation pipeline is a configured path that moves a document from intake to signed delivery without manual steps. TurboDocx Pipelines watch a source location, resolve signer details, place signature fields, send for e-signature, and return the signed file and audit trail to the destination you choose.
How does TurboDocx pick up documents from SharePoint?
A pipeline watches a SharePoint library you nominate during setup. When a new file lands in that library, TurboDocx picks it up automatically, runs it through the pipeline, and delivers the signed result back to SharePoint. After submission, the source file moves to a Sent folder so intake shows only what still needs sending.
Can a pipeline resolve signer details from a legacy ERP without opening a firewall?
Yes. A Cloud connector runs inside your network and makes only outbound HTTPS calls to TurboDocx, so no inbound firewall access is required. It looks up signer details from a private or legacy system, such as a back-office ERP, and returns them to the pipeline while your data stays in place.
What gets delivered when a document is signed?
When signing completes, the pipeline delivers the signed document and its audit trail as a single ZIP to your chosen destination, and sends a customizable completion email. You control the email subject and body, the signer-facing document name and message, and which team is notified for each store or destination.
Do I need to write code to build a pipeline?
No. TurboDocx Pipelines are configured in a wizard, not in code. An administrator connects the source library, sets field extraction and routing, chooses signers and a signed-document destination, and turns the pipeline on. TurboDocx professional services can set up the connectors and rules for you during onboarding.
Related Resources
TurboSign E-Signature →
The signing engine behind every pipeline, with a full audit trail.
Bulk Signature Sending Guide →
Send and track agreements at scale across teams and locations.
TurboDocx for IT Teams →
Automate document workflows across the systems IT already runs.
TurboDocx Templating →
Generate the documents that feed your pipelines from templates.
MSP Documentation Automation →
The same pipeline pattern applied to managed-services operations.
TurboDocx for Sales Teams →
Route contracts and proposals to signature without manual steps.
Wire your own document workflow
Tell us the systems you run and the outcome you need. TurboDocx professional services builds the pipeline, connectors and all, so your team drops a file and gets a signed one back.