Workflow Templates

This workflow is the second of three. You can find the other workflkows here: Incident Response Workflow - Part 1 Incident Response Workflow - Part 2 Incident Response Workflow - Part 3 We have the following nodes in the workflow: Webhook node: This trigger node listens to the event when the Acknowledge button is clicked. PagerDuty node: This node changes the status of the incident report from 'Triggered' to 'Acknowledged' in PagerDuty. Mattermost node: This node publishes a message in the auxiliary channel saying that the status of the incident report has been changed to Acknowledged.

🚀 LinkedIn Comments to Leads Extractor & Enricher (Apify) → Google Sheets / CSV Overview Automate LinkedIn lead generation by scraping comments from targeted posts and enriching profiles with detailed data This n8n workflow automatically extracts leads from LinkedIn post comments using Apify's powerful scrapers (no LinkedIn login required), enriches the data with additional profile information, and exports everything to Google Sheets or CSV format. ✨ Key Features 🔍 No Login Required: Scrape LinkedIn data without sharing credentials 💰 Cost-Effective: First 1,000 comments are free with Apify 📊 Data Enrichment: Enhance basic comment data with full profile details 📈 Export Options: Choose between Google Sheets or CSV output 🎯 Targeted Scraping: Focus on specific posts for quality leads 🛠️ Apify Scrapers Used 1. LinkedIn Post Comments Scraper Tool**: LinkedIn Post Comments, Replies, Engagements Scraper | No Cookies Pricing**: $5.00 per 1,000 results Function**: Extracts all comments and engagement data from specified LinkedIn posts 2. LinkedIn Profile Batch Scraper Tool**: LinkedIn Profile Details Batch Scraper (No Cookies Required) Pricing**: $5.00 per 1,000 results Function**: Enriches scraped profiles with detailed information > 💡 Free Tier: Apify provides 1,000 free scraped comments to get you started! 📋 Prerequisites Required API Credentials Apify Token Add your APIFY_TOKEN to the workflow credentials Get your token from Apify Console Google Sheets Credentials (if using Sheets export) Configure OAuth credentials for Google Sheets integration Follow n8n's Google Sheets setup guide 🔄 Workflow Process Default Mode: Form-Based Execution Manual Trigger → Launches the workflow Form Submission → User-friendly form for inputting LinkedIn post URLs Comment Scraping → Apify extracts all comments from specified posts Profile Enrichment → Additional profile data gathered for each commenter Data Processing → Creates unique, enriched lead list Google Sheets Export → Automatically populates your spreadsheet Result: You'll be redirected to a Google Sheets document containing all enriched leads Alternative Mode: CSV Export For users preferring CSV output: Disable: Form trigger nodes Enable: Manual trigger node Disable: Google Sheets export nodes Enable: CSV download nodes Configure: Add post IDs/URLs in "Set manual fields" node Execute: Run workflow and download CSV from the CSV node 📊 Output Data Structure Your exported data will include: Basic Info**: Name, headline, location Profile Details**: Company, position, industry Engagement Data**: Comment content, engagement metrics Contact Info**: Available profile links and connections Enriched Data**: Additional profile insights from Apify 💡 Pro Tips Quality over Quantity**: Target posts with high-quality, relevant engagement Monitor Costs**: Track your Apify usage to stay within budget Data Hygiene**: Regularly clean and deduplicate your lead lists Compliance**: Ensure your scraping activities comply with LinkedIn's terms of service 🆘 Troubleshooting Common Issues: Authentication Errors**: Verify your Apify token is correctly configured Empty Results**: Check that your LinkedIn post URLs are valid and public Export Failures**: Ensure Google Sheets credentials are properly set up Need Help? Contact Saverflow.ai for support and custom workflow development.

Never lose an inbound lead because someone missed the phone. This workflow captures missed inbound calls from Twilio, logs them, notifies your team, and instantly sends a context aware SMS to the caller. It automatically adapts messaging based on business hours, ensuring fast response during working hours and clear expectations after hours. Built for small service businesses, agencies, clinics, and local operators who rely heavily on phone calls. How it works Receives inbound call events from Twilio via webhook Filters for failed, busy, or no answer call statuses Checks whether the call happened during business hours Logs call details to Google Sheets for tracking and follow up Sends an automatic SMS reply to the caller During business hours, promises a quick callback After hours, sets next business day expectations Notifies your team in Slack with caller details This creates instant acknowledgment, internal visibility, and a structured follow up trail. Setup steps Connect your Twilio account and configure the webhook URL Connect Google Sheets and select your tracking sheet Connect Slack and choose a notification channel Adjust business hours and timezone inside the code node Customize SMS copy to match your brand voice Setup typically takes 10 to 15 minutes.

