HumationHuman + Automation
Back to Catalog

Monitor SEO keyword rankings with SERP API & send drop alerts via Slack

Oneclick AI SquadOneclick AI Squad
391 views
2/3/2026
CloudinaryStable DiffusionWebhookAI Image GenerationOpenRouter
Official Page

This automated workflow monitors your website's keyword rankings daily and sends instant alerts to your team when significant ranking drops occur. It fetches current ranking positions, compares them with historical data, and triggers notifications through Slack and email when keywords drop beyond your defined threshold.

Good to know

  • The workflow uses SERP API for accurate ranking data; API costs apply based on your usage volume
  • Ranking checks are performed daily to avoid overwhelming search engines with requests
  • The system tracks ranking changes over time and maintains historical data for trend analysis
  • Slack integration requires workspace permissions and proper bot configuration
  • False positives may occur due to personalized search results or data center variations

How it works

  • Daily SEO Check Trigger initiates the workflow on a scheduled basis
  • Get Keywords Database retrieves your keyword list and current ranking data
  • Filter Active Keywords Only processes only keywords marked as active for monitoring
  • Fetch Google Rankings via SERP API gets current ranking positions for each keyword
  • Wait For Response Wait for gets current ranking positions
  • Parse Rankings & Detect Changes compares new rankings with historical data and identifies significant drops
  • Filter Significant Ranking Drops isolates keywords that dropped beyond your threshold (e.g., 5+ positions)
  • Send Slack Ranking Alert notifies your team channel about ranking drops
  • Send Email Ranking Alert sends detailed email reports to stakeholders
  • Update Rankings in Google Sheet saves new ranking data for historical tracking
  • Generate SEO Monitoring Summary creates a comprehensive report of all ranking changes

How to use

  • Import the workflow into n8n and configure your SERP API credentials
  • Set up your Google Sheet with the required keyword database structure
  • Configure Slack webhook URL and email SMTP settings
  • Define your ranking drop threshold (recommended: 5+ position drops)
  • Test the workflow with a small keyword set before full deployment
  • Schedule the workflow to run daily during off-peak hours

Requirements

  • SERP API account with sufficient credits for daily keyword checks
  • Google Sheets access for keyword database and ranking storage
  • Slack workspace with webhook permissions for team notifications
  • Email service (SMTP or API) for stakeholder alerts
  • Keywords database properly formatted in Google Sheets

Database/Sheet Columns Required

Google Sheet: "Keywords Database"

Create a Google Sheet with the following columns:

| Column Name | Description | Example | |-------------|-------------|---------| | keyword | Target keyword to monitor | "best seo tools" | | domain | Your website domain | "yourwebsite.com" | | current_rank | Latest ranking position | 5 | | previous_rank | Previous day's ranking | 3 | | status | Monitoring status | "active" | | target_url | Expected ranking URL | "/best-seo-tools-guide" | | search_volume | Monthly search volume | 1200 | | difficulty | Keyword difficulty score | 65 | | date_added | When keyword was added | "2025-01-15" | | last_checked | Last monitoring date | "2025-07-30" | | drop_threshold | Custom drop alert threshold | 5 | | category | Keyword grouping | "Product Pages" |

Customising this workflow

  • Modify ranking thresholds in the "Filter Significant Ranking Drops" node to adjust sensitivity (e.g., 3+ positions vs 10+ positions)
  • Add competitor monitoring by duplicating the SERP API node and tracking competitor rankings for the same keywords
  • Customize alert messages in Slack and email nodes to include your brand voice and specific stakeholder information
  • Extend to multiple search engines by adding Bing or Yahoo ranking checks alongside Google
  • Implement ranking improvement alerts to celebrate when keywords move up significantly
  • Add mobile vs desktop tracking by configuring separate SERP API calls for different device types

Monitor SEO Keyword Rankings with SERP API & Send Drop Alerts via Slack

This n8n workflow automates the process of monitoring SEO keyword rankings using a hypothetical SERP API, comparing current rankings against a historical record in Google Sheets, and sending alerts via Slack and email if a significant drop is detected.

What it does

