PDF
Template Input
Loads a Word (.docx) template and lists the <<tag>> placeholders it holds — in the body, headers and footers — one row per tag.
When to use it
Use it at the start of a mail-merge branch: letters, certificates, report cards or invoices filled in from rows, one document per row.
In a pipeline
Template InputTemplate MergePDF GeneratorExport PDF
Settings
| Setting | Type | Required | Default or hint |
|---|---|---|---|
| Template (.docx) | select | Yes | Upload a .docx template |
Example
Detecting the tags in an offer letter template
- Template (.docx)=offer-letter.docx
| Where | Text in the document |
|---|---|
| Body | Dear <<Candidate_Name>>, |
| Body | Start date: <<Start_Date>> |
| Header | <<Company_Name>> |
| Tag | Placeholder | Found In | Template |
|---|---|---|---|
| Candidate_Name | <<Candidate_Name>> | Body | offer-letter.docx |
| Start_Date | <<Start_Date>> | Body | offer-letter.docx |
| Company_Name | <<Company_Name>> | Header | offer-letter.docx |
Connect this node to the Template pin of Template Merge; the rows to merge go to its Data pin.
Worth knowing
- Type tags straight into Word as <<Name>>. A tag may mix formatting (for example a bold name) and still be found.
- Name each tag after a column of your data; matching ignores case and surrounding spaces.
- Inside a Loop over a folder of .docx files, the current file is used as the template instead of the upload.