n8n Workflow: Convert JSON Objects to Base64 Strings with File Processing

This n8n workflow demonstrates how to process JSON data, convert it into a Base64 encoded string, and then extract it back from a Base64 encoded file. It's a useful pattern for handling binary data within JSON structures or for secure data transfer.

Description

This workflow provides a clear example of how to manipulate data using n8n's core nodes. It starts with a simple JSON object, encodes it into a Base64 string, encapsulates it as a file, and then reverses the process to extract the original JSON object. This can be adapted for various use cases involving data serialization, de-serialization, or handling binary content.

What it does

1. Manual Trigger: Initiates the workflow manually for testing and demonstration purposes.
2. Edit Fields (Set): Defines an initial JSON object with a data field containing a simple string. This node also sets a fileName field for the subsequent file operations.
3. Convert to File: Takes the JSON object from the previous step and converts it into a Base64 encoded string, storing it as a binary file. The fileName field is used to name this binary file.
4. Extract from File: Decodes the Base64 file created in the previous step and extracts its content, making the original JSON object available again in the workflow.

Prerequisites/Requirements

• An n8n instance (self-hosted or cloud).
• No external API keys or credentials are required as this workflow uses only core n8n nodes.

Setup/Usage

1. Import the workflow:
   • Copy the provided JSON code.
   • In your n8n instance, go to "Workflows" and click "New".
   • Click the three dots next to the workflow name and select "Import from JSON".
   • Paste the JSON code and click "Import".
2. Execute the workflow:
   • Click the "Execute Workflow" button on the "Manual Trigger" node.
   • Observe the output of each node to see the data transformation steps:
     • "Edit Fields" will show the initial JSON object.
     • "Convert to File" will show the binary data (Base64 encoded string) as a file.
     • "Extract from File" will show the re-extracted, original JSON object.
3. Customize:
   • Modify the JSON data in the "Edit Fields" node to experiment with different input data.
   • Integrate this pattern into larger workflows where you need to encode or decode data for storage, transmission, or processing.