This workflow is designed to run on a schedule and perform the following actions:

  1. Triggers on a schedule: The workflow starts at a predefined interval (e.g., daily, weekly).
  2. Fetches historical keyword data: It retrieves a list of keywords and their previous rankings from a Google Sheet.
  3. Queries SERP API: For each keyword, it makes an HTTP request to a SERP API (e.g., Google Search API, a specialized SEO API) to get its current ranking.
  4. Compares rankings: It compares the newly fetched ranking with the historical ranking from Google Sheets.
  5. Detects ranking drops: It uses a Code node to implement custom logic for detecting significant drops in ranking (e.g., a drop of more than 5 positions).
  6. Filters for drops: Only items where a significant ranking drop is detected are passed on.
  7. Sends Slack alerts: For each detected drop, it sends a detailed alert message to a specified Slack channel.
  8. Sends Email alerts: For each detected drop, it also sends an email notification.
  9. Updates Google Sheet: Finally, it updates the Google Sheet with the new, current rankings, ensuring the historical data is always up-to-date for the next run.

Prerequisites/Requirements

To use this workflow, you will need:

  • n8n Instance: A running n8n instance.
  • Google Sheets Account: A Google Sheets spreadsheet containing your keywords and their historical ranking data. You will need to configure Google Sheets credentials in n8n.
  • SERP API Access: Access to a SERP (Search Engine Results Page) API. This workflow uses a generic "HTTP Request" node, so you'll need to configure the specific API endpoint, authentication, and parameters for your chosen SERP API.
  • Slack Account: A Slack workspace and channel where you want to receive alerts. You will need to configure Slack credentials in n8n.
  • SMTP Server: Access to an SMTP server for sending email alerts. You will need to configure Email (SMTP) credentials in n8n.

Setup/Usage

  1. Import the workflow: Download the provided JSON and import it into your n8n instance.
  2. Configure Credentials:
    • Google Sheets: Set up your Google Sheets credentials. Ensure the service account or OAuth credentials have read/write access to your ranking spreadsheet.
    • Slack: Set up your Slack credentials.
    • Email (SMTP): Set up your SMTP credentials for sending emails.
  3. Configure Google Sheets Node:
    • Specify the Spreadsheet ID and Sheet Name where your keyword data is stored.
    • Ensure the sheet has columns for keyword, url, previous_rank, and current_rank.
  4. Configure HTTP Request Node (SERP API):
    • Update the URL and Headers to match your SERP API's documentation.
    • Adjust the Body to send the keyword and url from the Google Sheet to the API.
    • Modify the JSON Path expressions to correctly extract the current_rank from the API response.
  5. Configure Code Node:
    • Review the JavaScript code in the "Code" node. This node contains the logic to compare previous_rank and current_rank and determine if a drop is significant enough to trigger an alert. Adjust the logic (dropThreshold) as needed.
  6. Configure Filter Node:
    • The filter node is set to pass items where the rankingDrop variable (set in the Code node) is true. No changes should be needed here unless you modify the Code node's output.
  7. Configure Slack Node:
    • Specify the Channel where alerts should be sent.
    • Customize the Message content to include relevant details like the keyword, URL, previous rank, and current rank.
  8. Configure Send Email Node:
    • Specify the To email address(es).
    • Customize the Subject and Body of the email alert.
  9. Activate the workflow: Once all configurations are complete, activate the workflow to enable its scheduled execution.
  10. Adjust Cron Schedule: Modify the "Cron" node to set your desired monitoring frequency (e.g., daily, weekly).

Related Templates

Automate Dutch Public Procurement Data Collection with TenderNed

