How can I view and download files using the move-binary-data node in n8n v0.168.2?

When you see just the text “binary data” in the output, it means that n8n is indicating the presence of binary data rather than showing its contents. In the n8n UI, binary fields aren’t automatically rendered as the file’s actual text. To properly view and download your file, you need to convert your workflow’s payload into a true file output.

Here are some adjustments you can make:

1. Convert Your Formatted Text to a File
   Instead of (or after) using the Move Binary Data node, you should pass your formatted (custom-delimited) text data into the Convert to File node. This node takes the incoming data (for example, the text generated from your table) and converts it into a proper binary file format.

2. Write the File to Disk
   After converting to a file, use the Read/Write Files from Disk node to save the generated file. This ensures that you’re working with a file that is actually stored on your machine (or in your Docker container) and can be downloaded.

3. Ensure the Correct Field Names
   Double-check that the newly created binary file is stored in the expected field (typically “data” or a custom field you’ve defined). If you’re using the Move Binary Data node to rearrange fields, it must be configured to move the binary content from the field where it was created (by Convert to File) into the field that the file-saving node uses.

Here’s an example workflow sequence that might address your issue:

• Custom Data Extraction & Formatting: Use a function or set nodes to extract your table data and format it with your custom delimiters.
• Convert to File: Pass that text (for example, from a Set node) into the Convert to File node. Configure this node so that the output binary field (by default, “data”) contains the file content.
• Move Binary Data (Optional): If you need to change the field name or reposition the binary data, use the Move Binary Data node. Make sure that after the move, the binary file remains in the field that your next node expects.
• Read/Write Files from Disk: Finally, write the binary file to disk. To verify its content, you can then use the same node to read the file or download it from your storage path.

By converting your text to a proper file and then writing it to disk, you’ll be able to download and view its actual contents rather than just seeing “binary data” as a placeholder.

If you need further assistance tweaking node parameters (like setting the correct file name/path in the Read/Write Files node), feel free to ask!