Workflow Templates

⚠️ Disclaimer: > I am not a cybersecurity expert. This workflow was built through research and with the assistance of an LLM (Claude Opus 4.6). While it implements well-established security patterns (HMAC-SHA256, timing-safe comparison, replay protection, strict payload validation), please review the logic carefully and ensure it meets your own security requirements before deploying it in production. Who is this for? This template is for anyone exposing an n8n workflow via webhook and wanting to ensure that only authenticated, untampered requests are processed. What problem does this solve? Public webhooks are vulnerable by default. Without proper verification, anyone who discovers your URL can send forged requests, replay old ones, or inject unexpected parameters. While n8n's built-in Webhook authentication modes (Basic Auth, Header Auth, JWT) verify who is calling, they don't verify that the payload hasn't been altered, that the request is fresh, or that the data structure matches what you expect. This template adds those missing layers: Authentication** — Verifies the sender's identity through HMAC-SHA256 signature validation Integrity** — Ensures the payload hasn't been modified by signing the raw body byte-for-byte Replay protection** — Rejects requests with expired timestamps (configurable, default: 5 minutes) Payload sanitization** — Strict whitelist filtering blocks unauthorized fields before they reach your logic What this workflow does The workflow chains six security layers before any business logic runs: Webhook receives the request with Header Auth + Raw Body enabled to preserve the original payload Extract rawBody (Code node) decodes the binary into a UTF-8 string and extracts the security headers Crypto computes the HMAC-SHA256 signature of {timestamp}.{rawBody} using your HMAC secret Timing-Safe HMAC Check (Code node) validates the timestamp freshness and compares signatures using crypto.timingSafeEqual() Strict Payload Validation (Code node) parses the JSON, checks required fields, and rejects any unexpected keys AI Agent processes the prompt only after all checks pass Invalid requests are immediately rejected with 403 Forbidden (signature/timestamp failure) or 400 Bad Request (payload validation failure), with no response body to avoid leaking internal logic. Example use case The included example protects an AI Agent endpoint that expects a simple {"prompt": "..."} payload. But this is just a starting point — replace the AI Agent with any node and adapt the payload validation to your own schema. Common adaptations: CRM or SaaS event callbacks CRUD operations on a database Third-party API integrations Setup Prerequisites An n8n instance (Cloud or Self-hosted) A shared HMAC secret between the sender and this workflow — keep it safe and never expose it in workflow logs or execution data Going further This workflow is a solid starting point — it's more secure than a raw exposed webhook. However, it focuses on application-level security (authentication, integrity, replay protection, payload sanitization). For a production-grade setup, consider adding layers at the infrastructure level : Rate limiting** IP whitelisting** Reverse proxy hardening**

Turn your favorite podcast episodes into engaging social media content automatically. This workflow fetches new episodes from an RSS feed, transcribes the audio using OpenAI Whisper, generates a concise summary using GPT-4o, and drafts a tweet. It then sends the draft to Slack for your review before posting it to X (Twitter). Who is this for Content creators, social media managers, and podcast enthusiasts who want to share insights without manually listening to and typing out every episode. Key Features Large File Support:** Includes a custom logic to download audio in chunks, ensuring stability even with long episodes (preventing timeouts). Human-in-the-Loop:** Nothing gets posted without your approval. You can review the AI-generated draft in Slack before it goes live. High-Quality AI:** Uses OpenAI's Whisper for accurate transcription and GPT-4o for intelligent summarization. How it works Monitor: Checks the Podcast RSS feed daily for new episodes. Process: Downloads the audio (handling large files via chunking) and transcribes it. Draft: AI summarizes the transcript into bullet points and formats it for X (Twitter). Approve: Sends the draft to a Slack channel. Publish: Once approved by you, it posts the tweet to your X account. Requirements OpenAI API Key Slack Account & App (Bot Token) X (Twitter) Developer Account (OAuth2) Setup instructions RSS Feed: The template defaults to "TED Talks Daily" for demonstration. Open the [Step 1] RSS node and replace the URL with your target podcast. Connect Credentials: Set up your credentials for OpenAI, Slack, and X (Twitter) in the respective nodes. Slack Channel: In the [Step 12] Slack node, select the Channel ID where you want to receive the approval request.