📄 What this workflow does This workflow transforms your n8n instance into a fully automated AI sales assistant for WooCommerce stores. It detects customer intent from chat, searches products, answers FAQs, generates Stripe payment links, captures leads into your CRM, and even escalates to human support when needed. It provides smooth conversational memory and syncs with your knowledge base to ensure accurate, human-like responses. 👤 Who is this for WooCommerce store owners who want to automate customer support and sales. Sales and marketing teams looking to scale personalized product recommendations. E-commerce managers who want to reduce manual chat handling. Anyone aiming to integrate AI assistants with payments, CRM, and FAQs. ✅ Requirements WooCommerce account with API access. Qdrant vector store (for FAQ and RAG retrieval). OpenAI/Gemini API credentials (for intent detection + message generation). Google Drive account (to sync and update knowledge base docs). Stripe account (to generate instant payment links). CRM account (HubSpot, Pipedrive, etc.) if lead capture is required. Telegram account for optional human escalation. ⚙️ How to set up Connect WooCommerce API credentials in n8n. Configure Gemini/OpenAI API for intent extraction and chat generation. Set up Qdrant for document retrieval, and link to your Google Drive Sales Docs folder. Configure Stripe API to enable instant payment link generation. Connect your CRM to capture new leads automatically. Add Telegram bot credentials for human escalation (optional). Enable conversational memory and test chat flows end-to-end. 🔁 How it works Intent Extraction → AI analyzes chat messages to detect Product Search, FAQ, Payment, or Lead Capture. Product Search → Queries WooCommerce catalog by keyword, SKU, or price range. FAQ Answering → Retrieves company policies/docs from Qdrant + Google Drive, answered via RAG. Payment Links → Stripe generates instant checkout links for customers ready to buy. Lead Capture → Name + email are auto-stored into CRM. Human Escalation → If intent is unclear, conversation is forwarded to Telegram. Conversational Memory → Maintains last 12 exchanges for natural dialogue. Knowledge Sync → Google Drive docs auto-update into Qdrant for live FAQ support. 💡 About Margin AI Margin AI is an AI-services agency that acts as your AI Service Companion. We design intelligent, human-centric automation solutions—turning your team’s best practices into scalable workflows and tools. Industries like marketing, sales, and operations benefit from our tailored AI consulting, automation tools, and chatbot development.

This workflow automates the process of estimating a person’s fashion size from an uploaded image using an AI model. This workflow is an automated pipeline that uses an AI model to estimate a person's body measurements and clothing size from an image URL. Key Features 🔁 Full Automation** – From image submission to result display, the process requires no manual steps. ⚙️ Easy Integration** – Uses n8n’s native nodes and simple HTTP requests to connect with Fal.ai’s API. 🕒 Real-Time Processing** – Automatically waits and checks for the AI result, ensuring the user receives the output as soon as it’s ready. 🧩 Modular Design** – Each step (submit → process → check → result) is clearly separated, making it easy to modify or extend (e.g., adding notifications or storing results in a database). 💡 User-Friendly Interface** – The initial form and final result form make it accessible even for non-technical users. 🔐 Secure** – Authentication to the Fal.ai API is handled through HTTP header authorization, keeping API keys protected. How it works Form Trigger: The workflow starts with a public form where a user submits a URL of an image. AI Processing Request: The submitted image URL is sent to the fal.run AI service (specifically, the "fashion-size-estimator" model) via a POST request. This initial request places the job in a queue and returns a unique request_id. Polling for Completion: The AI processing is asynchronous and takes some time. The workflow enters a loop where it: Waits: Pauses for 10 seconds to give the AI model time to process the request. Checks Status: Uses the request_id to check the status of the job. Conditional Check: An IF node checks if the status is "COMPLETED". If NO (not completed), the loop repeats (wait, then check again). If YES, the workflow exits the loop. Fetching and Displaying Results: Once processing is complete, the workflow retrieves the final result (containing the size, height, bust, waist, and hip measurements) and automatically displays it to the user on a "thank you" page. Set up steps To make this workflow operational, you need to configure the API authentication. Obtain an API Key: Create an account at fal.ai Navigate to your account settings to generate an API key. Configure Credentials in n8n: In your n8n instance, create a new HTTP Header Auth credential (you can name it "Fal.run API"). Set the Name field to Authorization. Set the Value field to Key YOURAPIKEY, replacing "YOURAPIKEY" with the actual key you obtained from fal.ai. Ensure this credential is correctly selected in the three HTTP Request nodes: "Send image to estimator", "Get status", and "Get result". Need help customizing? Contact me for consulting and support or add me on Linkedin.

