by Jitesh Dugar
Empower your property management with a high-efficiency automated support desk. This workflow manages the complete maintenance lifecycle—from initial issue classification and ticket creation to team assignment, status updates, and tenant feedback—all centralized through WhatsApp using WATI and Google Sheets. 🎯 What This Workflow Does Turns WhatsApp into an intelligent bridge between tenants, maintenance teams, and landlords: 📝 Instant Ticket Creation Tenants can report any property issue via WhatsApp. The system automatically classifies the problem (Plumbing, Electrical, etc.) and assigns a priority level based on keywords. 🚦 Smart Command Routing A master switch node handles incoming messages based on intent: New Issue: Classifies and logs a new ticket. update <id> <status>: Allows maintenance teams to update progress. rate <id> <1-5>: Captures tenant satisfaction scores. mystatus: Provides tenants a view of their active tickets. dashboard: Gives landlords an overview of property health. 🛠️ Maintenance Coordination Simultaneously notifies the tenant of their Ticket ID and pings the relevant maintenance team with full issue details and an SLA deadline. 🚨 Proactive SLA Monitoring A daily morning trigger scans all open tickets for SLA breaches (e.g., High Priority overdue after 4 hours) and alerts the landlord and teams for immediate action. ✨ Key Features Keyword Intelligence:** Uses built-in logic to detect urgent issues like "leak" or "no power" and auto-flags them as High Priority. Team Mapping:** Automatically routes requests to specific teams (Plumbing, Electrical, Structural) based on the detected category. Service Rating Loop:** Automatically prompts tenants for a 1-5 star rating once a ticket is marked "resolved," logging feedback directly for the landlord. Property Dashboard:** Landlords receive a visual summary including total open tickets, average ratings, and category breakdowns. Audit Trail:** Every status change and team note is timestamped and saved in the lastUpdated column in Google Sheets. 💼 Perfect For Property Managers:** Handling requests for multiple buildings without a manual call center. Landlords:** Keeping a transparent, timestamped record of all repairs and contractor performance. Facility Management Firms:** Coordinating various specialized technical teams across different sites. Co-living Spaces:** Providing a modern, mobile-first support experience for young professional tenants. 🔧 What You'll Need Required Integrations WATI** – To receive tenant issues and send status updates to all parties. Google Sheets** – To act as your centralized ticket database and landlord dashboard. Optional Customizations Photo Evidence:** Add a node to allow tenants to upload photos of the damage to be saved in a Google Drive folder. AI Summarization:** Integrate OpenAI to summarize long tenant descriptions for quicker team review. 🚀 Quick Start Import Template – Copy the JSON and import it into your n8n instance. Set Credentials – Connect your WATI and Google Sheets accounts. Configure Teams – Edit the teamMap in the Classify Issue node to include your contractors' actual WhatsApp numbers. Configure Sheets – Ensure your Google Sheet has a Tickets tab with headers: ticketId, phone, tenantName, issueText, category, priority, status, assignedTeam, teamPhone, createdAt, slaDueAt, rating, lastUpdated, notes Test the Loop – Send "My sink is leaking" to your WATI number, then use a team number to reply update <ID> in-progress. 📈 Expected Results Zero manual routing: Issues reach the right technician without administrative intervention. Improved transparency: Tenants are never "left in the dark" about the status of their repairs. Data-driven management: Identify recurring structural issues and underperforming teams via the dashboard. Accountability: SLA breach alerts ensure no emergency ticket is forgotten. Ready to simplify your property management? Import this template and connect your Google Sheets to start tracking maintenance requests today!
by Jitesh Dugar
💊 WhatsApp Medication Adherence & Caregiver Alert Automation Ensure health and safety with a fully automated medication adherence system. This workflow manages the entire patient care cycle—from scheduled dosage reminders to interactive logging and automated caregiver escalations—all through WhatsApp using WATI and Google Sheets. 🎯 What This Workflow Does Turns WhatsApp into a proactive health assistant and caregiver's dashboard: 📝 Timed Dosage Reminders A scheduled trigger fires 3x daily (Morning, Afternoon, Night) to identify which medications are due and send personalized WhatsApp alerts. 🚦 Smart Patient Routing A Switch node detects patient replies to manage their health data in real-time: taken: Logs the dose as complete and updates the patient's "Streak". skip: Records the skipped dose and empathetic feedback while checking for consecutive skips. snooze: Schedules a 30-minute follow-up reminder. mystats: Generates a 7-day adherence report with visual progress bars. mymeds: Provides the full daily medication schedule and instructions. 👁️ Automated Caregiver Alerts An hourly check detects "Pending" reminders. If a patient hasn't responded within 2 hours, the bot automatically alerts the designated caregiver via WhatsApp. 📊 Comprehensive Analytics Caregivers can request a full patient report (e.g., report <phone>) to view a categorized summary of taken vs. missed doses. ✨ Key Features Slot-Based Intelligence:** Automatically determines if it is Morning, Afternoon, or Night to send only relevant medications. Gamified Adherence:** Tracks "Streaks" (consecutive days taken) with motivational emojis to encourage patient consistency. Visual Bar Charts:** Patients and caregivers receive structured reports using visual bars (███░░) to show adherence percentages. Temporary Snooze Queue:** Uses a dedicated "SnoozeQueue" tab to ensure follow-up reminders aren't forgotten. Proactive Safety:** Built-in logic to detect 2+ consecutive skips, alerting caregivers before it becomes a health risk. 💼 Perfect For Elderly Care:** Providing automated support for seniors managing multiple daily medications. Chronic Condition Management:** Ensuring strict adherence for long-term treatments like hypertension or diabetes. Home Healthcare Agencies:** Scaling patient monitoring without increasing manual staff check-ins. Clinical Trials:** Tracking participant adherence with a digital, timestamped audit trail. 🔧 What You'll Need Required Integrations WATI** – To deliver medication reminders and process patient responses. Google Sheets** – To store the master medication list, adherence logs, and snooze queue. Optional Customizations AI Analysis:** Integrate OpenAI to answer patient questions about specific medication side effects. Emergency Escalation:** Add a voice call node if a high-priority medication is missed 3 times in a row. 🚀 Quick Start Import Template – Copy the JSON and import it into your n8n instance. Set Credentials – Connect your WATI and Google Sheets accounts. Configure Sheets – Ensure your Google Sheet has three tabs: Medications: phone, patientName, medName, dosage, frequency, timeSlots, status, caregiverPhone AdherenceLog: logKey, phone, patientName, date, slot, status, sentAt, respondedAt, caregiverPhone SnoozeQueue: phone, patientName, followUpAt, snoozedAt, status Test Reminders – Add a test row to your sheet and manually trigger the 8 AM node. Simulate a Reply – Reply taken or mystats to your WATI number to see your report generated live. 🎨 Customization Options Custom Time Windows:** Modify the Filter Medications by Time Slot code to align with specific clinic hours. Empathetic Messaging:** Customize the reinforce messages in the Process Taken and Process Skip nodes to match your brand voice. Adherence Thresholds:** Adjust the caregiver alert logic to trigger after 1 hour or 4 hours depending on medication sensitivity. 📈 Expected Results 95% adherence transparency for caregivers and family members. Reduced health risks by identifying missed doses within a 2-hour window. Improved patient morale through positive streak reinforcement and visual progress. Efficient monitoring: One caregiver can monitor dozens of patients through a single WhatsApp interface. Ready to launch your digital health assistant? Import this template and connect your Google Sheets to start improving patient adherence today!
by Luis Hernandez
GLPI Pending Tickets Notification to Microsoft Teams 📋 Overview Automate daily notifications for pending GLPI tickets directly to Microsoft Teams. Never miss critical support cases with this workflow that monitors assigned tickets and sends personal alerts. 🔧 How It Works Connect to GLPI - Authenticates and searches for your assigned tickets Filter Results - Finds tickets in "In Progress" status within your entity Send Notifications - Delivers formatted alerts to your Teams chat Clean Up - Properly closes GLPI session for security 📊 What Gets Monitored Tickets assigned to specific technician (configurable) Status: "In Progress/Assigned" Entity: Your organization (customizable) Date range: Tickets after specified date ⚡ Key Benefits Never Miss Deadlines - Daily automated reminders Personal Focus - Only your assigned tickets Time Savings - Eliminates manual checking (15-30 min daily) Rich Details - Shows ticket title, ID, and due date ⚙️ Setup Steps Time Required: ~30 minutes Import Template - Add workflow to your n8n instance Configure GLPI - Set server URL, credentials, and app token Set Technician ID - Update to your GLPI user ID Connect Teams - Link your Microsoft Teams account Customize Filters - Adjust entity name and date range Test & Schedule - Verify notifications and set daily trigger 🎨 Easy Customization Change technician ID for different users Adjust notification schedule (default: 8 AM daily) Modify entity filters for your organization Add multiple technicians by duplicating workflow 📋 Prerequisites GLPI instance with API enabled GLPI user account with ticket read permissions Microsoft Teams account (basic license) n8n with Microsoft Teams integration Perfect for support technicians who want automated reminders about their pending GLPI tickets without manual daily checks.
by Pixcels Themes
Who’s it for This template is for teams using n8n in production who want immediate visibility into workflow failures. It’s ideal for DevOps teams, automation engineers, and operations teams who need reliable error monitoring, alerting, and historical logs without building custom observability tooling. What it does / How it works This workflow automatically captures and logs errors whenever any other n8n workflow fails. Here’s how it works: The Error Trigger node activates automatically when a workflow execution fails. It captures key error details: Workflow name Execution URL Last node executed Error message A formatted alert message is generated. The error summary is immediately sent to a designated slack channel for real-time visibility. At the same time, the full error details are appended as a new row in a Google Sheets document for long-term tracking and analysis. All of this runs automatically with no manual intervention. Requirements To use this workflow, you’ll need: Slack API credentials Google Sheets OAuth2 credentials A Slack channel for workflow alerts (e.g. #alerts-n8n-workflows) A Google Sheet with columns for: Workflow name Execution URL Node name Error message How to set up Import this workflow into your n8n instance. Connect your Slack credentials in the Slack node. Select the Slack channel where alerts should be sent. Connect your Google Sheets credentials. Replace the Google Sheet ID with your own error log sheet. Ensure the column mappings match your sheet structure. Activate the workflow. Once enabled, it will automatically monitor all workflows for failures. How to customize the workflow You can easily adapt this template to your needs: Change the Slack message format in the Set message node. Log additional metadata (execution time, environment, tags, etc.). Add more notification channels (Email, PagerDuty, Microsoft Teams). Extend logging to databases or observability tools. Why use this template 🚀 Instant visibility into workflow failures 🧠 Centralized error history for debugging and audits 🔁 Fully automated, no manual checks required 🛠️ Easy to extend as your automation stack grows This template helps you keep your n8n automations reliable, observable, and production-ready.
by Kirill Khatkevich
This workflow is a production-ready Meta Ads Webhook dispatcher for the Ad Account object. It receives webhook deliveries from Meta, returns the required acknowledgement, routes events by field, logs them to Google Sheets (separate tabs per event type), and sends a compact Slack notification with counts. Use Case Meta webhooks are powerful, but the “last mile” is usually missing: storing raw events, making them readable, and triggering the next automation reliably. This workflow is ideal if you want to: Centralize all Meta Ads webhook events** in one place (one endpoint, one workflow). Log every event** for auditing and analysis (Google Sheets). Get lightweight alerts** in Slack (count-based, not spammy). Trigger downstream workflows** depending on the webhook type (e.g., Creative Fatigue → replace creatives in the affected ad set). How it Works The workflow is organized into clear blocks: 1. Webhook endpoint + verification A Webhook trigger receives requests from Meta. The workflow detects verification requests (hub.mode=subscribe) and validates the Verify Token. It responds with the hub.challenge value so you can successfully subscribe your webhook in Facebook Developers. 2. Route by event field For real webhook deliveries (object=ad_account), the workflow routes execution by: creative_fatigue ad_recommendations ads_async_creation_request in_process_ad_objects product_set_issue with_issues_ad_objects 3. Acknowledge every webhook delivery For each branch, the workflow immediately returns a JSON acknowledgement (e.g., { "status": "received", "field": "...", "webhook_type": "..." }), so Meta considers the delivery successful. 4. Normalize + log to Google Sheets The workflow splits array payloads (Meta can send multiple entry items and multiple changes). Each event type is appended to its own Google Sheets tab (one spreadsheet, multiple sheets), with the raw webhook body also saved for future debugging. 5. Summarize + notify All event logs are merged and summarized to compute a compact count per field. A Slack node sends a short message like “New Meta Webhook / Type / Count” with a link to the spreadsheet. Setup Instructions 1. Create and configure a Meta app Create an app in Facebook Developers. Add the Webhooks product. Subscribe to the Ad Account object. Configure: Callback URL (your n8n webhook URL) Verify Token (must match the value in the workflow) 2. Configure the Webhook node Set the webhook path. Use the Production URL when you go live. 3. Connect credentials Connect Google Sheets OAuth credentials in all Google Sheets nodes. Connect Slack credentials and choose your target channel. 4. Update Google Sheets destinations Set your Spreadsheet ID and ensure the expected sheet tabs exist (one per supported webhook field). 5. Activate Save and activate the workflow. Trigger a verification request from Facebook Developers to confirm everything is wired correctly. Testing To test the dispatcher before going live, use the open-source tool: meta-ads-webhook-tester. Further Ideas & Customization Add Telegram**: duplicate the Slack notification step and send the same summary message to Telegram. Trigger automations**: after routing by field, execute another workflow (e.g., Creative Fatigue → fetch affected ad set → rotate creatives). Hardening**: add de-duplication (event IDs), retries, and a dead-letter/error sheet tab for failed log writes.
by Ehsan
Who's it for This template is for sales teams, marketing operations (M-Ops), or freelancers who use Airtable as a "control panel" or staging area for new leads. If you're tired of manually copying and pasting approved leads into HubSpot, this workflow automates the entire process for you. How it works This workflow runs on a schedule (e.g., every 5 minutes) to check for new leads. 1. Before: Your Airtable has new leads with a '📥 New Lead' status. 2. The Trigger: You (or a teammate) manually review and change a lead's status to '👍 Ready to Sync'. 3. The Workflow Runs: n8n fetches all leads in that view (up to 50 at a time) and loops through them one by one. For each lead, it: Finds (or creates) a Company in HubSpot based on the email domain. Creates (or updates) a Contact in HubSpot based on the email. Automatically associates that Contact with that Company. 4. After: The workflow automatically updates the same Airtable row with the new HubSpot IDs and a '✅ Synced' status, completing the 2-way sync. This template includes a full batch-processing loop, robust error-handling (it logs failures back to Airtable), and detailed sticky notes to guide you. How to set up Setup should take less than 10 minutes. All detailed instructions are in the sticky notes inside the workflow. Copy the Airtable Base: This is a mandatory first step! You must use this template. ➡️ Click Here to Copy the Base Template (First time using Airtable? Sign up here with my link) Add Your Credentials: How to connect Airtable to n8n (Video) How to connect HubSpot to n8n (Video) Configure 3 Nodes: Schedule Trigger: Set how often you want it to run (e.g., every 5 minutes). get 👍Ready to Sync: Select your Airtable credential and the Base you copied. Also, Do this for the other Airtable nodes. Search company: Select your HubSpot credential. Also, Do this for the othe HubSpot nodes. Activate! Save and activate the workflow. To test it, just change a lead's 'Status' in Airtable to '👍 Ready to Sync'. Requirements An Airtable account. A HubSpot account (a free developer sandbox account is recommended for testing). n8n credentials for both Airtable and HubSpot (using a Private App Token for HubSpot). How to customize the workflow Add More Fields:** Easily sync more data (like 'Phone Number' or 'Lead Source') by adding columns in your Airtable, then adding those fields to the Create or update a contact node in n8n. Change the Schedule:** Adjust the Schedule Trigger to run more or less frequently. Add Notifications:** Connect a Slack or email node to the 👍Done! Going for next record (success) or specially 👎Failed! Going for next record1 (error) paths to get real-time alerts.
by Sk developer
📊 TikTok Account Monitoring Automation This n8n workflow automates the daily process of fetching TikTok account analytics using the TikTok API and logging the results to Google Sheets. It helps marketing teams, social media managers, and influencer agencies track video performance and audience growth across multiple TikTok usernames without manual effort. 🔁 Workflow Summary ⏰ Trigger via Schedule The workflow runs automatically every day (or any custom interval), ensuring data is consistently updated without manual input. 📥 Sheet 1 – Read TikTok Usernames A Google Sheet stores the list of TikTok usernames you want to monitor. ✅ Example Columns: username category priority notes 🔁 Loop Through Each Username Each username is processed individually in a loop to make separate API calls and avoid data conflicts. 📡 Fetch Analytics via RapidAPI The following TikTok API endpoint is used: POST https://tiktok-api42.p.rapidapi.com/videos_view_count.php You get per-user stats like: Number of videos Total views Recent video views This endpoint is highly stable and works without TikTok login or auth. 📤 Sheet 2 – Append Analytics Results Fetched data is logged in another Google Sheet for performance tracking. ✅ Example Columns: username total_videos total_views average_views fetch_date category 📦 Sheet 3 – Log API History or Errors A third sheet stores logs of API fetch status, failures, or skipped usernames for debugging. ✅ Example Columns: username status (e.g., success, failed, skipped) message timestamp 🔐 RapidAPI Notes You must have an API key from TikTok API All requests are made to https://tiktok-api42.p.rapidapi.com The main endpoint in use is: POST https://tiktok-api42.p.rapidapi.com/videos_view_count.php Each request uses POST with params like username, region, number The response is JSON and easy to parse in n8n workflows 📌 Optional Extensions (Same API, More Insights) This same TikTok API also supports other advanced endpoints that can be added to enrich your workflow: | Endpoint Name | Functionality | |---------------------------|------------------------------------------------------------------| | User Profile Data | Get bio, profile image, followers, likes, etc. | | User Account Stats | Extract detailed user metrics (likes, comments, shares) | | User Audience Stats | Know where their followers are from and gender split | | Historical Data | Track historical performance trends (useful for growth charts) | | HashTags Scraper | Find trending or related hashtags used by the user | | Related User Info | Suggest accounts similar to the one queried | | Videos Views Counts | Already used to get view stats for multiple videos | Each of these can be added using HTTP Request nodes in n8n and plugged into the same sheet or separate ones. ✅ Benefits 🔄 Fully Automated: No manual copy-paste or login required 📊 Centralized Analytics: Track all creators or clients in one dashboard 📈 Performance Insights: Daily growth visibility with historical tracking 📤 Data Export Ready: Stored in Google Sheets for easy share/report/export 🔧 Scalable & Flexible: Add hashtags, followers, or audience demographics 🧠 Use Cases Influencer Agencies** tracking clients' TikTok growth daily Brands running UGC Campaigns** who want to monitor video traction Analysts** building dashboards from Sheet-to-DataStudio/Looker Marketers** analyzing viral trends or creators across niches 📌 Final Note This workflow is extendable. You can: Merge multiple endpoints per user Schedule it weekly or monthly Send email summaries Push to Slack or Google Data Studio > API Used in this workflow: > TikTok API
by Milan Vasarhelyi - SmoothWork
Video Introduction Want to automate your inbox or need a custom workflow? 📞 Book a Call | 💬 DM me on Linkedin Overview This workflow automatically sends personalized SMS notifications to customers when their order status changes in Airtable. Monitor your order management base and instantly notify customers about updates like "Confirmed" or "Shipped" without manual intervention. When an order status changes in your Orders table, a notification record is automatically created in a Status Notifications table. The workflow monitors this table, prepares personalized messages using the customer's name and order status, sends the SMS via Twilio, and updates the delivery status back to Airtable for complete tracking and logging. Key Features Automated SMS sending triggered by Airtable record changes Personalized messages with customer name and order status Complete delivery tracking with success/error status updates Error handling for invalid phone numbers Works with Twilio's free trial account for testing Common Use Cases E-commerce order status updates Shipping notifications Order confirmation messages Customer communication logging Setup Instructions Step 1: Duplicate the Airtable Base Copy the Order Management Base template to your Airtable workspace. You must use your own copy as the workflow needs write permissions. Step 2: Connect Your Accounts Add your Airtable Personal Access Token credentials to the workflow nodes Create a Twilio account (free trial available) From your Twilio dashboard, obtain your Account SID, Auth Token, and Twilio phone number Add Twilio credentials to the "Send Order Status SMS" node Step 3: Configure the Workflow In the Config node, update these URLs with your duplicated Airtable base: notifications_table_url: Your Status Notifications table URL orders_table_url: Your Orders table URL from_number: Your Twilio phone number Step 4: Customize the Message Modify the "Prepare SMS Content" node to personalize the message template with your brand voice and additional order details. Step 5: Activate Toggle the workflow to 'Active' and the automation will monitor your Airtable base every minute, sending notifications automatically.
by Marth
How It Works: The 5-Node Monitoring Flow This concise workflow efficiently captures, filters, and delivers crucial cybersecurity-related mentions. 1. Monitor: Cybersecurity Keywords (X/Twitter Trigger) This is the entry point of your workflow. It actively searches X (formerly Twitter) for tweets containing the specific keywords you define. Function:** Continuously polls X for tweets that match your specified queries (e.g., your company name, "Log4j," "CVE-2024-XXXX," "ransomware"). Process:** As soon as a matching tweet is found, it triggers the workflow to begin processing that information. 2. Format Notification (Code Node) This node prepares the raw tweet data, transforming it into a clean, actionable message for your alerts. Function:** Extracts key details from the raw tweet and structures them into a clear, concise message. Process:** It pulls out the tweet's text, the user's handle (@screen_name), and the direct URL to the tweet. These pieces are then combined into a user-friendly notificationMessage. You can also include basic filtering logic here if needed. 3. Valid Mention? (If Node) This node acts as a quick filter to help reduce noise and prevent irrelevant alerts from reaching your team. Function:** Serves as a simple conditional check to validate the mention's relevance. Process:** It evaluates the notificationMessage against specific criteria (e.g., ensuring it doesn't contain common spam words like "bot"). If the mention passes this basic validation, the workflow continues. Otherwise, it quietly ends for that particular tweet. 4. Send Notification (Slack Node) This is the delivery mechanism for your alerts, ensuring your team receives instant, visible notifications. Function:** Delivers the formatted alert message directly to your designated communication channel. Process:* The notificationMessage is sent straight to your specified *Slack channel** (e.g., #cyber-alerts or #security-ops). 5. End Workflow (No-Op Node) This node simply marks the successful completion of the workflow's execution path. Function:** Indicates the end of the workflow's process for a given trigger. How to Set Up Implementing this simple cybersecurity monitor in your n8n instance is quick and straightforward. 1. Prepare Your Credentials Before building the workflow, ensure all necessary accounts are set up and their respective credentials are ready for n8n. X (Twitter) API:* You'll need an X (Twitter) developer account to create an application and obtain your Consumer Key/Secret and Access Token/Secret. Use these to set up your *Twitter credential** in n8n. Slack API:* Set up your *Slack credential* in n8n. You'll also need the *Channel ID** of the Slack channel where you want your security alerts to be posted (e.g., #security-alerts or #it-ops). 2. Import the Workflow JSON Get the workflow structure into your n8n instance. Import:** In your n8n instance, go to the "Workflows" section. Click the "New" or "+" icon, then select "Import from JSON." Paste the provided JSON code (from the previous response) into the import dialog and import the workflow. 3. Configure the Nodes Customize the imported workflow to fit your specific monitoring needs. Monitor: Cybersecurity Keywords (X/Twitter):** Click on this node. Select your newly created Twitter Credential. CRITICAL: Modify the "Query" parameter to include your specific brand names, relevant CVEs, or general cybersecurity terms. For example: "YourCompany" OR "CVE-2024-1234" OR "phishing alert". Use OR to combine multiple terms. Send Notification (Slack):** Click on this node. Select your Slack Credential. Replace "YOUR_SLACK_CHANNEL_ID" with the actual Channel ID you noted earlier for your security alerts. (Optional: You can adjust the "Valid Mention?" node's condition if you find specific patterns of false positives in your search results that you want to filter out.) 4. Test and Activate Verify that your workflow is working correctly before setting it live. Manual Test:** Click the "Test Workflow" button (usually in the top right corner of the n8n editor). This will execute the workflow once. Verify Output:** Check your specified Slack channel to confirm that any detected mentions are sent as notifications in the correct format. If no matching tweets are found, you won't see a notification, which is expected. Activate:** Once you're satisfied with the test results, toggle the "Active" switch (usually in the top right corner of the n8n editor) to ON. Your workflow will then automatically monitor X (Twitter) at the specified polling interval.
by Nima Salimi
🧠 Automated SEO Keyword and SERP Analysis with DataForSEO for High-Converting Content | n8n workflow template Overview 🌐 This is a complete SEO automation workflow built for professionals who want to manage all their DataForSEO operations inside n8n — no coding required ⚙️ You can easily choose your operator (action), such as: 🔍 SERP Analysis – Get ranking data for specific keywords 📈 Keyword Data – Retrieve search volume, CPC, and trends 🧠 Competitor Research – Analyze which domains dominate target queries Once the workflow runs, it automatically creates a new Google Sheet 📊 (if it doesn’t exist) and appends the results — including metrics like keyword, rank, domain, and date — to keep a growing historical record of your SEO data 📅 💡 Ideal for SEO specialists, agencies, and growth teams who want a single automation to handle all keyword and ranking data pipelines using DataForSEO + Google Sheets + n8n. Examples related keyword sheet Each operator (SERP, Keywords Data, Competitors) automatically creates a separate Google Sheet 📊 👤 Who’s it for? 🧩 SEO Specialists who need accurate keyword & SERP insights daily ✍️ Content Marketers planning new blog posts or landing pages 📊 Digital Marketing Teams tracking top-performing keywords and competitors 💼 Agencies managing multiple websites or niches with automated reports 🧠 AI-Driven SEOs building GPT-powered content strategies using live ranking data ⚙️ How It Works Trigger & Input Setup Start the workflow manually or schedule it to run daily / weekly 🕒 Import a keyword list from Google Sheets 📄, NocoDB, or an internal database Keyword Data Retrieval (DataForSEO Keyword API) Sends requests to the keywords_data endpoint of DataForSEO Gathers search volume, CPC, competition level, and trend data Identifies the most promising keywords for conversion-focused content SERP Analysis (DataForSEO SERP API) Fetches the top organic results for each keyword Extracts domains, titles, snippets, and ranking positions Highlights which competitors dominate the search landscape Data Enrichment & Filtering Uses Code nodes to clean and normalize the DataForSEO JSON output Filters out low-intent or irrelevant keywords automatically Optionally integrates OpenAI or GPT nodes for insight generation ✨ Store & Visualize Saves results into Google Sheets, Airtable, or NocoDB for tracking Each run adds fresh data, building a performance history over time 📈 Optional AI Layer (Advanced) Use OpenAI Chat Model to summarize SERP insights: > “Top 3 competitors for cloud storage pricing focus on cost transparency — recommend including pricing tables.” Automatically generate content briefs or keyword clusters 🧩 Workflow Highlights ⚡ Multiple DataForSEO Endpoints Supported (keywords_data, serp, competitors) 🔁 Automated Scheduling for daily / weekly updates 🧠 Data Normalization for clean, structured SEO metrics 📊 Easy Export to Google Sheets or NocoDB 🧩 Expandable Design — integrate GPT, Google Search Console, or Analytics 🌎 Multi-Language & Multi-Location Support via language_code and location_code 📊 Example Output (Google Sheets) | keyword | rank | domain | volume | cpc | competition | date | |----------|------|----------------|---------|---------|---------------|------------| | cloud hosting | 1 | cloud.google.com | 18,100 | $2.40 | 0.62 | 2025-10-25 | | cloud server | 3 | aws.amazon.com | 12,900 | $3.10 | 0.75 | 2025-10-25 | | hybrid cloud | 5 | vmware.com | 9,800 | $2.90 | 0.58 | 2025-10-25 | Each run appends new keyword metrics for trend and performance tracking. 💡 Pro Tips 🔍 Combine this workflow with Google Search Console for even richer insights ⚙️ Adjust the location_code and language_code for local SEO targeting 💬 Add a Slack or Gmail alert to receive weekly keyword opportunity reports 🤖 Extend with OpenAI to automatically create content briefs or topic clusters 📚 Integrations Used 🧭 DataForSEO API – Keyword & SERP data source 📄 Google Sheets / Airtable / NocoDB – Storage and visualization 🤖 OpenAI Chat Model (optional) – Insight generation and summarization ⚙️ Code Nodes – JSON parsing and custom data processing ✅ Features 🌎 Choose from 100+ Locations Select your target country, region, or city using the location_code parameter. Perfect for local SEO tracking or multi-market analysis. 🗣️ Choose from 50+ Languages Define the language_code to get accurate, language-specific keyword and SERP data. Supports English (en), Spanish (es), French (fr), German (de), and more. 📊 Auto-Creates Google Sheets for You No need to manually set up a spreadsheet — the workflow automatically creates a new Google Sheet (if it doesn’t exist) and structures it with the right columns (query, rank, domain, date, etc.). 🔁 Append New Data Automatically Every run adds fresh SEO metrics to your sheet, building a continuous daily or weekly ranking history. ⚙️ Flexible Operator Selection Choose which DataForSEO operator (action) you want to run: keywords_data, serp, or competitors. Each operator retrieves a different type of SEO insight. 🧠 Fully Expandable Add Slack alerts, Airtable sync, or AI summaries using OpenAI — all within the same workflow. ⚙️ How to Set Up 🔑 Add DataForSEO Credentials Get your API login from dataforseo.com Add it under HTTP Request → Basic Auth in n8n 📄 Connect Google Sheets Authorize your Google account The workflow will auto-create the sheet if it doesn’t exist 🎛 Choose Operator (Action) Pick one: serp, keywords_data, or competitors Each operator runs a different SEO analysis 🌍 Set Location & Language Example: location_code: 2840 (US), language_code: en 🕒 Run or Schedule Trigger manually or set a daily schedule New results will append to your Google Sheet automatically 📺 Check Out My Channel 💬 Learn more about SEO Automation, n8n, and AI-powered content workflows 👉 Connect with me on LinkedIn: Nima Salimi Follow for more templates, AI workflows, and SEO automation tutorials 💥
by Milan Vasarhelyi - SmoothWork
Video Introduction Want to automate your inbox or need a custom workflow? 📞 Book a Call | 💬 DM me on Linkedin Overview This workflow automatically exports customer balance data from QuickBooks to Google Sheets on a monthly basis. It eliminates manual data entry and creates a historical record of customer balances that updates automatically, making it easy to track payment trends, identify outstanding balances, and monitor customer financial health over time. Key Features Automated Monthly Reporting**: Runs on the first day of each month to capture a snapshot of all customer balances Clean Data Structure**: Extracts only the essential fields (Customer ID, Balance, Email, and Period) for easy analysis Historical Tracking**: Each monthly run appends new data to your Google Sheet, building a timeline of customer balances No Manual Work**: Once configured, the workflow runs completely hands-free Common Use Cases Track customer payment patterns and identify accounts with growing balances Create monthly reports for management or finance teams Build dashboards and visualizations from historical QuickBooks data Monitor customer account health without logging into QuickBooks Setup Requirements QuickBooks Developer Account: Register at developer.intuit.com and create a new app in the App Dashboard. Select the 'Accounting' scope for permissions. You'll receive a Client ID and Client Secret to configure your n8n credentials. Credentials: Set up QuickBooks OAuth2 credentials in n8n using your app's Client ID and Client Secret. Use 'Sandbox' environment for testing or 'Production' for live data (requires Intuit app approval). Also connect your Google Sheets account. Google Sheet: Create a spreadsheet with column headers matching the workflow output: Period, Id, Balance, and Email. Configuration Schedule**: The workflow runs monthly on the first day at 8 AM. Modify the Schedule Trigger to change timing or frequency Spreadsheet URL**: Update the 'Export to Google Sheets' node with your destination spreadsheet URL Data Fields**: Customize the 'Prepare Customer Data' node to extract different customer fields if needed
by Mohammed Abid
Shopify Order Data to Airtable This n8n template demonstrates how to capture incoming Shopify order webhooks, transform the data into a structured format, and insert each product line item as a separate record in an Airtable sheet. It provides both high-level order information and detailed product-level metrics, making it ideal for analytics, reporting, inventory management, and customer insights. Good to Know Airtable API Rate Limits: By default, Airtable allows 5 requests per second per base. Consider batching or adding delays if you process high volumes of orders. Shopify Webhook Configuration: Ensure you have configured the orders/create webhook in your Shopify Admin to point to the n8n webhook node. Field Mapping: The template maps standard Shopify fields; if your store uses custom order or line item properties, update the Function nodes accordingly. How It Works Webhook Trigger: A Shopify orders/create webhook fires when a new order is placed. Normalize Order Data: The Function node extracts core order, customer, shipping, and billing details and computes financial totals (subtotal, tax, shipping, discounts). Line Item Breakdown: A second Function node builds an array of objects—one per line item—calculating per-item totals, tax/shipping allocation, and product attributes (color, size, material). Check Customer Record: Optionally check against an Airtable "Customers" sheet to flag new vs existing customers. Auto-Increment Record ID: A Function node generates a running serial number for each Airtable record. Insert Records: The Airtable node writes each line item object into the target base and table, creating rich records with both order-level and product-level details. How to Use Clone the Template: Click "Use Template" in your n8n instance to import this workflow. Configure Credentials: Shopify Trigger: Add your Shopify store domain and webhook secret. Airtable Node: Set up your Airtable API key and select the base and table. Review Field Names: Match the field names in the Function nodes to the columns in your Airtable table. Activate Workflow: Turn on the workflow and place a test order in your Shopify store. Verify Records: Check your Airtable sheet to see the new order and its line items. Requirements n8n@latest Shopify Store with orders/create webhook configured Airtable Account with a base and table ready to receive records Customizing This Workflow Add Custom Fields: Extend the Functions to include additional Shopify metafields, discounts, or customer tags. Alternative Destinations: Replace the Airtable node with Google Sheets, Supabase, or another database by swapping in the corresponding node. Error Handling: Insert If/Wait nodes to retry on API failures or send notifications on errors. Multi-Currency Support: Adapt the currency logic to convert totals based on dynamic exchange rates.