HumationHuman + Automation
Back to Catalog

Seo competitor analysis & data logging with Semrush API and Google Sheets

Sk developer Sk developer
1180 views
2/3/2026
slackdatabaseautomationwebhooknotion
Official Page

Competitor Analysis & SEO Data Logging Workflow Using Competitor Analysis Semrush API

Description

This workflow automates SEO competitor analysis using the Competitor Analysis Semrush API and logs the data into Google Sheets for structured reporting.
It captures domain overview, organic competitors, organic pages, and keyword-level insights from the Competitor Analysis Semrush API, then appends them to different sheets for easy tracking.

Node-by-Node Explanation

  1. On form submission – Captures the website URL entered by the user.
  2. Competitor Analysis – Sends the website to the Competitor Analysis Semrush API via HTTP POST request.
  3. Re format output – Extracts and formats the domain overview data.
  4. Domain overview – Saves organic keywords and traffic into Google Sheets.
  5. Reformat – Extracts the organic competitors list.
  6. Organic Competitor – Logs competitor domains, relevance, and traffic into Google Sheets.
  7. Reformat 2 – Extracts organic pages data.
  8. Organic Pages – Stores page-level data such as traffic and keyword counts.
  9. Reformat2 – Extracts organic keywords details.
  10. organic keywords – Logs keyword data like CPC, volume, and difficulty into Google Sheets.

Benefits

  • ✅ Automated competitor tracking – No manual API calls, all logged in Google Sheets.
  • ✅ Centralized SEO reporting – Data stored in structured sheets for quick access.
  • ✅ Time-saving – Streamlines research by combining multiple reports in one workflow.
  • ✅ Accurate insights – Direct data from the Competitor Analysis Semrush API ensures reliability.

Use Cases

  • 📊 SEO Research – Track domain performance and competitor strategies.
  • 🔍 Competitor Monitoring – Identify competitor domains, keywords, and traffic.
  • 📝 Content Strategy – Find top-performing organic pages and replicate content ideas.
  • 💰 Keyword Planning – Use CPC and difficulty data to prioritize profitable keywords.
  • 📈 Client Reporting – Generate ready-to-use SEO competitor analysis reports in Google Sheets.

SEO Competitor Analysis & Data Logging with Semrush API and Google Sheets

This n8n workflow automates the process of performing SEO competitor analysis using the Semrush API and logging the results into a Google Sheet. It's designed to be triggered manually via an n8n form, allowing users to input competitor domains and keywords directly.

What it does

  1. Triggers on Form Submission: The workflow starts when a user submits data through a simple n8n form.
  2. Processes Input Data: It takes the submitted competitor domains and keywords from the form.
  3. Performs Semrush API Requests: For each competitor domain and keyword, it makes requests to the Semrush API to gather relevant SEO metrics (e.g., keyword rankings, traffic, backlinks).
  4. Transforms Data: The raw data from Semrush is processed and transformed into a structured format suitable for logging.
  5. Logs Data to Google Sheets: The processed SEO metrics are then appended as new rows to a specified Google Sheet, creating a historical record of competitor performance.

Prerequisites/Requirements

  • n8n Instance: A running n8n instance (cloud or self-hosted).
  • Semrush API Key: An active Semrush account with API access. You will need to configure a credential for the HTTP Request node.
  • Google Account: A Google account with access to Google Sheets. You will need to configure a Google Sheets credential in n8n.
  • Google Sheet: A pre-existing Google Sheet where the competitor analysis data will be logged. Ensure the sheet has appropriate headers for the data you intend to store.

Setup/Usage

  1. Import the Workflow: Import the provided JSON into your n8n instance.
  2. Configure Credentials:
    • Semrush API: For the "HTTP Request" node, create or select an existing HTTP Request credential. You will likely need to add your Semrush API key as a header or query parameter, depending on Semrush's API documentation.
    • Google Sheets: For the "Google Sheets" node, create or select an existing Google Sheets OAuth2 credential to allow n8n to write to your spreadsheets.
  3. Configure Google Sheets Node:
    • Specify the Spreadsheet ID of your target Google Sheet.
    • Specify the Sheet Name within that spreadsheet where data should be appended.
    • Ensure the "Operation" is set to "Append Row".
  4. Configure n8n Form Trigger:
    • The "On form submission" node is pre-configured to accept inputs. You may customize the form fields (e.g., competitorDomains, keywords) to match your exact needs.
  5. Activate the Workflow: Once configured, activate the workflow.
  6. Trigger the Workflow:
    • Open the n8n form URL provided by the "On form submission" node.
    • Enter the competitor domains and keywords you wish to analyze.
    • Submit the form. The workflow will execute, fetch data from Semrush, and log it to your Google Sheet.

