Compress Binary Files to ZIP Format

This n8n workflow demonstrates how to compress binary files into a ZIP archive using the Compression node. It's a basic example that can be extended to fetch files from various sources (like cloud storage, FTP, or webhooks) and then compress them before further processing or storage.

What it does

This workflow showcases the core functionality of the Compression node:

1. Starts the workflow: Initiates the execution flow.
2. Provides example binary data: Uses a Dropbox node to simulate receiving binary file data. Note: In a real-world scenario, this would be replaced by a node that actually fetches your files.
3. Compresses the data: Takes the binary data and compresses it into a ZIP format.
4. Sends a dummy HTTP Request: Simulates sending the compressed data to an external service or API. Note: This node is a placeholder; you would configure it to send the ZIP file to your desired destination.

Prerequisites/Requirements

• n8n Instance: You need a running n8n instance to import and execute this workflow.
• Dropbox Credentials (Optional): If you intend to use the example Dropbox node as-is, you will need to configure Dropbox credentials in n8n. However, this node primarily serves as a placeholder for binary data.

Setup/Usage

1. Import the workflow:
   • Copy the provided JSON content.
   • In your n8n instance, go to "Workflows" and click "New".
   • Click the "Import from JSON" button (usually a cloud icon with an arrow pointing down) and paste the JSON.
   • Click "Import".
2. Configure the Dropbox node (if using):
   • Click on the "Dropbox" node.
   • Select or create your Dropbox API credentials.
   • Configure the operation to fetch the binary file you wish to compress.
3. Configure the Compression node:
   • The "Compression" node is pre-configured to compress the input data into a ZIP file. You can adjust settings like the output filename if needed.
4. Configure the HTTP Request node:
   • Click on the "HTTP Request" node.
   • Change the "URL" and "Method" to point to your desired API endpoint or service where you want to send the compressed ZIP file.
   • Configure any necessary headers or body parameters for your API call.
5. Activate the workflow:
   • Ensure the workflow is active by toggling the "Active" switch in the top right corner.
6. Execute the workflow:
   • You can manually test the workflow by clicking "Execute Workflow" in the editor.
   • For production use, you would typically set up a trigger node (e.g., a Webhook, Cron, or another app's trigger) to automatically run this workflow when new files are available for compression.