This n8n template from Intuz provides a complete solution to automate your accounting by instantly creating QuickBooks sales receipts for every new Stripe payment. This workflow automates the process of recording successful payments from Stripe into QuickBooks by creating corresponding Sales Receipts. It ensures payment data is captured accurately, checks whether the customer exists in QuickBooks, and creates a new customer if necessary before generating the receipt. This integration streamlines bookkeeping by eliminating manual data entry and ensuring all payment records are synchronized between systems. Who's this workflow for? Accountants & Bookkeepers Small Business Owners E-commerce Managers Finance Teams How it works 1. Trigger on Successful Payment: The workflow starts instantly when a payment_intent.succeeded event is received from Stripe via a webhook. This means it only runs after a payment is confirmed. 2. Get Customer Details: It uses the customer ID from the payment to fetch the customer's full details (name and email) from Stripe. 3. Check for Customer in QuickBooks: The workflow then searches your QuickBooks account to see if a customer with that name already exists. 4. Create Customer if New: If the customer is not found in QuickBooks, a new customer record is automatically created using the information from Stripe. 5. Generate Sales Receipt: Finally, using the correct customer record (either existing or newly created) and the payment amount, the workflow creates and saves a new sales receipt in QuickBooks, perfectly matching the Stripe transaction. Key Requirements to Use This Template 1. n8n Instance: An active n8n account (Cloud or self-hosted). 2. Stripe Account: An active Stripe account with API access. You must be able to create and manage webhooks. 3. QuickBooks Online Account: An active QuickBooks Online account with API access to manage customers and sales receipts. Setup Instructions 1. Configure the Webhook Trigger: Copy the webhook URL from the Capture Payment (Webhook) node in n8n. In your Stripe dashboard, go to Developers > Webhooks and add a new endpoint. Paste the n8n webhook URL and have it listen for the payment_intent.succeeded event. 2. Connect Stripe: In the Get a customer node, connect your Stripe account credentials. 3. Connect QuickBooks: In all three QuickBooks nodes (Find Customer, Create a customer, and Create a payment), connect your QuickBooks Online account using OAuth2 credentials. 4. Activate Workflow: Save the workflow and toggle the "Active" switch to ON. Your accounting automation is now live! Connect with us Website: https://www.intuz.com/services Email: getstarted@intuz.com LinkedIn: https://www.linkedin.com/company/intuz Get Started: https://n8n.partnerlinks.io/intuz For Custom Worflow Automation Click here- Get Started