Related Templates

Two-way property repair management system with Google Sheets & Drive

This workflow automates the repair request process between tenants and building managers, keeping all updates organized in a single spreadsheet. It is composed of two coordinated workflows, as two separate triggers are required — one for new repair submissions and another for repair updates. A Unique Unit ID that corresponds to individual units is attributed to each request, and timestamps are used to coordinate repair updates with specific requests. General use cases include: Property managers who manage multiple buildings or units. Building owners looking to centralize tenant repair communication. Automation builders who want to learn multi-trigger workflow design in n8n. --- ⚙️ How It Works Workflow 1 – New Repair Requests Behind the Scenes: A tenant fills out a Google Form (“Repair Request Form”), which automatically adds a new row to a linked Google Sheet. Steps: Trigger: Google Sheets rowAdded – runs when a new form entry appears. Extract & Format: Collects all relevant form data (address, unit, urgency, contacts). Generate Unit ID: Creates a standardized identifier (e.g., BUILDING-UNIT) for tracking. Email Notification: Sends the building manager a formatted email summarizing the repair details and including a link to a Repair Update Form (which activates Workflow 2). --- Workflow 2 – Repair Updates Behind the Scenes:\ Triggered when the building manager submits a follow-up form (“Repair Update Form”). Steps: Lookup by UUID: Uses the Unit ID from Workflow 1 to find the existing row in the Google Sheet. Conditional Logic: If photos are uploaded: Saves each image to a Google Drive folder, renames files consistently, and adds URLs to the sheet. If no photos: Skips the upload step and processes textual updates only. Merge & Update: Combines new data with existing repair info in the same spreadsheet row — enabling a full repair history in one place. --- 🧩 Requirements Google Account (for Forms, Sheets, and Drive) Gmail/email node connected for sending notifications n8n credentials configured for Google API access --- ⚡ Setup Instructions (see more detail in workflow) Import both workflows into n8n, then copy one into a second workflow. Change manual trigger in workflow 2 to a n8n Form node. Connect Google credentials to all nodes. Update spreadsheet and folder IDs in the corresponding nodes. Customize email text, sender name, and form links for your organization. Test each workflow with a sample repair request and a repair update submission. --- 🛠️ Customization Ideas Add Slack or Telegram notifications for urgent repairs. Auto-create folders per building or unit for photo uploads. Generate monthly repair summaries using Google Sheets triggers. Add an AI node to create summaries/extract relevant repair data from repair request that include long submissions.

Matt@VeraisonLabsBy Matt@VeraisonLabs
208

Send WooCommerce cross-sell offers to customers via WhatsApp using Rapiwa API

