DocumentsPlumsail Documents Processes can now generate more than one document at a time. With the new Document sets feature, you can add multiple templates to the same Process, use different template formats, and generate the entire set from the same data in a single run.
To see how it works, we'll build a sales proposal package containing a project proposal, pricing spreadsheet, and presentation. We'll use the same client and project data across all three templates and make the presentation conditional, so it's only generated when it's actually needed.
Instead of maintaining a separate Process for each document, we'll keep the whole proposal package together and generate it in one run.
Further in the article:
A Document set is a collection of multiple templates within a single Plumsail Documents Process. All templates in the set can be generated together from the same input data in a single Process run.
The templates don't have to use the same format. You can combine DOCX, XLSX, PPTX, fillable PDF, and HTML templates in one Process and configure each template separately, including its output format, file name, and conditions for when it should be generated.
For our sales proposal package, we'll use three templates:
All three documents will use the same client and project data, but each template will use it differently.
Let's start by creating a Process and adding the three templates that make up our proposal package.
We'll start with the main project proposal. It contains the client name, project overview, scope of work, timeline, and total investment.
The template uses tokens such as:
{{clientName}}
{{projectName}}
{{projectSummary}}
{{duration}}
{{total}}It also uses the services collection to populate the scope of work table.
Open the template settings and configure:
{{clientName}} - Project proposal — the {{clientName}} token makes the file name dynamic, for example Contoso - Project proposal.pdfWe use a DOCX template because it's convenient to design and edit in Word, while the final proposal will be generated as a PDF.
Instead of creating another Process for the pricing spreadsheet, we'll add it to the same Document set.
Configure:
{{clientName}} - Pricing breakdown
The spreadsheet contains the same client and project information as the proposal, but uses the services collection to create a detailed pricing table with quantities, rates, and amounts.
The XLSX template also contains the {{presentationRequired}} token. We'll use this value later to decide whether the PowerPoint presentation should be generated.
The {{presentationRequired}} token can be kept on a separate data sheet so it doesn't appear in the customer-facing pricing table.
Finally, add the PowerPoint presentation to the same Process.
Open the template settings and configure:
{{clientName}} - Proposal presentationThe presentation is not needed for every sales opportunity, so we use the presentationRequired token to control whether this template should run. When its value is TRUE, Plumsail Documents Process generates the PowerPoint presentation along with the other documents in the set. If it is FALSE, the presentation is skipped.
At this point, our Sales proposal package contains three templates in three different formats: a Word proposal, an Excel pricing breakdown, and a conditional PowerPoint presentation. All three remain independently configurable while being part of the same Process.
Before adding a delivery, open Process settings and make sure Output files is set to Separate files.
This keeps the generated documents as separate files, ready to attach to the Outlook email we'll configure next. If needed, you can also combine the generated documents into a single PDF or package them into a ZIP archive.
We'll use Outlook to send the complete proposal package by email. Since the Process output is set to Separate files, the generated PDF, Excel spreadsheet, and PowerPoint presentation can all be attached to the same message.
Tokens can be used in Outlook recipients, subject lines, and email bodies, so the delivery can use the same Process data as the document templates.
Now that the templates, Process output, and Outlook delivery are configured, let's run the complete Process using sample JSON data.
Plumsail Documents Processes can be started in several ways, including web forms, CSV or Excel files, custom JSON, Power Automate, Make, Zapier, and REST API. For this example, we'll submit JSON directly so we can clearly see the single data object used to generate the entire Document set.
{
"clientName": "Contoso",
"clientContact": "Alex Morgan",
"projectName": "Customer onboarding automation",
"proposalDate": "2026-09-09T00:00:00",
"validUntil": "2026-10-09T00:00:00",
"projectSummary": "Design and implement an automated customer onboarding workflow that reduces manual handoffs, standardizes document collection, and gives the team a clear view of onboarding progress.",
"startDate": "2026-10-19T00:00:00",
"duration": "8 weeks",
"presentationRequired": true,
"services": [
{
"name": "Discovery and workflow design",
"shortDescription": "Workflow analysis and solution design",
"description": "Review the current onboarding process, map requirements, and design the future workflow.",
"quantity": 1,
"rate": 3500,
"amount": 3500
},
{
"name": "Implementation",
"shortDescription": "Workflow configuration and integration",
"description": "Configure the onboarding workflow, integrations, document generation, and testing.",
"quantity": 1,
"rate": 12000,
"amount": 12000
},
{
"name": "Training and handover",
"shortDescription": "Team training and documentation",
"description": "Train the customer team and provide implementation documentation.",
"quantity": 1,
"rate": 3000,
"amount": 3000
}
],
"total": 18500
}
The same input is used across all three templates. For example, clientName appears in the proposal, pricing spreadsheet, and presentation, while each template uses only the fields it needs.
Since presentationRequired is set to TRUE, the conditional PowerPoint template is generated as well.
The Process generates:
The Outlook delivery then sends all three files as attachments in a single email:
With one Process run, we've generated three documents in different formats from the same data and delivered them together by email.
To see the template condition in action, change:
"presentationRequired": trueto:
"presentationRequired": falseand run the Process again.
This time, the PowerPoint template is skipped. The Outlook email contains only:
The Process itself stays the same. Only the documents that meet the configured conditions are generated and delivered.
A sales proposal is just one example. Document sets work well whenever the same business event needs to produce several related documents.
| Scenario | Possible Document set |
|---|---|
| Employee onboarding | Employment agreement + onboarding checklist + training presentation |
| Project kickoff | Project plan + budget spreadsheet + kickoff deck |
| Customer reporting | Written report + detailed Excel data + presentation |
| Procurement | Proposal + pricing workbook + supporting documents |
With Plumsail Documents, you can keep related templates in one Process and generate them from the same data.
Start a free trial and try Document sets with your own templates.
DocumentsDocumentsSharePoint
Power AutomateLearn how to generate PDF invoices with EPC QR Codes (Girocode) and Swiss QR Bills automatically from Word templates using data from SharePoint, CRM, ERP, and other business systems.
Documents
FormsMicrosoft 365SharePointPower AutomateI tested four ways to generate documents in SharePoint and compared their setup, features, limitations, pricing, and best use cases.
DocumentsSharePointPower AutomateLearn how to export multiple SharePoint list items to one Word or PDF document with Power Automate, including repeating table rows and images.