Capture leads from Tally forms to Google Sheets CRM This workflow automates lead intake by capturing form submissions, enriching them with smart tags and scores, storing them in a Google Sheets CRM, and sending personalized welcome emails. Who's it for This template is perfect for solopreneurs, small agencies, and marketing consultants who need a simple yet powerful CRM system without paying for expensive tools like HubSpot or Salesforce. If you're collecting leads through forms and manually copying data to spreadsheets, this automation will save you hours every week. What it does When someone submits your Tally lead capture form, this workflow automatically: Generates a unique lead ID and timestamps the entry Analyzes their responses to assign relevant service tags (Podcast Lead, Social Content Lead, Video Editing Lead, etc.) Calculates an initial lead score based on interest level Determines the next follow-up date automatically Appends all data to your Google Sheets CRM with proper formatting Logs the activity in a separate tracker sheet Sends a personalized welcome email tailored to their interests Updates the lead status to "Nurturing" Requirements Apps & Services: Google Sheets (for your CRM database) Tally.so or Google Forms (for lead capture) SendGrid account (free tier works) for email sending n8n instance (cloud or self-hosted) Setup needed: Create the Google Sheets CRM structure (4 sheets: Leads, Email Sequence Tracker, Activity Log, Dashboard Data) Set up your Tally form with fields: Name, Email, Business Type, Interest Level, Services Needed Configure SendGrid API credentials in n8n Connect your Google Sheets account to n8n How to set up Copy the Google Sheets template with all four sheets (Leads, Email Sequence Tracker, Activity Log, Dashboard Data) and set up column headers as specified Create your Tally form at tally.so with the required fields, then grab the webhook URL from n8n Import this workflow into your n8n instance Configure credentials for Google Sheets and SendGrid Update the webhook URL in your Tally form settings Customize the welcome email in the "Generate Welcome Email" node with your branding Test with a sample submission to verify everything flows correctly Activate the workflow and start capturing leads How to customize Modify service tags: Edit the serviceTagMap object in the "Auto-Tag Lead" node to match your specific services. Adjust lead scoring: Change the scoring logic in "Calculate Initial Dates & Score" to prioritize different interest levels or sources. Personalize emails: Update the email templates in "Generate Welcome Email" to match your brand voice and add specific resources or links. Add more integrations: Extend the workflow with Slack notifications, SMS alerts via Twilio, or sync to other tools like Notion or Airtable. Change follow-up timing: Modify the daysToAdd calculation to adjust when leads receive their next touchpoint. Add conditional paths: Use IF nodes to route different lead types to different email sequences or team members.