Who Is This For? This n8n workflow enables automated cross-selling by identifying each WooCommerce customer's most frequently purchased product, finding a related product to recommend, and sending a personalized WhatsApp message using the Rapiwa API. It also verifies whether the user's number is WhatsApp-enabled before sending, and logs both successful and unsuccessful attempts to Google Sheets for tracking. What This Workflow Does Retrieves all paying customers from your WooCommerce store Identifies each customer's most purchased product Finds the latest product in the same category as their most purchased item Cleans and verifies customer phone numbers for WhatsApp compatibility Sends personalized WhatsApp messages with product recommendations Logs all activities to Google Sheets for tracking and analysis Handles both verified and unverified numbers appropriately Key Features Customer Segmentation: Automatically identifies paying customers from your WooCommerce store Product Analysis: Determines each customer's most purchased product Smart Recommendations: Finds the latest products in the same category as customer favorites WhatsApp Integration: Uses Rapiwa API for message delivery Phone Number Validation: Verifies WhatsApp numbers before sending messages Dual Logging System: Tracks both successful and failed message attempts in Google Sheets Rate Limiting: Uses batching and wait nodes to prevent API overload Personalized Messaging: Includes customer name and product details in messages Requirements WooCommerce store with API access Rapiwa account with API access for WhatsApp verification and messaging Google account with Sheets access Customer phone numbers in WooCommerce (stored in billing.phone field) How to Use — Step-by-Step Setup Credentials Setup WooCommerce API: Configure WooCommerce API credentials in n8n (e.g., "WooCommerce (get customer)" and "WooCommerce (get customer data)") Rapiwa Bearer Auth: Create an HTTP Bearer credential with your Rapiwa API token Google Sheets OAuth2: Set up OAuth2 credentials for Google Sheets access Configure Google Sheets Ensure your sheet has the required columns as specified in the Google Sheet Column Structure section Verify Code Nodes Code (get paying_customer): Filters customers to include only those who have made purchases Get most buy product id & Clear Number: Identifies the most purchased product and cleans phone numbers Configure HTTP Request Nodes Get customer data: Verify the WooCommerce API endpoint for retrieving customer orders Get specific product data: Verify the WooCommerce API endpoint for product details Get specific product recommend latest product: Verify the WooCommerce API endpoint for finding latest products by category Check valid WhatsApp number Using Rapiwa: Verify the Rapiwa endpoint for WhatsApp number validation Rapiwa Sender: Verify the Rapiwa endpoint for sending messages Google Sheet Required Columns You’ll need two Google Sheets (or two tabs in one spreadsheet): A Google Sheet formatted like this ➤ sample The workflow uses a Google Sheet with the following columns to track coupon distribution: Both must have the following headers (match exactly): | name | number | email | address1 | price | suk | title | product link | validity | staus | | ---------- | ------------- | ----------------------------------------------- | ----------- | ----- | --- | ---------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ | ---------- | -------- | | Abdul Mannan | 8801322827799 | contact@spagreen.net | mirpur dohs | 850 | | Sharp Most Demanding Hoodie x Nike | https://yourshopdomain/p-img-nike | verified | sent | | Abdul Mannan | 8801322827799 | contact@spagreen.net | mirpur dohs | 850 | | Sharp Most Demanding Hoodie x Nike | https://yourshopdomain/p-img-nike | unverified | not sent | | Abdul Mannan | 8801322827799 | contact@spagreen.net | mirpur dohs | 850 | | Sharp Most Demanding Hoodie x Nike | https://yourshopdomain/p-img-nike | verified | sent | Important Notes Phone Number Format: The workflow cleans phone numbers by removing all non-digit characters. Ensure your WooCommerce phone numbers are in a compatible format. API Rate Limits: Rapiwa and WooCommerce APIs have rate limits. Adjust batch sizes and wait times accordingly. Data Privacy: Ensure compliance with data protection regulations when sending marketing messages. Error Handling: The workflow logs unverified numbers but doesn't have extensive error handling. Consider adding error notifications for failed API calls. Product Availability: The workflow recommends the latest product in a category, but doesn't check if it's in stock. Consider adding stock status verification. Testing: Always test with a small batch before running the workflow on your entire customer list. Useful Links Dashboard: https://app.rapiwa.com Official Website: https://rapiwa.com Documentation: https://docs.rapiwa.com Support & Help WhatsApp: Chat on WhatsApp Discord: SpaGreen Community Facebook Group: SpaGreen Support Website: https://spagreen.net Developer Portfolio: Codecanyon SpaGreen

RapiwaBy Rapiwa
183

Track SDK documentation drift with GitHub, Notion, Google Sheets, and Slack

📊 Description Automatically track SDK releases from GitHub, compare documentation freshness in Notion, and send Slack alerts when docs lag behind. This workflow ensures documentation stays in sync with releases, improves visibility, and reduces version drift across teams. 🚀📚💬 What This Template Does Step 1: Listens to GitHub repository events to detect new SDK releases. 🧩 Step 2: Fetches release metadata including version, tag, and publish date. 📦 Step 3: Logs release data into Google Sheets for record-keeping and analysis. 📊 Step 4: Retrieves FAQ or documentation data from Notion. 📚 Step 5: Merges GitHub and Notion data to calculate documentation drift. 🔍 Step 6: Flags SDKs whose documentation is over 30 days out of date. ⚠️ Step 7: Sends detailed Slack alerts to notify responsible teams. 🔔 Key Benefits ✅ Keeps SDK documentation aligned with product releases ✅ Prevents outdated information from reaching users ✅ Provides centralized release tracking in Google Sheets ✅ Sends real-time Slack alerts for overdue updates ✅ Strengthens DevRel and developer experience operations Features GitHub release trigger for real-time monitoring Google Sheets logging for tracking and auditing Notion database integration for documentation comparison Automated drift calculation (days since last update) Slack notifications for overdue documentation Requirements GitHub OAuth2 credentials Notion API credentials Google Sheets OAuth2 credentials Slack Bot token with chat:write permissions Target Audience Developer Relations (DevRel) and SDK engineering teams Product documentation and technical writing teams Project managers tracking SDK and doc release parity Step-by-Step Setup Instructions Connect your GitHub account and select your SDK repository. Replace YOURGOOGLESHEETID and YOURSHEET_GID with your tracking spreadsheet. Add your Notion FAQ database ID. Configure your Slack channel ID for alerts. Run once manually to validate setup, then enable automation.

Rahul JoshiBy Rahul Joshi
31