Workflow Templates

Temporary solution using the undocumented REST API for backups with file versioning (Nextcloud)

This workflow gets data from an API and exports it into Google Sheets and a CSV file.

Automatically adding expense receipts to Google Sheets with Telegram, Mindee API, Twilio, and n8n.

Every 10 minutes check if a new article was stared, if so, save it in wallabag to read it later.

query data from two different databases handle and unify in a single return

This n8n template helps in making informed decisions for Crypto and Stocks Trading by helping you keep track of breaking changes in the market. How it works Collects crypto and/or stock market headlines from multiple sources: CoinDesk, CoinTelegraph, Google News, and X (via an RSS proxy). Normalizes all items into a consistent structure with fields like source, kind, title, url, publishedAt, matchedKeywords, media[], and topic. Uses topic-specific keyword lists to keep relevant items and a small spam blacklist to drop giveaways / airdrops / obvious noise. Deduplicates items across runs by tracking previously seen links. Bundles everything into a compact { topic, items[] } JSON payload and sends it to your own backend or UI via HTTP. Set up steps Import the template JSON into a new n8n workflow. In the Init RunConfig code node, choose a default topic (crypto or stocks), which platforms to use (CoinDesk / CoinTelegraph / Google News / X), and optionally adjust tickers and keywords. Open the final HTTP Request - Send to your backend node and: Replace the example URL with your own API endpoint. Either set a x-webhook-secret header that your backend validates, or remove this header entirely if you don’t use it. Create any required credentials (for the webhook header auth and for HTTP requests, if needed) – the template does not contain real API keys. Enable either the Schedule Trigger for periodic runs or the Webhook trigger for on-demand runs from your app. Expect roughly 10–20 minutes to import, configure, and test the first run; detailed per-node notes are available as sticky notes inside the workflow canvas.

Who is this for? This workflow listens for new or updated WooCommerce orders, cleans and structures the order data, processes orders in batches, and standardizes WhatsApp phone numbers. It verifies phone numbers via the Rapiwa API, sends invoice links or messages to verified numbers, and logs results into separate Google Sheets tabs for verified and unverified numbers. Throttling and looping are managed using batch processing and wait delays. What this Workflow Does Receives order events (e.g., order.updated) from WooCommerce or a similar trigger. Extracts customer, billing/shipping address, product list, and invoice link from the order payload. Processes orders/items in batches for controlled throughput. Cleans and normalizes phone numbers by removing non-digit characters. Verifies whether a phone number is registered on WhatsApp using the Rapiwa API. If verified, sends a personalized message or invoice link via Rapiwa's send-message endpoint. If not verified, logs the customer as unverified in Google Sheets. Logs every send attempt (status and validity) into Google Sheets. Uses Wait nodes and batching to avoid API rate limits. Key Features Trigger-based automation (WooCommerce trigger; adaptable to Shopify webhook). Batch processing using SplitInBatches for stable throughput. Phone number cleaning using JavaScript (waNoStr.replace(/\D/g, "")). Pre-send WhatsApp verification via Rapiwa to reduce failed sends. Conditional branching (IF node) between verified and unverified flows. Personalized message templates that include product and customer fields. Logging to Google Sheets with separate flows for verified/sent and unverified/not sent. Wait node for throttling and looping control. Requirements Running n8n instance with nodes: HTTP Request, Code, SplitInBatches, IF, Google Sheets, Wait, and a WooCommerce trigger (or equivalent). Rapiwa account and Bearer token for verify/send endpoints. Google account and Google Sheets access with OAuth2 credentials. WooCommerce store access credentials (or Shopify credentials if adapting). Incoming order payloads containing billing and line_items fields. Google Sheet format (example rows) A Google Sheet formatted like this ➤ Sample | Customer Name | Phone Number | Email Address | Address | Product Title | Product ID | Size | Quantity | Total Price | Product Image | Invoice Link | Status | Validity | | -------------- | ------------- | --------------------------------------------------------------------- | ----------- | ------------------------------------ | ---------- | ---- | -------- | ----------- | ------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -------- | ---------- | | Abdul Mannan| 8801322827799 | contact@spagreen.net | mirpur| T-Shirt - XL | 110 | XL | 1 | BDT 499.00 | https://your_shop_domain/Product/gg.img | https://your_shop_domain/INV/DAS | sent | verified | | Abdul Mannan| 8801322827799 | contact@spagreen.net | mirpur| T-Shirt - XL | 110 | XL | 1 | BDT 499.00 | https://your_shop_domain/Product/gg.img | https://your_shop_domain/INV/DAS | not sent | unverified | Important Notes The Code nodes assume billing and line_items exist in the incoming payload; update mappings if your source differs. The message template references products[0]; if orders contain multiple items, update logic to summarize or iterate products. Start testing with small batches to avoid accidental mass messaging and to respect Rapiwa rate limits. Useful Links Dashboard:** https://app.rapiwa.com Official Website:** https://rapiwa.com Documentation:** https://docs.rapiwa.com Support & Help WhatsApp**: Chat on WhatsApp Discord**: SpaGreen Community Facebook Group**: SpaGreen Support Website**: https://spagreen.net Developer Portfolio**: Codecanyon SpaGreen