Order Fulfillment & Shipping Notification System Automatically notify customers via WhatsApp when their orders ship, with intelligent phone validation, multi-country support, and bilingual messaging including complete tracking information. What does this workflow do? When you fulfill an order in Shopify, this workflow instantly updates your database, validates the customer's phone number across 23+ countries, and sends a professional WhatsApp notification with full tracking details in their preferred language. Key features: 🌍 23+ Country Phone Validation - Automatically detects and formats phone numbers for GCC, MENA, and international customers 📦 Complete Tracking Info - Includes tracking number, courier name, and clickable tracking URL 🌐 Smart Bilingual Messaging - Arabic and English with luxury brand tone 💾 Real-time Database Sync - Updates order status and shipping details instantly 🔒 Test Number Protection - Blocks notifications to development phone numbers ✨ Personalized Messages - Addresses customers by first name ⏱️ Delivery Expectations - Communicates clear 7-12 business day timeline 🎯 International Format - Handles phone numbers with automatic country code detection Setup Requirements Integrations Needed: Shopify - For order fulfillment webhooks PostgreSQL - For order and customer data storage WhatsApp Business API - For sending notifications via Facebook Graph API Credentials Required: Shopify Access Token (with fulfillment webhook permissions) PostgreSQL database credentials WhatsApp Business API Bearer Token (Facebook Graph API v18.0) How to Use Import the workflow into your n8n instance Configure credentials: Add your Shopify store access token Connect your PostgreSQL database Add your WhatsApp Business API credentials Update test phone numbers in filter nodes (If10 and If11) with your actual test numbers Customize brand name in WhatsApp message templates if needed (currently "" / "") Activate the workflow to start sending shipping notifications Workflow Structure 1. Trigger (Shopify Webhook) Listens for fulfillments/create events when orders are marked as shipped in Shopify 2. Update Order Status Updates PostgreSQL database with: Status changed to 'shipped' Shipping company name Tracking number 3. Customer Lookup Retrieves customer record from database using phone number from fulfillment data 4. Phone Validator (Code Node) Intelligent phone number formatting: Detects country from shipping address Validates and cleans phone number Adds appropriate country code if missing Supports 23 countries across GCC, MENA, and international markets Ensures proper international format (+CountryCode) 5. Get Customer Preferences Retrieves language preference and first name for personalization 6. Language Detection Routes workflow based on customer's preferred language (Arabic vs. English) 7. Test Number Filter Prevents notifications to internal/development phone numbers 8. WhatsApp Notification Sends comprehensive shipping notification with tracking details in customer's language Supported Countries & Codes GCC Region: 🇴🇲 Oman (968) 🇦🇪 UAE (971) 🇸🇦 Saudi Arabia (966) 🇰🇼 Kuwait (965) 🇶🇦 Qatar (974) 🇧🇭 Bahrain (973) MENA Region: 🇯🇴 Jordan (962) 🇪🇬 Egypt (20) 🇮🇶 Iraq (964) 🇱🇧 Lebanon (961) 🇸🇾 Syria (963) 🇵🇸 Palestine (970) 🇾🇪 Yemen (967) International: 🇺🇸 USA (1) 🇬🇧 UK (44) 🇩🇪 Germany (49) 🇫🇷 France (33) 🇮🇹 Italy (39) 🇪🇸 Spain (34) 🇹🇷 Turkey (90) 🇮🇳 India (91) 🇵🇰 Pakistan (92) Message Templates Arabic Message (عربي): مرحبًا [الاسم]، يسرّنا إعلامكم بأنه تم شحن طلبكم بنجاح. رقم الطلب: [order_id] رقم التتبع: [tracking_number] شركة الشحن: [courier_name] رابط التتبع: [tracking_url] المدة المتوقعة للتوصيل: من 7 إلى 12 يوم عمل. يمكنكم متابعة حالة الشحنة عبر رقم التتبع، وسنحرص على إبقائكم على اطلاع حتى استلام الطلب. مع أطيب التحيات، English Message: Hello [Name], We are pleased to inform you that your order has been shipped successfully. Order No: [order_id] Tracking No: [tracking_number] Courier Company: [courier_name] Tracking URL: [tracking_url] Estimated delivery time: 7–12 business days. You may track your shipment using the tracking number provided. We will continue to keep you informed until your order is delivered. Kind regards, Database Schema Requirements Orders Table: CREATE TABLE orders ( order_id VARCHAR PRIMARY KEY, -- Shopify order number status VARCHAR, -- Order status ('open', 'shipped', 'delivered', 'canceled') shipping_company VARCHAR, -- Courier service name tracking_number VARCHAR, -- Package tracking ID customer_id INTEGER -- Foreign key to customers table ); Customers Table: CREATE TABLE customers ( id SERIAL PRIMARY KEY, website_id INTEGER, -- Shopify customer ID phone VARCHAR, -- Customer phone number language VARCHAR(2), -- Preferred language ('ar' or 'en') first_name VARCHAR, -- Customer first name last_name VARCHAR -- Customer last name ); Phone Validator Logic The Phone Validator node intelligently handles phone numbers: Extracts phone from fulfillment data (checks destination.phone, shipping_address.phone, or root phone) Detects country from destination.country_code (defaults to 'OM' if not provided) Cleans number by removing whitespace and non-numeric characters (except +) Validates length (minimum 5 digits required) Checks for country code in the number Adds country code automatically if missing based on shipping country Ensures + prefix for international format Returns: phone: Formatted number with country code (+XXX) original_phone: Raw input for reference country_code: ISO country code validation_status: 'success' or 'empty_or_invalid' Customization Tips Add more countries**: Extend the countryCodes object in Phone Validator node Change brand name**: Update "" / "" in WhatsApp message nodes Adjust delivery time**: Modify "7–12 business days" to match your actual shipping times Add more languages**: Create additional language detection branches (e.g., French, Spanish) Include product details**: Extend database query to fetch order items and include in message Add delivery date estimates**: Calculate and include specific delivery date ranges Email notifications**: Add email nodes for customers who prefer email SMS fallback**: Add SMS nodes for customers without WhatsApp Use Cases E-commerce stores shipping to multiple countries Luxury brands requiring premium communication Businesses with Arabic and English speaking customers International retailers with GCC and MENA presence Multi-channel sellers needing unified shipping notifications Stores using various courier services (DHL, FedEx, Aramex, etc.) Error Handling Empty phone numbers**: Workflow marks as 'empty_or_invalid' and skips notification Invalid formats**: Phone validator attempts to fix common issues Missing data**: Uses fallback values (e.g., 'OM' for country, 'en' for language) SQL injection protection**: Single quotes escaped in database queries Test number blocking**: Prevents accidental notifications during testing Performance Notes Execution time**: ~2-3 seconds per order Database queries**: 3 total (1 UPDATE, 2 SELECT) API calls**: 1 WhatsApp message per order Scalability**: Handles concurrent fulfillments independently Rate limits**: WhatsApp Business API applies standard rate limits Technical Notes WhatsApp API Version: v18.0 Phone API format: Country code without '+' (e.g., 962798087441) Database: PostgreSQL with prepared statements Default country: Oman (+968) Default language: English if not specified Workflow processes one fulfillment at a time (runOnceForEachItem) Tags: #shopify #whatsapp #fulfillment #shipping #tracking #bilingual #arabic #english #phone-validation #ecommerce #notifications #international