Description: Don't just get a recipe. Get a Strategy. (Speed / Healthy / Creative) 🍳🤖 This workflow solves the "What should I eat?" problem by using Google Gemini to generate 3 distinct recipe variations simultaneously based on your fridge leftovers. It demonstrates advanced n8n concepts like Array Processing and Data Aggregation. Key Features: Array Processing: Demonstrates how to handle JSON lists (Gemini outputs an array -> n8n splits it -> API calls run for each item). Aggregation: Shows how to combine processed items back into a single summary email. Visual Enrichment: Automatically searches for recipe images using Google Custom Search. How it works: Input: Enter ingredients via the Form Trigger. Generate: Gemini creates 3 JSON objects: "Speed (5min)", "Healthy", and "Creative". Process: The workflow iterates through the 3 recipes, searching for images and logging data to Google Sheets. Aggregate: The results are combined into one HTML comparison table. Deliver: You receive an email with 3 options to choose from. Setup Requirements: Google Sheets: Create a sheet named Recipes with headers: date, ingredients, style, recipe_name, recipe_text, image_url. Credentials: Google Gemini API, Google Custom Search (API Key & Engine ID), Gmail, Google Sheets. Configuration: Enter your IDs in the "1. Configuration" node.

HR Client Acquisition (Part 1) – Job Lead Discovery & AI Qualification System This n8n template helps recruitment agencies discover active job openings, filter them based on hiring relevance, and qualify them using AI — specifically designed for semi-skilled manpower hiring use cases. What this template demonstrates Job lead discovery using Apify scraping Hash-based deduplication to avoid duplicate entries Batch processing using Split In Batches Google Sheets as a structured lead database AI-based lead qualification with strict JSON outputs Separation between scraping, processing, and scoring Use cases Recruitment agencies sourcing overseas job demand HR consultancies targeting bulk hiring companies Manpower supply businesses (semi-skilled labor focus) Job demand validation before outreach Building job-based lead pipelines How it works User submits job roles and locations via form Inputs are expanded into multiple search combinations Apify scrapes job listings based on these inputs Jobs are normalized and assigned unique identifiers Existing jobs in Google Sheets are checked for duplicates Only new jobs are stored and processed Missing company data is enriched if required AI scores each job based on hiring relevance Jobs are marked as qualified or not qualified Final results are saved back into Google Sheets How to use Submit job roles and locations using the form trigger Connect your Apify API credentials Connect your Google Sheets account Add your OpenAI API key Run the workflow in test mode Check results inside Google Sheets Adjust scoring logic if needed Requirements n8n (Cloud or Self-hosted) Apify account for job scraping Google Sheets for storage OpenAI or compatible LLM API Customising this workflow Modify job roles to match your niche (e.g., drivers, welders, helpers) Adjust AI scoring logic for your hiring criteria Replace Google Sheets with a database if needed Add filters like salary, visa type, or urgency Extend workflow for enruching & outreach automation (Part 2) Good to know This template focuses only on job discovery and qualification It is designed for semi-skilled manpower hiring workflows AI scoring can be customized for any industry or role No outreach is performed in this workflow Works best with consistent job data sources Who this is for Recruitment agencies working with overseas clients HR consultants sourcing bulk hiring opportunities Founders building recruitment automation systems Anyone building a job-based lead generation pipeline

