by Sk developer
📞 Phone Number Validator with Google Sheets Validate and enrich phone numbers from Google Sheets using the phone number validator API. 📌 Use Case: Contact Validation & Enrichment Automatically check if phone numbers are valid and enrich them with metadata (country, location, timezone). Ideal for CRMs, lead management, and contact cleanup workflows. 🗂️ Google Sheets Columns | Column Name | Description | |-------------|-------------| | phone | The original phone number to validate (input column). | | is_valid | Result from API indicating if the phone number is valid (true / false). | | country | Country where the phone number is registered (e.g. "US"). | | location | More specific location info, such as city or region. | | timezone | The primary timezone associated with the phone number. | 🎯 Benefits ✅ Accurate Contact Data – Identify invalid or fake phone numbers automatically. 🌐 Geolocation Enrichment – Add country, location, and timezone for better segmentation. 🔁 Full Automation – No manual lookups or copying data between tools. 📊 Live Google Sheets Sync – Enriched data is updated directly into your spreadsheet. 🧠 Workflow Nodes Explained | Node | Purpose | |------|---------| | 🟢 Manual Trigger | Starts the workflow manually from n8n. | | 📄 Google Sheets (Read) | Fetches phone numbers from your spreadsheet using a Service Account. | | 🔁 Split In Batches | Loops over each row one at a time to handle individual API requests. | | 🌐 HTTP Request | Sends phone number to phone number validator via RapidAPI and receives validation + metadata. | | 📥 Google Sheets (Update) | Writes the response back into the matching row using the phone field. | 🛰️ API Used: phone number validator We use the phone number validator API from RapidAPI to: Validate phone numbers (real or fake?) Identify the country, location, and timezone > It’s fast, reliable, and great for cleaning large datasets or qualifying leads before outreach. 🧰 Prerequisites 📄 A Google Sheet with a column named phone 🔐 RapidAPI key with access to phone number validator 🔧 Google Service Account credentials set up in n8n 🚀 How to Use 🔗 Link your Google Sheet and configure authentication 🔑 Add your RapidAPI key in the HTTP node headers ▶️ Click "Execute Workflow" 🧠 Each phone number is validated and enriched 📊 Results are written back to your Google Sheet 📎 Tags phone validation, rapidapi, google sheets, data enrichment, phone number validator, crm automation, lead cleaning, timezone lookup
by Viktor Klepikovskyi
n8n Asynchronous Workflow with Wait Node POC This template contains a two-part workflow designed to demonstrate a proof-of-concept for asynchronous and parallel execution of tasks in n8n. Purpose The purpose of this template is to showcase how you can run multiple long-running tasks simultaneously without blocking your main workflow. It utilizes the "Wait For Sub-workflow Completion" option and the "Wait" node to effectively manage concurrent execution and collect results from sub-workflows via webhooks. This pattern is ideal for use cases involving batch processing or any scenario where a workflow needs to trigger multiple independent tasks and wait for all of them to report back. Setup Instructions Import: Import both the "Main Orchestrator" and "Asynchronous Worker" workflows into your n8n instance. Link Workflows: In the "Main Orchestrator" workflow, ensure the "Execute Workflow" node is correctly configured to call the "Asynchronous Worker" workflow. You can select it by its name from the dropdown menu. Configure: The template is pre-configured to run two parallel tasks with different wait durations to simulate a real-world scenario. You can adjust the parameters on the "Execute Workflow" node to test different wait times. Execution: Execute the "Main Orchestrator" workflow. You will see the workflow pause at the "Wait" nodes while the "Asynchronous Worker" workflows run in the background. Once they complete, they will call back via the webhook, allowing the main workflow to resume and summarize the results. For a detailed walkthrough of how this template works and an explanation of the underlying concepts, please read the full blog post here
by Mihail Morosan
Get the latest news, from Kagi, with a workflow that lets you filter by news category. Feed the results in your voice assistant automations to get on-demand news. Or leverage LLM models to create daily summaries from the headlines you retrieved. How it works This workflow takes a category name, from the ones available on Kagi News, then uses the Kagi News API to get all of the day's stories in that category. It then does a bit of filtering, to make it easier to manipulate. But you can skip or change that to your liking. How to use To test it, simply change the pinned data in the Start node, particularly the category field. You can use such examples as World, UK or Technology. Unsure as to what options for category there are? Just run the workflow and check the output of the Split Categories node! It will list all categories available. Take the value from categoryName. Things to consider I used categoryName as the input instead of categoryId for one reason: to make it easier for LLMs to populate that field. If this doesn't work for you, it should be quite easy to change. It is also a single category at a time. If you want to get stories from more categories at once, you can take an array as input in Start, then filter on the categories list containing your entries, rather than an exact match. Finally, you will have to merge all calls to Split out stories after each call to the API. Requirements None beyond an internet connection for your n8n instance. There is no API access token needed or any authorisation of any kind.
by Rahul Joshi
Description: Stay on top of product issues with this n8n automation template that centralizes bug reports from Zendesk into a Google Sheets dashboard. The workflow filters only tickets tagged as “bug,” enriches them with reporter details, and updates a single source of truth for developers, QA teams, and support staff. Perfect for product managers, SaaS companies, and agile teams that need full visibility into bug trends and customer impact without wasting time on manual data entry. What This Template Does (Step-by-Step) ⚡ Manual Trigger or Scheduling Run on-demand after releases or bug triage meetings, or set up a schedule to auto-run daily/weekly. 📥 Fetch All Zendesk Tickets Retrieves tickets from your Zendesk account with full metadata. 🔍 Filter Bug Reports Only Processes only tickets tagged as “bug” to ensure relevance. 👤 Add Reporter Details Enriches bug reports with requester’s name, email, and profile data for impact tracking. 📊 Update Google Sheets Bug Tracker Stores bug details including Ticket No., Description, Status, Reporter Info, and Tags. ✔️ Smart update avoids duplicates by using description as a unique key. 🔁 Continuous Bug Aggregation Ensures all relevant bug reports are tracked and kept up-to-date in one central place. Key Features 🔍 Tag-based bug filtering 📊 Centralized bug dashboard in Google Sheets ⚡ Zendesk + Google Sheets integration with OAuth2 ♻️ Real-time sync with deduplication logic 🔐 Secure API credential handling Use Cases 🐞 Track and prioritize product bugs from customer reports 📊 Give QA and dev teams a shared bug dashboard 📩 Identify high-impact bugs based on affected customers 📈 Monitor bug frequency and trends for release planning Required Integrations Zendesk API (for ticket fetch + user info) Google Sheets (for storing/updating bug tracker) Why Use This Template? ✅ Centralizes bug visibility for all teams ✅ Saves hours of manual spreadsheet updates ✅ Improves prioritization with customer context ✅ Scales easily with more tags or categories ✅ Keeps bug tracking transparent across stakeholders
by System Admin
Tagged with: , , , ,
by System Admin
Tagged with: , , , ,
by Adrian Kendall
Key Features Implements a simple round-robin distribution mechanism using a Data Table to track the last route used. Supports multiple downstream workflows or resources, balancing workload across them sequentially. Uses Switch and Code nodes for flexible routing logic. Designed for easy customization — replace placeholder “Route” nodes with sub-workflow calls or API triggers. Works with any trigger type, and includes merge logic to preserve input data. Nodes in Use | Node Name | Type | Purpose | |-------------------------------------------------|---------------|--------------------------------------------------------------------------| | When clicking ‘Execute workflow’ | Manual Trigger | Test entry point for manual execution. | | Calculate the next route to use | Data Table | Retrieves the last used route number. | | Code in JavaScript | Code | Increments the route counter (0–3 cycle). | | Update last_used in the datatable | Data Table | Updates the “Last_Used” field to track next route. | | Round Robin Router | Switch | Routes workflow execution to the correct path based on Last_Used value. | | Route 1 / Route 2 / Route 3 | NoOp | Placeholder routes — replace with your own workflows. | | Merge trigger data to pass to subworkflow if needed | Merge | Combines trigger data with routing data for sub-workflows. | | Sticky Notes | Annotations | Explain workflow logic and intended replacements. | How It Works The workflow starts when triggered manually (or by another workflow). The Data Table node fetches the current value of Last_Used, which identifies which route was last used. The Code node increments that value, resetting to 0 after 3, creating a round-robin cycle. The Data Table update node stores the new Last_Used value. The Switch node reads Last_Used and routes execution to the correct downstream branch. Each route can represent a duplicated workflow, resource, or API endpoint. Optionally, the Merge node reattaches trigger data before sending it to sub-workflows. Step-by-Step Trigger the workflow manually or via webhook/cron/etc. Retrieve current route index using the Data Table node. Increment route counter with the JavaScript Code node: If Last_Used = 3, it resets to 0. Otherwise, increments by 1. Update Data Table with the new Last_Used value. Route execution using the Switch node based on that value. Send data to corresponding subworkflow (Route 1, Route 2, Route 3). Replace the NoOp nodes with your target workflow or HTTP call nodes for real routing. Use Cases Distribute load across multiple API endpoints to prevent throttling. Run identical sub-workflows on different worker instances for parallel processing. Simulate load balancing during testing of N8N workflows. Sequentially alternate between external systems or servers handling similar tasks. Act as a proof-of-concept for balancing strategies before scaling up.
by System Admin
No description available
by Yasser Sami
Zillow Property Scraper Using Olostep API This n8n template automates Zillow property data collection by scraping Zillow search results using the Olostep API. It extracts property price, link to listing, and location, removes duplicates, and stores everything in a Google Sheet or Data Table. Who’s it for Real estate analysts and investors researching property markets. Lead generators needing structured Zillow data. Freelancers and automation builders collecting housing listings. Anyone needing fast, clean Zillow data without manual scraping. How it works / What it does Form Trigger User enters a Zillow search URL. This becomes the base Zillow search URL. Pagination Logic A list of page numbers (1–7) is generated. Each number is used to load the next Zillow search page. Scrape Zillow Pages with Olostep For each page, the Olostep API scrapes the Zillow results. Olostep’s LLM extraction schema extracts: price url (link to the Zillow listing) location Parse & Split Results Returned JSON is cleaned and converted into individual listing items. Remove Duplicates Ensures each Zillow listing appears only once. Insert into Google Sheet / Data Table Final cleaned listings are inserted row-by-row. Perfect for filtering, exporting, or further analysis. This workflow gives you a fast, scalable property scraper using Zillow + Olostep — no browser automation, no manual copy/paste. How to set up Import the template into n8n. Add your Olostep API key. Connect your Google Sheet or n8n Data Table. Deploy the form and start scraping by entering a place name. Requirements Olostep API key Google Sheets account or Data Table n8n cloud or self-hosted instance How to customize the workflow Add more pages to the pagination array (e.g., 1–20). Expand the LLM extraction schema to include: number of bedrooms number of bathrooms square footage property type Trigger via Telegram or API instead of a form. Send results to Airtable or Notion instead of Google Sheets. 👉 This template gives you an automated Zillow scraper powered by AI extraction — perfect for real estate lead gen or market research.
by Wayne Simpson
This template is a practical introduction to n8n Webhooks with built-in examples for all major HTTP methods and authentication types. It is designed as a learning resource to help you understand how webhooks work in n8n, how to connect them to a data store, and how to secure them properly. What’s included: Webhook nodes for GET, POST, PUT, PATCH, DELETE, and HEAD Demonstrations of Basic Auth, Header Auth, and JWT Auth Supabase integration for creating, retrieving, updating, and deleting rows Example response handling with Respond to Webhook nodes Sticky notes explaining each method, response type, and security option Use this template to: Learn how to configure and test webhooks in n8n Explore different authentication strategies Connect webhooks to a simple Supabase table Understand best practices for securing webhook endpoints This workflow is intended as an educational starting point. It shows you how to receive requests, map data, and return responses securely. For production use, adapt the structure, apply your own security policies, and extend the logic as needed. Check out the YouTube video here: https://www.youtube.com/watch?v=o6F36xsiuBk
by System Admin
Tagged with: , , , ,
by System Admin
Tagged with: , , , ,