📍Overview This no-code workflow is built for creators, agencies, and operators who want to automate the repurposing of Instagram Reels. It runs end-to-end and outputs structured insights and content-ready scripts—without touching a single tool manually. 🧰 What It Does Triggered simply by sending an Instagram Reel URL via Telegram. Downloads the Reel automatically. Converts video to audio using FreeConvert API. Transcribes speech to text using AssemblyAI. Analyzes both transcript and description using a connected LLM (OpenAI or Mistral). Extracts: Niche Core message 3 viral content hooks 3 ready-to-use short-form video scripts Saves all data to a Google Sheet for easy reuse by the creator or team. 🧪 APIs & Integrations Telegram Bot API (for triggering) FreeConvert API (MP4 to MP3 conversion) AssemblyAI (for transcription) OpenAI or Mistral (LLM for content analysis) Google Sheets API (for logging all outputs) ✅ Requirements An n8n instance (self-hosted or cloud) AssemblyAI API key FreeConvert API key Telegram Bot token Google service account credentials Your preferred LLM key (OpenAI or Mistral) 💡 Why Use This Workflow Runs entirely from Telegram—no dashboards required Helps you extract deep insights and reusable content from any Instagram Reel All tools used are free or very low cost Ideal for scaling personal brands or agency operations

Automated WhatsApp Welcome Messages for Sales Leads with Google Sheets & Rapiwa Who is this for? This automation is ideal for sales teams, digital marketers, support agents, or small business owners who collect leads in Google Sheets and want to automatically send WhatsApp welcome messages. It's a cost-effective and easy-to-use solution built for those not using the official WhatsApp Business API but still looking to scale communication. What this Workflow Does This n8n automation reads leads from a connected Google Sheet, verifies if the provided WhatsApp numbers are valid using the Rapiwa API, and sends a personalized welcome message. It updates the sheet based on delivery success or failure, and continues this process every 5 minutes — ensuring new leads are automatically engaged. Key Features Automatic Scheduling**: Runs every 5 minutes (adjustable) Google Sheets Integration**: Reads and updates lead data WhatsApp Number Validation**: Confirms number validity via Rapiwa Personalized Messaging**: Uses lead name for custom messages Batch Processing**: Sends up to 60 messages per cycle Safe API Usage**: Adds 5-second delay between each message Error Handling**: Marks failed messages as not sent and unverified Live Status Updates**: Sheet columns are updated after each attempt Loop Logic**: Repeats continuously to catch new rows How to Use Step-by-step Setup Prepare Your Google Sheet Copy this Sample Sheet Ensure it includes the following columns: WhatsApp No name (note: trailing space is required) row_number status, check, validity Connect Google Sheets in n8n Use OAuth2 credentials to allow n8n access Set the workflow to fetch rows where check is not empty Get a Rapiwa Account Sign up at https://rapiwa.com Add your WhatsApp number Retrieve your Bearer Token from your Rapiwa dashboard Configure HTTP Request Nodes Use Rapiwa's API endpoints: Verify Number: https://app.rapiwa.com/api/verify-whatsapp Send Message: https://app.rapiwa.com/api/send-message Add your Bearer Token to the header Start Your Workflow Run the n8n automation It will read leads, clean phone numbers, verify WhatsApp validity, send messages, and update the sheet accordingly Requirements A Google Sheet with correctly formatted columns Active Rapiwa subscription (~$5/month) A valid Bearer Token from Rapiwa Your WhatsApp number connected to Rapiwa n8n instance with: Google Sheets integration (OAuth2 setup) HTTP Request capability Google Sheet Column Reference | name | number | email | time | check | validity | status | |-----------------|--------------|-------------------|-----------------------------|---------|------------|-----------| | Abdul Mannan | 8801322827799| contact@spagreen.net| September 14th 2025, 10:34 | checked | verified | sent | | Abdul Mannan | 8801322827798| contact@spagreen.net| September 14th 2025, 10:34 | checked | unverified | not sent | Workflow Logic Summary Trigger Every 5 Minutes Fetch All Rows with Pending Status Limit to 60 Rows per Execution Clean and Format Phone Numbers Check Number Validity via Rapiwa Condition Check: If valid → Send Message If invalid → Update status as not sent, unverified Send WhatsApp Message via Rapiwa Update Sheet Row On success: sent, verified, checked On failure: not sent, unverified Delay 5 seconds before next message Repeat for next lead Customization Ideas Add image or document sending support via Rapiwa Customize messages based on additional fields (e.g., product, service) Log failures to a separate sheet Send admin email for failed batches Add support for multilingual messages Notes & Warnings The column name "name " includes a space — do not remove or rename it. International number format is required for Rapiwa to work correctly. If you're sending many messages, increase the Wait node delay to prevent API throttling. Support WhatsApp Support: Chat Now Discord: Join SpaGreen Community Facebook Group: SpaGreen Support Website: https://spagreen.net Developer Portfolio: Codecanyon SpaGreen