⚠️ Disclaimer: This workflow utilizes community nodes that needs self hosted version Code for UI Form is accessible here The bykhaisa workflow streamlines makeup service bookings by capturing customer details via webhook, calculating pricing including add-ons and payment types, generating payment invoices with Xendit, and sending personalized WhatsApp booking confirmations. This powerful combination of n8n, GoWhatsApp API, and Xendit reduces manual work and accelerates payment collection, saving you valuable time and boosting client satisfaction. 💡 Why Use bykhaisa? Save Time:** Automate booking and payment processes to eliminate hours spent on manual data entry Simplify Payments:** Generate invoices instantly with Xendit, making it easier for clients to pay securely and promptly Enhance Communication:** Send automated WhatsApp messages that keep customers informed and engaged without lifting a finger Stand Out:** Offer a modern, seamless booking experience that elevates your makeup business above competitors still stuck in the stone age ⚡ Perfect For Makeup Artists & Studios:** Who want a hassle-free booking and payment system Beauty Salons:** Seeking smooth client communication and invoicing automation Freelancers:** Looking to appear professional with automated workflows and instant payment requests General Business with booking system**: to make a seamless booking process 🔧 How It Works ⏱ Trigger: Customer sends booking details via Form (a POST request to the webhook) 📎 Process: Extract and format booking data, calculate prices with add-ons and urgent fees, and create a unique booking ID 🤖 Smart Logic: Calculate whether payment is a Down Payment (DP) or full amount, set invoice expiry, and generate Xendit invoices automatically 💌 Output: WhatsApp notification with booking details and payment link sent to customer, complete with friendly typing delays for that human touch 🗂 Storage: Booking data enriched with pricing and payment state, ready for follow-up or record-keeping 🔐 Quick Setup Import JSON file to your n8n instances Add credentials: Xendit API key, GoWhatsApp API credentials Customize: Adjust pricing logic, add-on fees, and payment types as needed Update: Replace webhook URLs and redirect URLs for payment success/failure pages Test: Run the workflow with sample booking data to verify end-to-end automation 🧩 Requirements Active n8n instances Xendit account & API credentials for invoice generation GoWhatsApp API setup for WhatsApp messaging Optional: Custom domain for webhook endpoint 🛠️ Level Up Ideas Add calendar integration to automatically block booked slots Integrate Google Sheets or Airtable for backup and reporting Set up payment reminders and follow-ups via WhatsApp automatically 🧠 Nodes Used Webhook** - Receives booking requests Set (Process Booking)** - Data transformation and formatting Code (Calculate Price)** - Custom pricing logic with add-ons HTTP Request (Generate Invoice)** - Xendit invoice creation Respond to Webhook** - Send response back to client GoWhatsApp** - WhatsApp messaging functionality 📋 Workflow Categories Category:** E-commerce, Bussiness Tags:** automation, booking, invoicing, payments, whatsapp, makeup Made by: khaisa Studio Need custom work? Contact Me

A sample demo showing how to integrate Browser Use Cloud API with N8N workflows. This template demonstrates AI-powered web research automation by collecting competitor intelligence and delivering formatted results to Slack. How It Works Form trigger accepts competitor name input Browser Use Cloud API performs automated web research Webhook processes completion status and retrieves structured data JavaScript code formats results into readable Slack message HTTP request sends final report to Slack Integration Pattern This workflow showcases key cloud API integration techniques: REST API authentication with bearer tokens Webhook-based status monitoring for long-running tasks JSON data parsing and transformation Conditional logic for processing different response states Setup Required Browser Use API key (signup at cloud.browser-use.com) Slack webhook URL Perfect demo for learning browser-use cloud API integrations and building automated research workflows.

