Template Nodes
Template Nodes are the primary action node in the Workflow Builder. They take data from upstream nodes and stamp a PDF template, producing a filled document.
Configuration
When you add a Template Node and click to configure it:
1. Select a Template
Choose from your available templates. The dropdown shows all templates accessible to you (owned or shared via your organization).
2. Map Data Fields
The node displays all dynamic fields from the selected template. For each field, you map an upstream data path:
event.tenant_name → TO_TenameName
event.address → RentalUnitAddress
event.amount → OweMeAmount
The left side references the incoming data (from a Webhook Trigger or an upstream data node). The right side is the template's column name.
3. Output
The Template Node produces:
- A filled PDF binary (for downstream email or storage nodes).
- Status metadata (success/failure, filename, field count).
Data Flow
Template Nodes receive data from their upstream connections. The most common pattern is:
You can also chain data transformation nodes before the Template Node:
Handling Multiple Templates
You can stamp multiple templates from the same webhook event by adding multiple Template Nodes:
Each Template Node operates independently and can map different fields from the same event payload.
Error Handling
If a Template Node fails (e.g., a required field is missing or the template is unavailable):
- The node's status changes to Error.
- An error message describes the issue.
- Downstream nodes are not executed.
- The workflow continues processing other branches (if any).
Ensure all dynamic fields have valid mappings before activating the workflow. Missing mappings will result in blank fields in the generated PDF, which may not be acceptable for official documents.