[Meta] Multi-Format Documentation Generator for N8N Creators (+More) One-Line Description Transform n8n workflow JSON into five ready-to-publish documentation formats including technical guides, social posts, and marketplace submissions. Detailed Description What it does: This workflow takes an exported n8n workflow JSON file and automatically generates a complete documentation package with five distinct formats: technical implementation guide, LinkedIn post, Discord community snippet, detailed use case narrative, and n8n Creator Commons submission documentation. All outputs are compiled into a single Google Doc for easy access and distribution. Who it's for: n8n creators** preparing workflows for the template library or community sharing Automation consultants** documenting client solutions across multiple channels Developer advocates** creating content about automation workflows for different audiences Teams** standardizing workflow documentation for internal knowledge bases Key Features: Parallel AI generation** - Creates all five documentation formats simultaneously using Claude, saving 2+ hours of manual writing Automatic format optimization** - Each output follows platform-specific best practices (LinkedIn character limits, Discord casual tone, n8n marketplace guidelines) Single Google Doc compilation** - All documentation consolidated with clear section separators and automatic workflow name detection JSON upload interface** - Simple form-based trigger accepts workflow exports without technical setup Smart content adaptation** - Same workflow data transformed into technical depth for developers, engaging narratives for social media, and searchable descriptions for marketplaces Ready-to-publish outputs** - No editing required—each format follows platform submission guidelines and style requirements How it works: User uploads exported n8n workflow JSON through a web form interface Five AI agents process the workflow data in parallel, each generating format-specific documentation (technical guide, LinkedIn post, Discord snippet, use case story, marketplace listing) All outputs merge into a formatted document with section headers and separators Google Docs creates a new document with auto-generated title from workflow name and timestamp Final document populates with all five documentation formats, ready for copying to respective platforms Setup Requirements Prerequisites: Anthropic API** (Claude AI) - Powers all documentation generation; requires paid API access or credits Google Docs API** - Creates and updates documentation; free with Google Workspace account n8n instance** - Cloud or self-hosted with AI agent node support (v1.0+) Estimated Setup Time: 20-25 minutes (15 minutes for API credentials, 5-10 minutes for testing with sample workflow) Installation Notes API costs**: Each workflow documentation run uses ~15,000-20,000 tokens across five parallel AI calls (approximately $0.30-0.50 per generation at current Claude pricing) Google Docs folder**: Update the folderId parameter in the "Create a document" node to your target folder—default points to a specific folder that won't exist in your Drive Testing tip**: Use a simple 3-5 node workflow for your first test to verify all AI agents complete successfully before processing complex workflows Wait node purpose**: The 5-second wait between document creation and content update prevents Google Docs API race conditions—don't remove this step Form URL**: After activation, save the form trigger URL for easy access—bookmark it or share with team members who need to generate documentation Customization Options Swappable integrations: Replace Google Docs with Notion, Confluence, or file system storage by swapping final nodes Switch from Claude to GPT-4, Gemini, or other LLMs by changing the language model node (may require prompt adjustments) Add Slack/email notification nodes after completion to alert when documentation is ready Adjustable parameters: Modify AI prompts in each agent node to match your documentation style preferences or add company-specific guidelines Add/remove documentation formats by duplicating or deleting agent nodes and updating merge configuration Change document formatting in the JavaScript code node (section separators, headers, metadata) Extension possibilities: Add automatic posting to LinkedIn/Discord by connecting their APIs after doc generation Create version history tracking by appending to existing docs instead of creating new ones Build approval workflow by adding human-in-the-loop steps before final document creation Generate visual diagrams by adding Mermaid chart generation from workflow structure Create multi-language versions by adding translation nodes after English generation Category Development Tags documentation n8n content-generation ai claude google-docs workflow automation-publishing Use Case Examples Marketplace contributors**: Generate complete n8n template submission packages in minutes instead of hours of manual documentation writing across multiple format requirements Agency documentation**: Automation consultancies can deliver client workflows with professional documentation suite—technical guides for client IT teams, social posts for client marketing, and narrative case studies for portfolio Internal knowledge base**: Development teams standardize workflow documentation across projects, ensuring every automation has consistent technical details, use case examples, and setup instructions for team onboarding