📥 Download Slideshare and Store in Drive ⚙️ Automate the download of Slideshare presentations and save them to Google Drive using the Slideshare Downloader Pro API. 🔄 Workflow Overview: Node by Node 📝 On Form Submission → Displays a form for users to input the Slideshare URL. 🌐 Slideshare Downloader → Sends the submitted URL to the Slideshare Downloader Pro API to fetch a downloadable PDF link. ✅ If (API Success?) → Checks if the API response returns a 200 status (success). ⬇️ Download PDF → Downloads the actual PDF file from the media URL received in the API response. ☁️ Upload to Google Drive → Uploads the downloaded PDF into a specific Google Drive folder. 🔓 Google Drive Set Permission → Sets the file’s permission to "Anyone with the link can view". ⏱️ Wait (Error Handling) → Adds a small delay before logging errors to prevent rapid multiple logs. 📄 Google Sheets Append Row → Logs failed attempts with the original Slideshare URL and "N/A" for tracking. 💡 Use Case A content curator or student often downloads Slideshare presentations for archiving, referencing, or sharing. Instead of repeatedly copy-pasting URLs, downloading files, and uploading them manually, this automated workflow streamlines the process from input to storage. It leverages the Slideshare Downloader Pro API to handle the heavy lifting — ensuring reliable PDF extraction. ✅ Benefits 🕒 Save Time:** Automates multi-step tasks in one seamless flow. 📂 Organized Storage:** PDFs are directly saved in Google Drive with public access enabled. 📉 Track Failures:** Failed downloads are logged for review via Google Sheets. 🔗 Easy Sharing:** Uploaded files are made instantly accessible via shareable links. 🧩 API Integration:** Integrates smoothly with the Slideshare Downloader Pro API, ensuring robust and scalable automation. 🔑 How to Get API Key from RapidAPI Slideshare Downloader Pro Follow these steps to get your API key and start using it in your workflow: Visit the API Page 👉 Click here to open Slideshare Downloader Pro API on RapidAPI Log in or Sign Up Use your Google, GitHub, or email account to sign in. If you're new, complete a quick sign-up. Subscribe to a Pricing Plan Go to the Pricing tab on the API page. Select a plan (free or paid, depending on your needs). Click Subscribe. Access Your API Key Navigate to the Endpoints tab. Look for the X-RapidAPI-Key under Request Headers. Copy the value shown — this is your API key. Use the Key in Your Workflow In your n8n workflow (HTTP Request node), replace: "x-rapidapi-key": "your key" with: "x-rapidapi-key": "YOUR_ACTUAL_API_KEY"

I built this tool because we faced a real, recurring problem: managing hundreds of client projects in a weekly automated loop. There was a time when a single error in that process could create a complete data mess, forcing us to manually clean and re-run everything. The Item Tracker was our solution. It proved that something simple, when used correctly, can be a game-changer for maintaining order and reliability in your workflows (at least it was for us). How the System Works: A Story of Order from Chaos Our main automation, which fetches and summarizes data, is where the heavy lifting happens. But its newfound stability comes from a simple, critical collaboration with the Item Tracker. It's like a two-step handshake that happens for every single project. Our main workflow starts by getting a long list of active projects. For each project, it first asks the Item Tracker: "Is this one already being worked on?" If the answer is no, the Item Tracker immediately puts a temporary "in-progress" note on the project Once our main workflow successfully completes its task for that project, it tells the Item Tracker to remove the "in-progress" note and set a "completed" note. This simple process is our safety net. If a task fails, that "in-progress" note will eventually disappear, allowing the system to confidently pick up and re-run only that specific item later. ++This saves us from having to start the entire job over from scratch.++ Key Components & Their Purpose Main Workflow:** This is the primary automation that does the heavy lifting, like getting a list of projects and connecting to HubSpot. Item Tracker Utility:** The smart part of the system. This separate tool keeps a simple record of what each project's status is at any given moment. Redis Database:** This is the fast, central hub where all of the Item Tracker's notes are stored. It's the engine that makes the entire system reliable. The Item Tracker in Action: Your Digital To-Do List For beginners, the names of the tracking notes (called "keys") might seem confusing, but the idea is actually simple. Imagine a digital to-do list for every project. A key is just the project's name on that list. Every key has three parts that tell you everything you need to know: The Group:** The first part groups all similar items together, like all your HubSpot projects. The ID:** The middle part is the project's unique ID, so you know exactly which project you're talking about. The Status:** The last part is a simple word that shows its status, like in_progress or completed. This simple naming system is the secret to keeping hundreds of projects organized, so you can easily see what's happening and what needs attention. Overall Business Value This solution directly addresses the pain of large-scale automation failures. It gave us a new level of confidence in our automated processes. Instead of facing the chaos of a messy run, this system provides immediate visibility into which project failed and why. It eliminates the need for manual cleanup and allows us to confidently re-run a specific item without risking data corruption across the entire set. The result is a highly reliable and scalable process that saves time, reduces frustration, and maintains data integrity.

How it works This workflow runs a spider job in the background via Scrapyd, using a YAML config that defines selectors and parsing rules. When triggered, it schedules the spider with parameters (query, project ID, page limits, etc.). The workflow polls Scrapyd until the job finishes. Once complete, it fetches the output items, enriches them (parse JSONL, deduplicate, extract ID/part number/make/model/part name, normalize price), sorts results, and returns structured JSON. Optional debug outputs such as logs, HTML dumps, and screenshots are also collected. How to use Use the manual trigger for testing, or replace it with webhook, schedule, or other triggers. Adjust the runtime parameters (q, project_id, pages, etc.) directly in the workflow when running. The background spider config (YAML and spider code) must be updated separately — this workflow only orchestrates and enriches results, it does not define scraping logic. Requirements Scrapyd service for job scheduling & status tracking A deployed spider with a valid YAML config (adjust selectors there) JSON Lines output (items.jl) from the spider Endpoints for optional artifacts (logs, HTML, screenshots) n8n with HTTP, Wait, Code, and Aggregate nodes enabled Customising this workflow Update the YAML config if the target website structure changes Modify the enrichment code to extract different fields (e.g., categories, ratings) Adjust deduplication (cheapest, newest, or other logic) Toggle debug retrieval depending on performance/storage needs Extend webhook response to integrate with databases, APIs, or downstream workflows