Overview
This node allows you to attach binary data (such as files) from the output of another node in your workflow to the current node's input items. It is useful when you want to reuse or combine binary data processed or generated by a previous node without re-uploading or re-fetching it.
Common scenarios include:
- Attaching images, documents, or other files that were downloaded or created earlier in the workflow.
- Combining binary data from multiple sources into one item for further processing.
- Passing along binary attachments between nodes while transforming or enriching the data.
For example, if you have a node that downloads images and another node that processes text data, you can use this node to attach those downloaded images to the text items for combined handling downstream.
Properties
| Name | Meaning |
|---|---|
| From Node | The name of the node containing the items with binary data you want to attach. |
| Attach | Choose whether to attach all binaries from the source node or only selected binary fields. |
| Binary Fields | (Shown if "Selected Binaries" is chosen) Specify the names of the binary fields to attach from the source node. Multiple field names can be provided separated by commas. |
| Item Mapping | Defines which item from the source node to attach binaries from: same index as current item, first item, or a specified item index. |
| Item Index | (Shown if "Specify Item Index" is chosen) The zero-based index of the item in the source node to attach binaries from. |
Output
The node outputs the original input items enriched with binary data attached from the specified source node. The binary data is added under the binary property of each item, either attaching all binary fields or only the selected ones depending on configuration.
If the source node contains multiple binary fields, they will be merged accordingly based on the selection. This enables subsequent nodes to access the attached files directly via the standard binary data structure.
Dependencies
- Requires that the referenced source node exists and has executed before this node runs.
- No external API keys or services are needed; it operates entirely within the workflow context.
- Proper naming of the source node is essential to correctly reference its output.
Troubleshooting
Issue: No binary data appears after execution.
- Cause: The specified source node name may be incorrect or does not contain any binary data.
- Solution: Verify the exact name of the source node and ensure it outputs binary data.
Issue: Error due to invalid item index.
- Cause: Specified item index exceeds the number of items in the source node.
- Solution: Adjust the item index to a valid range or use "Same as Current Item" or "First Item" options.
Issue: Selected binary fields do not attach.
- Cause: Field names may be misspelled or do not exist in the source node's binary data.
- Solution: Double-check the binary field names in the source node output.
Links and References
- n8n Documentation: Working with Binary Data
- n8n Community Forum – For user questions and shared workflows involving binary data attachments