Skip to main content
Merge node card with its required inputs and template edit button

​
What is the Merge node for?

The Merge node (or Merge with Template) acts as a templating engine within Draft & Goal. It lets you combine fixed text with dynamic variables (from previous steps) to produce a single, structured output. Main use cases:
  • Prepare and structure a complex prompt for an LLM.
  • Build a properly formatted JSON object to send data to external tools (e.g. Google Sheets).
  • Define reusable global “sub-prompts” (e.g. a persona, editorial guidelines) used in multiple places in your workflow.
  • Concatenate several text inputs into one coherent block.

​
Quick setup

Here’s how to add and configure the Merge node in your workspace. You’ll find it in the node library under Tools.
1

Add the node

Drag and drop the Merge (or Merge with Template) node from the library onto your workspace.
2

Edit the template

Click the pencil icon (Edit template) on the node card. A window opens where you write your content.
3

Insert variables

Write your text and insert dynamic variables using double curly braces, e.g. {{myVariable}}.
4

Connect inputs

Once the template is saved, the node will show the variables you created as input fields. Connect the outputs from your previous nodes to these inputs.
Merge template edit window showing an example prompt with dynamic variables
Need inspiration or help formatting complex JSON? Use the Select an example dropdown at the top right of the edit window to load pre-configured templates (e.g. JSON for Google Sheets, multi-line text, etc.).

​
Configuration fields

The Merge node is designed to be both simple and highly flexible.
Merge node settings panel showing ID, Name, Description and display options

​
Main fields

​
Name
string
required
The name of your node. You should rename this field (e.g. “Merge - SEO Prompt” instead of “Merge”) so you can easily tell what it does when running the workflow.
​
Description
string
required
A short description of what this merge is for. Especially useful when collaborating or when you need to remember the intended structure.

​
Template parameters

​
Template Editor
text/code
required
Accessed via the Edit template button, this is the plain-text area where you write your structure (text, Markdown, HTML, or JSON) and place your {{variables}}.
​
Input Variables
dynamic
required
These fields appear dynamically on the node card based on the {{}} placeholders you defined in your template. You must connect incoming data to them.

​
What does the node output?

The Merge node returns exactly the text and format you defined, with variables replaced by their actual values. The format is unchanged: a template written in HTML outputs HTML, a JSON template stays valid JSON (as long as the injected variables don’t break the syntax).
​
Merged content
string
required
The final text from combining your fixed template with the evaluated dynamic data.
Draft & Goal behavior: You don’t need to remember the Merge node’s ID to use its output. Just connect the Merge’s output to the next node’s input and map that connection to the variable you want in that node.
Execution screen showing the final merge result with variables replaced by the actual text

​
Example usage

The Merge node fits many scenarios. One of the most common is preparing a full prompt for an AI.
In the Edit template window, write the following structure with your target variables:
Template
AI Prompt : 

Role : {{role}}

Objective : {{objective}}

Constraints : {{constraints}}

Format : {{format}}

​
Best practices and pitfalls

To keep workflows readable and reliable, follow these guidelines:
Best practices
  • Use it often: Whenever you need to combine multiple pieces of data, the Merge node is the most reliable and flexible option.
  • Store global information: Use a Merge node at the start of your workflow to hold a “pre-prompt” or global instructions, and connect it to all AI agents that need it.
  • Use the built-in templates: For complex JSON (e.g. for Google Sheets), start from the examples in the Select an example menu.

​
Common issues and solutions

Issue: You’re using Merge to format JSON (e.g. to send to Google Sheets), but the destination node reports a parsing error.Solution: Check the syntax in the template editor.
  1. Make sure your {{variables}} are in the right place.
  2. JSON quotes and braces must be correct.
  3. If the content injected via a variable contains unescaped quotes or invisible line breaks, it can break the JSON structure.
Issue: The final text shows {{myVariable}} literally instead of the expected data.Solution: Check that you’ve connected an input to the field on the Merge card. If the input is empty or not connected, the system can’t inject the data.
Issue: You have several “Merge” nodes in the logs and can’t tell which one holds which information.Solution:
Always rename your nodes.
Open the settings for each Merge node and set Name to something descriptive, e.g. “Merge - Google Sheet row format”.

​
How it fits in a workflow

The Merge node is a “pivot” node that often sits between data extraction/generation and the final action. Typical pattern (workflow with proofreading): Here, the same pre-prompt is shared with both the writer and the proofreader so that the initial constraints are followed from start to finish.
The Merge node is rarely used alone. It sets things up for AI or data-integration nodes.

LLM

Generate high-quality text using the content structured by your Merge node as the input prompt.

Google Sheets

Send properly formatted JSON from your Merge straight to your spreadsheet cells.

Text Input

Manually enter base variables that will feed your dynamic template.

AI Agent

Give your autonomous agents solid context and clear instructions with a preparatory merge.