ConvertUniverseConvertUniverse Docs

Processing

Template Fill Nodes Reference

Technical reference for `pdfFormFill` and `wordFormFill`, including field detection, mapping behavior, and output naming.

Updated 2 min read

Overview

These nodes merge structured workflow data into document templates:

  • pdfFormFill fills existing AcroForm fields in a PDF.
  • wordFormFill replaces {{placeholder}} tokens in a DOCX template and can output DOCX or PDF.

Configuration / Settings

NodeSettingTypeRequiredDetails
pdfFormFillmappingsobjectYesMaps PDF field names to expressions like {{sheet_node.email}}.
wordFormFillmappingsobjectYesMaps placeholder names to expressions.
wordFormFilloutput_formatdocx or pdfNoDefaults to docx.

Inputs Expected

  • pdfFormFill expects PDF files with interactive form fields.
  • wordFormFill expects DOCX files containing {{placeholder}} markers.
  • Both nodes are designed to pair with structured inputs such as excel, googleSheets, httpRequest, or webhook bodies.

Variables Exported / Outputs

NodeOutput shapeFilename behavior
pdfFormFillBlob[]Each result is named <original>-filled.pdf.
wordFormFillBlob[]Each result is named <original>-filled.docx or .pdf.

Common Use Cases

  • Fill onboarding packets from spreadsheet rows.
  • Merge JSON from a webhook into a Word template and return a final PDF.
  • Loop over many records and generate one filled document per row.

Edge Cases

  • pdfFormFill throws when no PDF file is received or when the fill API is unavailable.
  • wordFormFill has multiple fallback paths to recover files from blobs, file IDs, loop payloads, and upstream graph context.
  • Auto-detection only helps map fields. It does not guarantee that every placeholder or form field has a value at runtime.