Reusable Subworkflow Zip Multiple Files Dynamically (Compress)
Published 12 days ago
Created by
Simon
Categories
Template description
π¦ Zip Multiple Files Dynamically
This template enables you to dynamically bundle multiple files into a ZIP archive. Designed to be used as a Subworkflow, itβs modular, flexible, and easy to integrate into various workflows. The output is a single ZIP file with a name that includes the current date, time, and fileName.
Shoutout:
Code from: Tom (mutedjam)
π€ Who is this for?
This workflow is perfect for:
- π Businesses automating file archiving tasks.
- π» Developers managing files programmatically.
- π Anyone needing a reusable solution for bundling files into ZIP archives.
β What problem is this workflow solving?
Manually zipping multiple files is:
- π Time-consuming.
- π€ Prone to errors.
This workflow automates the process and, as a Subworkflow, ensures:
- β‘ Consistent file archiving across different workflows.
- π οΈ Reduced manual effort.
- π Streamlined integration into existing automation.
π§ What this workflow does
- ποΈ Dynamically collects binary files from the input.
- π¦ Bundles them into a single ZIP archive.
- π Names the ZIP file with the current date, time, and a customizable
fileName. - β Outputs the ZIP file, ready for storage or further processing.
βοΈ Setup
- π Add this Subworkflow to your existing workflows.
- π₯ Pass the binary files as input to the Subworkflow.
- βΆοΈ Call the Subworkflow to generate a ZIP file.
π οΈ How to customize this workflow to your needs
- π File Sources: Adjust the input nodes in your parent workflow to connect to your preferred file sources.
- π File Naming: Customize the logic for the output
fileNamein the Subworkflow. - π Additional Use Cases: Use this Subworkflow in various scenarios, such as:
- βοΈ Sending ZIP files via email.
- βοΈ Uploading ZIP files to cloud storage.
- π Triggering further automation.
π Why use this as a Subworkflow?
Instead of building a fixed ZIP functionality for every workflow, this template offers a reusable solution that can be integrated into many different workflows effortlessly. Save time and ensure consistency across your automation projects! π‘
Share Template
More Building Blocks workflow templates
Creating an API endpoint
Task:
Create a simple API endpoint using the Webhook and Respond to Webhook nodes
Why:
You can prototype or replace a backend process with a single workflow
Main use cases:
Replace backend logic with a workflow
Jonathan
Very quick quickstart
Want to learn the basics of n8n? Our comprehensive quick quickstart tutorial is here to guide you through the basics of n8n, step by step.
Designed with beginners in mind, this tutorial provides a hands-on approach to learning n8n's basic functionalities.
Deborah
Pulling data from services that n8n doesnβt have a pre-built integration for
You still can use the app in a workflow even if we donβt have a node for that or the existing operation for that. With the HTTP Request node, it is possible to call any API point and use the incoming data in your workflow
Main use cases:
Connect with apps and services that n8n doesnβt have integration with
Web scraping
How it works
This workflow can be divided into three branches, each serving a distinct purpose:
1.Splitting into Items (HTTP Request - Get Mock Albums):
The workflow initiates with a manual trigger (On clicking 'execute').
It performs an HTTP request to retrieve mock albums data from "https://jsonplaceholder.typicode.com/albums."
The obtained data is split into items using the Item Lists node, facilitating easier management.
2.Data Scraping (HTTP Request - Get Wikipedia Page and HTML Extract):
Another branch of the workflow involves fetching a random Wikipedia page using an HTTP request to "https://en.wikipedia.org/wiki/Special:Random."
The HTML Extract node extracts the article title from the fetched Wikipedia page.
3.Handling Pagination (The final branch deals with handling pagination for a GitHub API request):
It sends an HTTP request to "https://api.github.com/users/that-one-tom/starred," with parameters like the page number and items per page dynamically set by the Set node.
The workflow uses conditions (If - Are we finished?) to check if there are more pages to retrieve and increments the page number accordingly (Set - Increment Page).
This process repeats until all pages are fetched, allowing for comprehensive data retrieval.
Jonathan
Joining different datasets
Task:
Merge two datasets into one based on matching rules
Why:
A powerful capability of n8n is to easily branch out the workflow in order to process different datasets. Even more powerful is the ability to join them back together with SQL-like joining logic.
Main use cases:
Appending data sets
Keep only new items
Keep only existing items
Jonathan
+11
Back Up Your n8n Workflows To Github
This workflow will backup your workflows to Github. It uses the public api to export all of the workflow data using the n8n node.
It then loops over the data checks in Github to see if a file exists that uses the workflow name. Once checked it will then update the file on Github if it exists, Create a new file if it doesn't exist and if it's the same it will ignore the file.
Config Options
repo_owner - Github owner
repo_name - Github repository name
repo_path - Path within the Github repository
>This workflow has been updated to use the n8n node and the code node so requires at least version 0.198.0 of n8n
Jonathan
+10
Building Your First WhatsApp Chatbot
This n8n template builds a simple WhatsApp chabot acting as a Sales Agent. The Agent is backed by a product catalog vector store to better answer user's questions.
This template is intended to help introduce n8n users interested in building with WhatsApp.
How it works
This template is in 2 parts: creating the product catalog vector store and building the WhatsApp AI chatbot.
A product brochure is imported via HTTP request node and its text contents extracted.
The text contents are then uploaded to the in-memory vector store to build a knowledgebase for the chatbot.
A WhatsApp trigger is used to capture messages from customers where non-text messages are filtered out.
The customer's message is sent to the AI Agent which queries the product catalogue using the vector store tool.
The Agent's response is sent back to the user via the WhatsApp node.
How to use
Once you've setup and configured your WhatsApp account and credentials
First, populate the vector store by clicking the "Test Workflow" button.
Next, activate the workflow to enable the WhatsApp chatbot.
Message your designated WhatsApp number and you should receive a message from the AI sales agent.
Tweak datasource and behaviour as required.
Requirements
WhatsApp Business Account
OpenAI for LLM
Customising this workflow
Upgrade the vector store to Qdrant for persistance and production use-cases.
Handle different WhatsApp message types for a more rich and engaging experience for customers.
Jimleuk