How It Works The webhook receives incoming profiles and extracts relevant demographic, financial, and credential data. The workflow then queries the programs database to identify suitable options, while the AI generates personalized recommendations based on eligibility and preferences. A formal recommendation letter is created, followed by a drafted outreach email tailored to coordinators. Parsers extract structured data from the letters and emails, a Slack summary is prepared for internal visibility, and the final response is sent to the appropriate recipients. Setup Steps Configure AI agents by adding OpenAI credentials and setting prompts for the Program Matcher, Letter Writer, and Email Drafter. Connect the programs database (Airtable or PostgreSQL) and configure queries to retrieve matching program data. Set up the webhook by defining the trigger endpoint and payload structure for incoming profiles. Configure JSON parsers to extract relevant information from profiles, letters, and emails. Add the Slack webhook URL and define the summary format for generated communications. Prerequisites OpenAI API key Financial programs database Slack workspace with webhook User profile structure (income, GPA, demographics) Use Cases Universities automating 500+ annual applicant communications Scholarship foundations personalizing outreach at scale Customization Add multilingual support for international applicants Include PDF letter generation with signatures Benefits Reduces communication time from 30 to 2 minutes per applicant, ensures consistent professional quality

How it works This workflow runs on a daily schedule and automatically sends follow-up reminders to candidates who have received an application link but have not yet applied. It checks Airtable for eligible records, calculates how much time has passed since outreach was sent, and decides whether to send a first reminder, second reminder, or no message. All decision logic is handled in a single Code node, which outputs a simple routing value. This makes the workflow easy to understand and prevents fragile conditional logic. Each reminder is sent only once. After a reminder is sent, the workflow updates Airtable with a corresponding “sent” flag so the same reminder cannot be sent again on future runs. Setup steps Connect your Airtable account and select the table containing candidate records. Ensure Airtable includes a timestamp field indicating when outreach was sent. Ensure checkbox fields exist for each reminder (for example, “Reminder 1 Sent” and “Reminder 2 Sent”). Connect your email provider (Brevo) and SMS provider. Set the Cron node to run once per day at your preferred time. Initial setup typically takes 10–15 minutes. When to use this template You want automated follow-ups without manual chasing You need to avoid sending duplicate reminders You want Airtable to remain the source of truth

AI Portfolio Generator for Freelancers Automatically transform any website URL into a complete portfolio entry with professional screenshots and AI-generated Upwork project descriptions. 🎯 Perfect For Freelancers** building their Upwork/portfolio from past projects Agencies** documenting client work at scale Web developers** showcasing their websites professionally Anyone** who needs consistent, high-quality website screenshots ✨ What It Does Submit a URL via simple web form AI analyzes the website (structure, niche, audience, services) Smart screenshots capture hero, fullpage, individual sections, and mobile views AI writes compelling Upwork portfolio description with title, role, and skills Auto-saves everything to Google Drive + Sheets + sends Telegram notification 🔥 Key Features JavaScript Rendering** — Works with React, Vue, Next.js, and any SPA (via Firecrawl) Intelligent Section Detection** — AI identifies real content sections, not utility elements Multiple Screenshot Types** — Hero (1920×1080), fullpage, custom sections, mobile (375×812) Retina Quality** — 2x device scale factor for crisp images Smart Error Handling** — Retries failed screenshots, filters invalid results Rate Limit Protection** — Built-in delays to respect API limits Complete Logging** — Every run logged to Google Sheets with all metadata 📸 Screenshots Captured | Type | Resolution | Description | |------|------------|-------------| | Hero | 1920×1080 @2x | Above-the-fold view | | Fullpage | 1920×auto @2x | Entire scrollable page | | Sections | 1920×1080 @2x | Each detected content section | | Mobile | 375×812 @2x | iPhone-style mobile view | 🤖 AI-Generated Upwork Content Project Title** (max 50 chars) Your Role** (e.g., "Full-Stack Developer", "Lead Designer") Project Description** (goals, solution, impact — max 600 chars) Skills** (5 relevant technical skills) 🔧 Services Used | Service | Purpose | Free Tier | |---------|---------|-----------| | Firecrawl | JavaScript rendering | ✅ 500 pages/month | | ScreenshotOne | Screenshot API | ✅ 100 screenshots/month | | OpenAI | GPT-4o-mini analysis | Pay-as-you-go | | Google Drive | Image storage | ✅ 15GB free | | Google Sheets | Results logging | ✅ Free | | Telegram | Notifications | ✅ Free | 📋 Setup Checklist ✅ Import workflow ✅ Add Firecrawl API key ✅ Add ScreenshotOne API key ✅ Connect OpenAI credentials ✅ Connect Google Drive (+ set your folder) ✅ Connect Google Sheets (+ set your spreadsheet) ✅ Set up Telegram bot + chat ID ✅ Activate & share the form URL! 💡 Pro Tips Test with simple sites first** before complex SPAs Increase delay** in Wait node if hitting rate limits Change AI model** to gpt-4o for better analysis quality All instructions included** as Sticky Notes inside the workflow! 📊 Output Example After processing example.com: 📁 5 PNG screenshots in Google Drive 📊 Full analysis row in Google Sheets 📱 Telegram message with all links and AI-generated Upwork content Built for freelancers, by a freelancer. Stop wasting hours on manual portfolio creation — let AI do the heavy lifting! 🚀 #portfolio, #screenshots, #upwork, #freelancer, #ai, #gpt, #automation, #firecrawl, #screenshotone, #google-drive, #google-sheets, #telegram, #website-analysis, #form-trigger