Quick Overview This workflow routes incoming WhatsApp home-service requests by using Groq to classify urgency and extract key details, logs every request to Supabase, and either alerts an on-call technician for emergencies or appends routine jobs to a Google Sheets queue while confirming the next steps to the customer. How it works Triggers when a new WhatsApp message is received via WhatsApp Business Cloud. Captures configuration values and pulls the customer’s message, name, and phone number from the inbound payload. Uses Groq to extract issue type, location, and a short description, and to classify the request as “emergency” or “routine.” Inserts the extracted request details into a Supabase table for record-keeping. If the request is an emergency, sends a WhatsApp alert to the on-call technician and a confirmation message back to the customer. If the request is routine, appends it to a Google Sheets service-queue row and sends the customer an acknowledgement with the expected response timeframe. Setup Connect WhatsApp Business Cloud credentials for the WhatsApp Trigger and all WhatsApp send steps, and configure your WhatsApp webhook in Meta to point to the trigger URL. Add a Groq API credential for the chat model used to extract and classify request details. Add a Supabase credential and create a service_requests table (customer_name, customer_number, issue_type, location, description, urgency, created_at with default now()). Add a Google Sheets OAuth credential and create a queue sheet with columns for status, location, issue_type, description, customer_name, and customer_number. Update the workflow configuration values for your WhatsApp phone number ID, on-call technician number, Google Sheet ID and sheet name, and the routine response window (days).

Overview When designing user interfaces, toolbar icons often get overlooked, even though their placement and grouping dramatically impact usability and user flow. This workflow leverages Gemini AI to automatically analyze UI screens, classify toolbar icons based on Apple’s Human Interface Guidelines (HIG), and suggest optimal placements. By combining AI analysis with structured placement logic, this workflow helps designers build more consistent, efficient, and user-friendly interfaces—without spending hours manually arranging icons. 🚀 Features AI Classification**: Uses Gemini AI to analyze screenshots and classify icons into roles like .primaryAction, .navigation, .confirmationAction, and more. HIG-Based Placement**: Automatically assigns icons to the correct toolbar areas—Leading (Left), Trailing (Right), Center, Bottom, or System-decided. Usage-Aware Reordering**: Reorders icons based on frequency of use so the most relevant actions appear where users expect them. JSON Output**: Delivers structured results for seamless integration into design tools or documentation. 🔧 Setup Instructions Install the Workflow: Import the workflow into your n8n instance. Configure Input: Upload a screenshot of your UI. Upload a set of icons you want to classify and place. Set Up Gemini AI Node: Add your Gemini AI API key in the node’s credentials. Run the Workflow: Submit the inputs and let the AI classify and assign placements. Export Results: Copy the JSON output or connect the workflow to your preferred design/documentation tools. ⚙️ How It Works Form Submission – Capture screenshot + icons. Gemini AI Agent – Interprets screen context and classifies each icon. Placement Logic – Maps icons to the correct toolbar areas. Reordering – Adjusts order based on relevance and HIG standards. Structured Output – Produces clean JSON for further use. 🎨 Customization Change AI Prompts**: Modify the Gemini AI node prompts to reflect your app’s design language. Adjust Placement Rules**: Update logic to follow custom guidelines beyond Apple HIG. Integrate with Design Tools**: Send the JSON output directly to tools like Figma, Sketch, or internal systems. 💡 Why This Matters Consistency**: Ensures toolbar designs always follow Apple’s HIG. Efficiency**: Saves designers hours of manual icon placement. Scalability**: Works across multiple screens, flows, and apps. AI-Assisted Design**: Augments designer decisions with structured insights instead of replacing them.