TenderNed Public Procurement What This Workflow Does This workflow automates the collection of public procurement data from TenderNed (the official Dutch tender platform). It: Fetches the latest tender publications from the TenderNed API Retrieves detailed information in both XML and JSON formats for each tender Parses and extracts key information like organization names, titles, descriptions, and reference numbers Filters results based on your custom criteria Stores the data in a database for easy querying and analysis Setup Instructions This template comes with sticky notes providing step-by-step instructions in Dutch and various query options you can customize. Prerequisites TenderNed API Access - Register at TenderNed for API credentials Configuration Steps Set up TenderNed credentials: Add HTTP Basic Auth credentials with your TenderNed API username and password Apply these credentials to the three HTTP Request nodes: "Tenderned Publicaties" "Haal XML Details" "Haal JSON Details" Customize filters: Modify the "Filter op ..." node to match your specific requirements Examples: specific organizations, contract values, regions, etc. How It Works Step 1: Trigger The workflow can be triggered either manually for testing or automatically on a daily schedule. Step 2: Fetch Publications Makes an API call to TenderNed to retrieve a list of recent publications (up to 100 per request). Step 3: Process & Split Extracts the tender array from the response and splits it into individual items for processing. Step 4: Fetch Details For each tender, the workflow makes two parallel API calls: XML endpoint - Retrieves the complete tender documentation in XML format JSON endpoint - Fetches metadata including reference numbers and keywords Step 5: Parse & Merge Parses the XML data and merges it with the JSON metadata and batch information into a single data structure. Step 6: Extract Fields Maps the raw API data to clean, structured fields including: Publication ID and date Organization name Tender title and description Reference numbers (kenmerk, TED number) Step 7: Filter Applies your custom filter criteria to focus on relevant tenders only. Step 8: Store Inserts the processed data into your database for storage and future analysis. Customization Tips Modify API Parameters In the "Tenderned Publicaties" node, you can adjust: offset: Starting position for pagination size: Number of results per request (max 100) Add query parameters for date ranges, status filters, etc. Add More Fields Extend the "Splits Alle Velden" node to extract additional fields from the XML/JSON data, such as: Contract value estimates Deadline dates CPV codes (procurement classification) Contact information Integrate Notifications Add a Slack, Email, or Discord node after the filter to get notified about new matching tenders. Incremental Updates Modify the workflow to only fetch new tenders by: Storing the last execution timestamp Adding date filters to the API query Only processing publications newer than the last run Troubleshooting No data returned? Verify your TenderNed API credentials are correct Check that you have setup youre filter proper Need help setting this up or interested in a complete tender analysis solution? Get in touch 🔗 LinkedIn – Wessel Bulte

Wessel BulteBy Wessel Bulte
247

🎓 How to transform unstructured email data into structured format with AI agent

This workflow automates the process of extracting structured, usable information from unstructured email messages across multiple platforms. It connects directly to Gmail, Outlook, and IMAP accounts, retrieves incoming emails, and sends their content to an AI-powered parsing agent built on OpenAI GPT models. The AI agent analyzes each email, identifies relevant details, and returns a clean JSON structure containing key fields: From – sender’s email address To – recipient’s email address Subject – email subject line Summary – short AI-generated summary of the email body The extracted information is then automatically inserted into an n8n Data Table, creating a structured database of email metadata and summaries ready for indexing, reporting, or integration with other tools. --- Key Benefits ✅ Full Automation: Eliminates manual reading and data entry from incoming emails. ✅ Multi-Source Integration: Handles data from different email providers seamlessly. ✅ AI-Driven Accuracy: Uses advanced language models to interpret complex or unformatted content. ✅ Structured Storage: Creates a standardized, query-ready dataset from previously unstructured text. ✅ Time Efficiency: Processes emails in real time, improving productivity and response speed. *✅ Scalability: Easily extendable to handle additional sources or extract more data fields. --- How it works This workflow automates the transformation of unstructured email data into a structured, queryable format. It operates through a series of connected steps: Email Triggering: The workflow is initiated by one of three different email triggers (Gmail, Microsoft Outlook, or a generic IMAP account), which constantly monitor for new incoming emails. AI-Powered Parsing & Structuring: When a new email is detected, its raw, unstructured content is passed to a central "Parsing Agent." This agent uses a specified OpenAI language model to intelligently analyze the email text. Data Extraction & Standardization: Following a predefined system prompt, the AI agent extracts key information from the email, such as the sender, recipient, subject, and a generated summary. It then forces the output into a strict JSON structure using a "Structured Output Parser" node, ensuring data consistency. Data Storage: Finally, the clean, structured data (the from, to, subject, and summarize fields) is inserted as a new row into a specified n8n Data Table, creating a searchable and reportable database of email information. --- Set up steps To implement this workflow, follow these configuration steps: Prepare the Data Table: Create a new Data Table within n8n. Define the columns with the following names and string type: From, To, Subject, and Summary. Configure Email Credentials: Set up the credential connections for the email services you wish to use (Gmail OAuth2, Microsoft Outlook OAuth2, and/or IMAP). Ensure the accounts have the necessary permissions to read emails. Configure AI Model Credentials: Set up the OpenAI API credential with a valid API key. The workflow is configured to use the model, but this can be changed in the respective nodes if needed. Connect the Nodes: The workflow canvas is already correctly wired. Visually confirm that the email triggers are connected to the "Parsing Agent," which is connected to the "Insert row" (Data Table) node. Also, ensure the "OpenAI Chat Model" and "Structured Output Parser" are connected to the "Parsing Agent" as its AI model and output parser, respectively. Activate the Workflow: Save the workflow and toggle the "Active" switch to ON. The triggers will begin polling for new emails according to their schedule (e.g., every minute), and the automation will start processing incoming messages. --- Need help customizing? Contact me for consulting and support or add me on Linkedin.