Who’s it for This template is built for WooCommerce store owners, eCommerce managers, and automation agencies who want to manage store operations directly from Telegram using an AI assistant. It’s ideal for users looking to save time, automate support, and access store data conversationally. How it works When a user sends a message via Telegram, the workflow triggers an AI agent that understands the request using a chat model with memory. Based on the intent, the agent executes the appropriate action such as retrieving orders, fetching product data, updating product information, logging data into Google Sheets, or sending email notifications. How to set up Connect your Telegram bot credentials Add your WooCommerce API keys Connect Google Sheets for data storage Connect your Gmail account Configure your OpenRouter or OpenAI API key Test the workflow via Telegram commands Requirements WooCommerce store with API access Telegram bot token Google Sheets account Gmail credentials OpenRouter or OpenAI API key How to customize You can expand this agent by adding tools like order creation, refund processing, CRM integrations, shipping updates, or advanced reporting. The AI prompt can also be modified to match your store operations.

This n8n workflow runs daily to analyze active customer behavior, engineers relevant features from usage and transaction data, applies a machine learning or AI-based model to predict churn probability, classifies risk levels, triggers retention actions for at-risk customers, stores predictions for tracking, and notifies relevant teams. Key Insights Prediction accuracy heavily depends on feature quality — ensure login frequency, spend trends, support interactions, and engagement metrics are consistently captured and up-to-date. Start with simple rule-based scoring or AI prompting (e.g., OpenAI/Claude) before integrating full ML models for easier testing and faster value. High-risk thresholds (e.g., >70%) should be tuned based on your actual churn data to avoid alert fatigue or missed opportunities. Workflow Process Initiate the workflow with the Daily Schedule Trigger node (runs every day at 2 AM). Query the customer database to fetch active user profiles, recent activity logs, login history, transaction records, and support ticket data. Perform feature engineering: calculate metrics such as login frequency (daily/weekly), average spend, spend velocity, days since last activity, number of support tickets, NPS/sentiment if available, and other engagement signals. Feed engineered features into the prediction step: call an ML model endpoint, run a Python code node with a lightweight model, or use an AI agent/LLM to estimate churn probability (0–100%). Classify each customer into risk tiers: HIGH RISK, MEDIUM RISK, or LOW RISK based on configurable probability thresholds. For at-risk customers (especially HIGH), trigger retention actions: create personalized campaigns, add to nurture sequences, generate discount codes, or create tasks in CRM. Store predictions, risk scores, features, and actions taken in an analytics database for historical tracking and model improvement. Send summarized alerts (e.g., list of high-risk customers with scores and recommended actions) via Email and/or Slack to customer success or retention teams. Usage Guide Import the workflow into n8n and configure credentials for your customer database (PostgreSQL/MySQL), ML API (if external), analytics DB, Slack webhook, SMTP/email, and CRM/retention platform. Define feature extraction queries and thresholds carefully in the relevant nodes — test with a small customer subset first. If using AI/LLM for prediction, refine the prompt to include clear examples of churn signals. Run manually via the Execute workflow button with sample data to validate data flow, scoring logic, and notifications. Once confident, activate the daily schedule. Prerequisites Customer database with readable tables for users, activity logs, transactions, and support interactions ML integration option: either an external ML API endpoint, Python code node with scikit-learn/simple model, or LLM node (OpenAI, Claude, etc.) for probabilistic scoring Separate analytics database (or same DB) with a table ready for churn predictions (customer_id, date, churn_prob, risk_level, etc.) SMTP credentials or email service for alerts Slack webhook URL (optional but recommended for team notifications) CRM or marketing automation API access (e.g., HubSpot, ActiveCampaign, Klaviyo) for creating retention campaigns/tasks Customization Options Adjust the daily trigger time or make it hourly for near real-time monitoring of high-value accounts. Change risk classification thresholds or add more tiers in the scoring logic node. Enhance the prediction step: switch from LLM-based to a trained ML model (via Hugging Face, custom endpoint, or Code node). Personalize retention actions: use AI to generate custom email content/offers based on the customer's behavior profile. Add filtering (e.g., only high-value customers > certain MRR) to focus retention efforts. Extend notifications: integrate with Microsoft Teams, Discord, or create tickets in Zendesk/Jira for follow-up. Build feedback loop: after actual churn occurs, update a training dataset or adjust weights/rules in future runs.

