You first upload a document or scene template (for example an InDesign .indd, a Photoshop .psd, or a 3D scene asset required by a composition node).
Last updated on
Apr 20, 2026
Upload templates to create mappable ports that merge data into repeatable workflows.
Template-driven nodes, such as Merge InDesign data, Merge Photoshop data, and 3D composition workflows, turn an authored document or scene into a repeatable pipeline. You upload a template once; the workflow maps upstream data into the places your template defines.
How template nodes differ from simple inputs
These nodes are specific in how they expose input ports:
The service inspects that template and creates mappable ports that correspond to placeholders, layers, fields, or scene inputs in the file.
You connect workflow inputs—text, images, tables, or other assets—to those ports. At run time, those values are merged into the template to produce outputs.
Until the template is uploaded and successfully validated, you typically cannot see the full set of mappable parameters. Treat template upload as the prerequisite step, same as in the single-node documentation for each merge type.
Authoring templates in external applications
To use these nodes effectively, author the template in the correct application first:
- InDesign: Build layouts with Data Merge and <<field>> placeholders; see Merge InDesign data for data sources, assets, and upload steps.
- Photoshop: Mark replaceable layers with {{tag}} in text or layer names; see Merge Photoshop data for Workflow Builder tagging rules and upload steps.
- 3D composition: Prepare scene or package files according to nodes such as Composite images (3D); scene data feeds the composition after a template or scene upload step.
Save or package the file with linked assets and fonts, as required, then upload the primary template file (and bundled assets, if the node asks for them) into Workflow Builder.
Upload, map, and connect
Add the node. Place Merge InDesign data, Merge Photoshop data, or your 3D composition node on the canvas.
Upload the template. Use the node’s upload control for the document or scene. Add Assets or font uploads if validation requests them.
Wait for inspection. When validation succeeds, mappable ports and parameters appear: text fields, image slots, and other merge targets detected from the file.
Map inputs — Connect upstream nodes (generative text, input images, and so on) to each port, or set static values where the workflow should not vary.
Connect downstream — Wire the node’s outputs to previews, output nodes, or further processing, same as any other node in the graph.
Unmapped fields may fall back to defaults or values embedded in the template, depending on the node—check validation messages before publishing.
Template preparation
For field-level setup inside InDesign and Photoshop (data sources, placeholders, layer naming), use Adobe’s product guides plus Workflow Builder–specific topics:
- Data merge (InDesign user guide)
- Merge Photoshop data — {{tag}} notation, text vs image layers, and uploading to the Merge Photoshop data node
- Merge InDesign data — data sources, <<field>> placeholders, and uploading to the Merge InDesign data node
Troubleshooting
|
Symptom |
What to check |
|
Ports do not appear |
Confirm the template uploaded successfully; fix validation errors (missing fonts, broken links, unsupported features). |
|
Wrong or empty merges |
Verify each mapped port is connected or has a static value; confirm upstream nodes run before this node. |
|
Asset missing in output |
Ensure linked files were uploaded as Assets where required, and paths or field names match the template. |
Turn text into art with Adobe Firefly
Create beautiful images and video clips from text prompts using generative AI.