DavideBy Davide
1616

Tax deadline management & compliance alerts with GPT-4, Google Sheets & Slack

AI-Driven Tax Compliance & Deadline Management System Description Automate tax deadline monitoring with AI-powered insights. This workflow checks your tax calendar daily at 8 AM, uses GPT-4 to analyze upcoming deadlines across multiple jurisdictions, detects overdue and critical items, and sends intelligent alerts via email and Slack only when immediate action is required. Perfect for finance teams and accounting firms who need proactive compliance management without manual tracking. 🏛️🤖📊 Good to Know AI-Powered: GPT-4 provides risk assessment and strategic recommendations Multi-Jurisdiction: Handles Federal, State, and Local tax requirements automatically Smart Alerts: Only notifies executives when deadlines are overdue or critical (≤3 days) Priority Classification: Categorizes deadlines as Overdue, Critical, High, or Medium priority Dual Notifications: Critical alerts to leadership + daily summaries to team channel Complete Audit Trail: Logs all checks and deadlines to Google Sheets for compliance records How It Works Daily Trigger - Runs at 8:00 AM every morning Fetch Data - Pulls tax calendar and company configuration from Google Sheets Analyze Deadlines - Calculates days remaining, filters by jurisdiction/entity type, categorizes by priority AI Analysis - GPT-4 provides strategic insights and risk assessment on upcoming deadlines Smart Routing - Only sends alerts if overdue or critical deadlines exist Critical Alerts - HTML email to executives + Slack alert for urgent items Team Updates - Slack summary to finance channel with all upcoming deadlines Logging - Records compliance check results to Google Sheets for audit trail Requirements Google Sheets Structure Sheet 1: TaxCalendar DeadlineID | DeadlineName | DeadlineDate | Jurisdiction | Category | AssignedTo | IsActive FED-Q1 | Form 1120 Q1 | 2025-04-15 | Federal | Income | John Doe | TRUE Sheet 2: CompanyConfig (single row) Jurisdictions | EntityType | FiscalYearEnd Federal, California | Corporation | 12-31 Sheet 3: ComplianceLog (auto-populated) Date | AlertLevel | TotalUpcoming | CriticalCount | OverdueCount 2025-01-15 | HIGH | 12 | 3 | 1 Credentials Needed Google Sheets - Service Account OAuth2 OpenAI - API Key (GPT-4 access required) SMTP - Email account for sending alerts Slack - Bot Token with chat:write permission Setup Steps Import workflow JSON into n8n Add all 4 credentials Replace these placeholders: YOURTAXCALENDAR_ID - Tax calendar sheet ID YOURCONFIGID - Company config sheet ID YOURLOGID - Compliance log sheet ID C12345678 - Slack channel ID tax@company.com - Sender email cfo@company.com - Recipient email Share all sheets with Google service account email Invite Slack bot to channels Test workflow manually Activate the trigger Customizing This Workflow Change Alert Thresholds: Edit "Analyze Deadlines" node: Critical: Change <= 3 to <= 5 for 5-day warning High: Change <= 7 to <= 14 for 2-week notice Medium: Change <= 30 to <= 60 for 2-month lookout Adjust Schedule: Edit "Daily Tax Check" trigger: Change hour/minute for different run time Add multiple trigger times for tax season (8 AM, 2 PM, 6 PM) Add More Recipients: Edit "Send Email" node: To: cfo@company.com, director@company.com CC: accounting@company.com BCC: archive@company.com Customize Email Design: Edit "Format Email" node to change colors, add logo, or modify layout Add SMS Alerts: Insert Twilio node after "Is Critical" for emergency notifications Integrate Task Management: Add HTTP Request node to create tasks in Asana/Jira for critical deadlines Troubleshooting | Issue | Solution | |-------|----------| | No deadlines found | Check date format (YYYY-MM-DD) and IsActive = TRUE | | AI analysis failed | Verify OpenAI API key and account credits | | Email not sending | Test SMTP credentials and check if critical condition met | | Slack not posting | Invite bot to channel and verify channel ID format | | Permission denied | Share Google Sheets with service account email | 📞 Professional Services Need help with implementation or customization? Our team offers: 🎯 Custom workflow development 🏢 Enterprise deployment support 🎓 Team training sessions 🔧 Ongoing maintenance 📊 Custom reporting & dashboards 🔗 Additional API integrations Discover more workflows – Get in touch with us

Oneclick AI SquadBy Oneclick AI Squad
93