n8n Workflow Duplicates Email Body When Multiple Gmail Items Are Processed

Below is a list of possible causes and workarounds to help resolve the behavior where the draft emails all have the first item’s email body when processing multiple items:

---

1. Check for Static vs. Dynamic Values

Ensure that the Message field (and any other dynamic fields like Subject) in the Create Draft node are set up to read from each item’s input via expressions. If you have a static (hard-coded) value, that value will be reused for all items. For example, use an expression like:

JSCopied
{{$json["emailBody"]}}

This way, each item is guaranteed to use its own email body value rather than retaining a value from the first run.

---

2. Confirm Expression Evaluation Mode

When multiple items are processed, n8n evaluates expressions for each item in the workflow. If your expression isn’t correctly referencing the data (for example, due to a typo or referencing a field that isn’t present in subsequent items), the node might fall back to a default value. Double-check that every dynamic parameter (especially the Message field) references the correct field in your input data.

---

3. Process Items Individually

If you suspect that the node is “caching” the first item’s parameters across all items:

• Consider splitting the workflow so that each item is processed individually before using the Create Draft node.
• You can use a SplitInBatches or Item Lists node so that the Create Draft node runs per item, ensuring its own unique data is used for each draft creation.

---

4. Review Node Configuration and Workflow Structure

Sometimes unexpected behavior can occur if there’s a mix of static and dynamic parameters:

• Double-check the node’s options and ensure no option has a default value overriding your dynamic setting.
• Use a Set node to explicitly define the parameters you wish to pass (e.g., setting separate fields for subject and message) from each item, then pass that structured data into your Create Draft node.

---

5. Check for Known Issues

Since you are using n8n version 1.74.1, it may be worth checking the community forum or issue list for any known bugs related to the Gmail node’s Create Draft operation when processing multiple items. Sometimes, updating to a newer version where multi-item processing issues have been resolved can also help.

---

Summary

This behavior is most likely due to the node using a static or improperly referenced value for the Message field when processing multiple items. Remediate by:

• Verifying that fields like Message use expressions that reference each item’s data.
• Confirming that your workflow processes each item’s data individually.
• Reviewing any potential caching behavior in your current setup.

By ensuring that each item's unique input is correctly passed into the node (either by using proper expressions or handling items individually), you should be able to have each draft email reflect its correct email body.

Let me know if you have further questions about setting up these parameters or handling multi-item workflows with the Gmail node.