Retail Price Sync Automation for Shopify & WooCommerce This workflow automates the synchronization of product prices across Shopify and WooCommerce platforms to ensure retail consistency. It triggers when a price change is detected in either system, applies platform-specific pricing rules (such as psychological rounding) and updates the secondary platform. The workflow also includes a threshold-based alerting system via Gmail for major price drops and logs every change to a Google Sheets master file for auditing. Quick Implementation Steps Set the priceChangeThreshold in the Shopify Configuration and WooCommerce Configuration nodes. Connect your Shopify Access Token credentials to the Shopify trigger and update nodes. Connect your WooCommerce API credentials to the WooCommerce trigger and update nodes. Link your Google Sheets OAuth2 and Gmail OAuth2 credentials for logging and notifications. Specify the documentId for your pricing log in the Log Price Changes node. What It Does This workflow acts as a bridge between two major e-commerce platforms, ensuring that a price update in one is intelligently reflected in the other. It goes beyond simple mirroring by: Threshold Monitoring: Detecting if a price change exceeds a set limit (e.g., $150 or $500) to trigger immediate management alerts. Platform-Specific Logic: Automatically formatting prices for different environments—for example, rounding WooCommerce prices to the nearest .99 for psychological pricing while using standard rounding for Shopify. Audit Trail Creation: Maintaining a centralized record of all price migrations in Google Sheets, including SKUs, old vs. new prices and timestamps. Team Communication: Sending automated email notifications to ensure the team is aware of successful syncs or critical price volatility. Who’s It For Multi-Channel Retailers who need to keep pricing in sync across Shopify and WooCommerce storefronts. Inventory Managers looking to automate price adjustments without manual data entry. Finance & Operations Teams requiring an automated audit log of all pricing modifications. Technical Workflow Breakdown Entry Points (Triggers) Shopify Price Update: Triggers on the orders/updated topic (or product updates) to capture new price data from Shopify. WooCommerce Price Update: Triggers on product.updated to capture changes originating from the WooCommerce store. Processing & Logic Configuration Nodes: Define the source system and set the specific threshold for what constitutes a "major" price change. Apply Platform-Specific Rules: A custom code block that calculates psychological pricing (e.g., forcing a .99 ending) and ensures prices never drop below a minimum safety floor (e.g., $1.00). Check Price Change Threshold: An internal filter that routes the workflow based on the magnitude of the price shift. Output & Integrations Update Nodes: Pushes the formatted price data to the target platform (Shopify or WooCommerce). Log Price Changes: Appends a new row to a Google Sheet with detailed metadata. Notifications: Uses Gmail to send high-priority alerts for major drops and routine confirmations for successful syncs. Customization Adjust Pricing Strategy Modify the Apply Platform-Specific Rules (Code Node) to change rounding logic, add currency conversion factors or implement different psychological pricing tiers. Change Alert Thresholds Update the priceChangeThreshold value in the Shopify Configuration or WooCommerce Configuration nodes to make alerts more or less sensitive. Expand Logging The Log Price Changes node is set to autoMapInputData. You can add custom columns to your Google Sheet and the workflow will automatically attempt to fill them if the data exists in the workflow. Troubleshooting Guide | Issue | Possible Cause | Solution | | :--------------------------------------- | :----------------------------------- | :----------------------------------------------------------------------------------------------------------------- | | Sync Not Triggering | Webhook not registered correctly. | Check the webhookId in the Shopify/WooCommerce trigger nodes and ensure the apps have permission to send events. | | Google Sheets Error | Sheet ID or Column names mismatched. | Verify the documentId and ensure the id column exists in your Sheet for matching. | | Prices Not Rounding Correct/Expected | Code node logic error. | Review the JavaScript in Apply Platform-Specific Rules to ensure the Math functions match your strategy. | | Emails Not Sending | Gmail OAuth2 expired. | Re-authenticate your Gmail credentials in the n8n settings. | Need Help? If you need assistance adjusting the psychological pricing code, adding more platforms (like Amazon or eBay) or setting up advanced Slack notifications, please reach out to our n8n automation experts at WeblineIndia. We can help scale this workflow to manage thousands of SKUs with high precision.

