Back to Catalog
Simon

Simon

I am an E-commerce entrepreneur specializing in spare parts, with a strong passion for automation and AI. I'm dedicated to continuously improving workflow processes, particularly in the e-commerce sector.

Total Views16,908
Templates3

Templates by Simon

Automatic background removal for images in Google Drive

This n8n workflow simplifies the process of removing backgrounds from images stored in Google Drive. By leveraging the PhotoRoom API, this template enables automatic background removal, padding adjustments, and output formatting, all while storing the updated images back in a designated Google Drive folder. This workflow is very useful for companies or individuals that are spending a lot of time into removing the background from product images. How it Works The workflow begins with a Google Drive Trigger node that monitors a specific folder for new image uploads. Upon detecting a new image, the workflow downloads the file and extracts essential metadata, such as the file size. Configurations are set for background color, padding, output size, and more, which are all customizable to match specific requirements. The PhotoRoom API is called to process the image by removing its background and adding padding based on the settings. The processed image is saved back to Google Drive in the specified output folder with an updated name indicating the background has been removed. Requirements PhotoRoom API Key Google Drive API Access Customizing the Workflow Easily adjust the background color, padding, and output size using the configuration node. Modify the output folder path in Google Drive or replace Google Drive with another storage service if needed. For advanced use cases, integrate further image processing steps, such as adding captions or analyzing content using AI.

SimonBy Simon
14344

Reusable subworkflow zip multiple files dynamically (compress)

πŸ“¦ 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 fileName in 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! πŸ’‘

SimonBy Simon
1653

Automatically correct wrong shipping addresses in Billbee orders

Address Validation Workflow About This workflow automates the process of validating and correcting client shipping addresses in Billbee, ensuring accurate delivery information. It's ideal for e-commerce businesses looking to save time and reduce errors in their order fulfillment process. The workflow uses Billbee, an order management platform for small to medium-sized online retailers, and the Endereco API for address validation. Who Is This For? E-Commerce Businesses: Streamline order fulfillment by automatically correcting common shipping address errors. Warehouse Teams: Reduce manual work and ensure packages are shipped to the correct address. Small to Medium-Sized Retailers: Businesses using Billbee to manage orders and requiring efficient, automated solutions for address validation. How it Works Trigger: Workflow starts via a Billbee Webhook when an order is imported. Fetch Data: Retrieve the client's shipping address using the Order ID. Validate Address: Send the address to the Endereco API for validation and correction (e.g., house number errors). Conditional Actions: Valid Address: Update the address in Billbee. Invalid Address: Tag the order with "Validation Error." Track Status: Add tags in Billbee for processed orders. Setup Steps API Keys: Obtain Billbee Developer/User API Keys and Endereco API Key. Billbee Rule: Create an automation rule: Trigger: Order imported. Action: Call External URL with OrderId to trigger n8n workflow. Optional: Use a secondary trigger (e.g., order state changes to "gepackt") for manual corrections. Customization Options Filter Delivery Addresses: Customize filters to exclude specific delivery types, such as pickup shops ("Postfiliale," "Paketshop," or "Packstation"). Filters can be adjusted within Billbee or in the workflow. Error Handling: Configure additional actions for orders that fail validation, such as notifying your team or flagging orders for manual review. Order Tags: Define custom tags in Billbee to better track order statuses (e.g., "Address Corrected," "Validation Error"). Trigger Types: Use additional triggers such as changes to order states (e.g., "gepackt" or "In Fulfillment") for manual corrections or validations. Address Fields: Modify the workflow to focus on specific address components, such as postal codes, city names, or country codes. Validation Rules: Adjust Endereco API settings or add custom logic to refine validation criteria based on your business needs. API Documentation Endereco: Endereco API Docs Billbee: Billbee API Docs

SimonBy Simon
911
All templates loaded