📊 Description This workflow automates interview scheduling by orchestrating Calendly, Zoom, Asana, and Gmail into a single, reliable hiring pipeline. When a candidate books an interview, the automation ensures the interview is properly scheduled, tracked, assigned, and communicated — without any manual follow-ups. The workflow listens for new Calendly bookings, normalizes scheduling data, creates a Zoom meeting, assigns a structured interview task in Asana, and notifies the appropriate interviewer via email. Conditional routing ensures the right stakeholders are involved while keeping candidate communications separate. Designed for real-world hiring operations, this automation provides consistency, accountability, and scalability as interview volume grows. 🔁 What this template does Receives interview booking events from Calendly via webhook. Normalizes and structures scheduling details such as time, timezone, and invitee information. Creates a Zoom meeting automatically for the scheduled interview. Routes the interview based on type (for example, HR or Technical). Creates a structured Asana task assigned to the appropriate interviewer. Stores interview context and Zoom meeting links directly in the Asana task. Sends automated email notifications to interviewers with complete interview details. Ensures interviewer-side visibility without exposing candidate-facing communications. Executes fully automatically with no manual intervention. ⭐ Key benefits Eliminates manual interview coordination and follow-ups Ensures every interview has a correctly configured Zoom meeting Keeps interviewers aligned through structured Asana task tracking Provides reliable, role-based notifications Reduces scheduling errors and missed interviews Production-ready automation for growing hiring teams 🧩 Features Calendly webhook-based trigger Normalized interview data handling Automated Zoom meeting creation Interview-type routing and interviewer assignment Interview-focused Asana task management Automated Gmail notifications Clean, interviewer-only communication flow Scalable interview orchestration design 🔐 Requirements Calendly account with webhook access enabled Zoom API credentials Asana OAuth2 credentials Gmail OAuth2 credentials n8n (cloud or self-hosted) 🎯 Target audience Hiring managers Technical interviewers HR and recruitment teams Startups and SaaS companies Automation engineers building internal hiring pipelines