Track SEO keyword rankings in Google Search with ScrapingBee API
Who is this template for?
This SEO Reporting workflow template is ideal for digital marketers, SEO consultants, content strategists, and founders who need to quickly gather, format, and store Google search result data. If you regularly audit SERPs, track keyword performance, or monitor competitors, this automation lets you generate polished SEO reports in seconds—ready to share or analyze further.
What problem does this workflow solve?
Scraping and formatting Google search results for SEO insights is often manual, repetitive, and error-prone or requires expensive software. Professionals frequently face challenges like:
- Collecting live, structured data from Google for multiple keywords
- Converting raw search results into readable reports for clients or stakeholders
- Logging changes in rankings or URLs across time for historical tracking
- Exporting SEO data into spreadsheets for deeper analysis
- High monthly software fees
What this workflow does
This n8n workflow scrapes the top organic Google search results for a given keyword and automatically creates a downloadable report while also logging the results in a table format for long-term storage or further processing.
Here’s what it includes:
- A trigger form that accepts a search keyword from the user
- An automated API call to fetch Google’s SERP data
- Two output formats: a formatted HTML table for emails and a Markdown table for download (e.g., for Excel, Airtable or Google Sheets)
- Automatic CSV file generation for download
- Optional email delivery of the report
Setup
Getting started is simple:
-
Enter your API key
- Add your API key to the “Scrape Google SERPs” HTTP Request node (Step-by-step guide inside the template)
- Replace the default query with your own custom Google search parameters if needed
-
Set up delivery options
- Update your email in the “Mail SEO Report” node for report delivery
- Use the downloadable file output from the “Convert to File” node
- Optional: Add a Google Sheets (or similar) node which imports the file
-
Test the workflow
- Use the built-in form to input a keyword
- Confirm that results appear in both your email and downloadable file
-
Activate the workflow
- Turn on the trigger so your team or clients can submit keywords at any time
How to customize this workflow
This template is easy to extend for a variety of SEO automation needs:
- Add a loop to handle multiple keywords at once
- Connect to Airtable, Notion or Google Sheets
- Integrate with Slack or Discord for notifications
- Apply additional filtering to track only new or changed search results
- Schedule it to run daily or weekly with a cron trigger
By combining live SERP scraping, report formatting, and spreadsheet integration, this workflow gives you a fast and flexible SEO reporting system you can use right away or scale up as needed.
n8n Form Trigger to Mailjet Email with File Conversion
This n8n workflow automates the process of sending an email via Mailjet whenever a form is submitted. It also includes a step to convert the form submission data into a file format before sending the email, allowing for flexible data attachment.
What it does
- Listens for Form Submissions: The workflow is triggered by an n8n form submission.
- Converts Data to File: It takes the data submitted through the form and converts it into a specified file format.
- Sends Email via Mailjet: It then uses the converted file as an attachment (or part of the email content) and sends an email through Mailjet.
- Optional Code Execution: Includes a 'Code' node, which can be used for custom data manipulation or logic if needed, although it's not directly connected in this specific JSON.
- Optional HTTP Request: Includes an 'HTTP Request' node, which can be used for making external API calls, though it's not directly connected in this specific JSON.
Prerequisites/Requirements
- n8n Instance: A running n8n instance.
- Mailjet Account: An active Mailjet account with API credentials (API Key and Secret Key) configured as an n8n credential.
- n8n Form: An n8n form set up to trigger this workflow.
Setup/Usage
- Import the Workflow: Import the provided JSON into your n8n instance.
- Configure Mailjet Credentials:
- Go to "Credentials" in n8n.
- Add a new credential of type "Mailjet API".
- Enter your Mailjet API Key and Secret Key.
- Configure "On form submission" Trigger:
- Open the "On form submission" node.
- Define the fields you expect from your form submission.
- Save the node and activate the workflow.
- Configure "Convert to File" Node:
- Specify the desired file format (e.g., CSV, JSON) and the data to be converted from the incoming form submission.
- Configure "Mailjet" Node:
- Select your Mailjet credential.
- Configure the sender email, recipient email, subject, and email body.
- Attach the output of the "Convert to File" node to the email if desired.
- Activate the Workflow: Once all nodes are configured, activate the workflow.
Now, every time your n8n form is submitted, the data will be converted to a file and sent via Mailjet.
Related Templates
Generate song lyrics and music from text prompts using OpenAI and Fal.ai Minimax
Spark your creativity instantly in any chat—turn a simple prompt like "heartbreak ballad" into original, full-length lyrics and a professional AI-generated music track, all without leaving your conversation. 📋 What This Template Does This chat-triggered workflow harnesses AI to generate detailed, genre-matched song lyrics (at least 600 characters) from user messages, then queues them for music synthesis via Fal.ai's minimax-music model. It polls asynchronously until the track is ready, delivering lyrics and audio URL back in chat. Crafts original, structured lyrics with verses, choruses, and bridges using OpenAI Submits to Fal.ai for melody, instrumentation, and vocals aligned to the style Handles long-running generations with smart looping and status checks Returns complete song package (lyrics + audio link) for seamless sharing 🔧 Prerequisites n8n account (self-hosted or cloud with chat integration enabled) OpenAI account with API access for GPT models Fal.ai account for AI music generation 🔑 Required Credentials OpenAI API Setup Go to platform.openai.com → API keys (sidebar) Click "Create new secret key" → Name it (e.g., "n8n Songwriter") Copy the key and add to n8n as "OpenAI API" credential type Test by sending a simple chat completion request Fal.ai HTTP Header Auth Setup Sign up at fal.ai → Dashboard → API Keys Generate a new API key → Copy it In n8n, create "HTTP Header Auth" credential: Name="Fal.ai", Header Name="Authorization", Header Value="Key [Your API Key]" Test with a simple GET to their queue endpoint (e.g., /status) ⚙️ Configuration Steps Import the workflow JSON into your n8n instance Assign OpenAI API credentials to the "OpenAI Chat Model" node Assign Fal.ai HTTP Header Auth to the "Generate Music Track", "Check Generation Status", and "Fetch Final Result" nodes Activate the workflow—chat trigger will appear in your n8n chat interface Test by messaging: "Create an upbeat pop song about road trips" 🎯 Use Cases Content Creators: YouTubers generating custom jingles for videos on the fly, streamlining production from idea to audio export Educators: Music teachers using chat prompts to create era-specific folk tunes for classroom discussions, fostering interactive learning Gift Personalization: Friends crafting anniversary R&B tracks from shared memories via quick chats, delivering emotional audio surprises Artist Brainstorming: Songwriters prototyping hip-hop beats in real-time during sessions, accelerating collaboration and iteration ⚠️ Troubleshooting Invalid JSON from AI Agent: Ensure the system prompt stresses valid JSON; test the agent standalone with a sample query Music Generation Fails (401/403): Verify Fal.ai API key has minimax-music access; check usage quotas in dashboard Status Polling Loops Indefinitely: Bump wait time to 45-60s for complex tracks; inspect fal.ai queue logs for bottlenecks Lyrics Under 600 Characters: Tweak agent prompt to enforce fuller structures like [V1][C][V2][B][C]; verify output length in executions
By Daniel NkenchoAutomate 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
By Wessel BulteAuto-reply & create Linear tickets from Gmail with GPT-5, gotoHuman & human review
This workflow automatically classifies every new email from your linked mailbox, drafts a personalized reply, and creates Linear tickets for bugs or feature requests. It uses a human-in-the-loop with gotoHuman and continuously improves itself by learning from approved examples. How it works The workflow triggers on every new email from your linked mailbox. Self-learning Email Classifier: an AI model categorizes the email into defined categories (e.g., Bug Report, Feature Request, Sales Opportunity, etc.). It fetches previously approved classification examples from gotoHuman to refine decisions. Self-learning Email Writer: the AI drafts a reply to the email. It learns over time by using previously approved replies from gotoHuman, with per-classification context to tailor tone and style (e.g., different style for sales vs. bug reports). Human Review in gotoHuman: review the classification and the drafted reply. Drafts can be edited or retried. Approved values are used to train the self-learning agents. Send approved Reply: the approved response is sent as a reply to the email thread. Create ticket: if the classification is Bug or Feature Request, a ticket is created by another AI agent in Linear. Human Review in gotoHuman: How to set up Most importantly, install the gotoHuman node before importing this template! (Just add the node to a blank canvas before importing) Set up credentials for gotoHuman, OpenAI, your email provider (e.g. Gmail), and Linear. In gotoHuman, select and create the pre-built review template "Support email agent" or import the ID: 6fzuCJlFYJtlu9mGYcVT. Select this template in the gotoHuman node. In the "gotoHuman: Fetch approved examples" http nodes you need to add your formId. It is the ID of the review template that you just created/imported in gotoHuman. Requirements gotoHuman (human supervision, memory for self-learning) OpenAI (classification, drafting) Gmail or your preferred email provider (for email trigger+replies) Linear (ticketing) How to customize Expand or refine the categories used by the classifier. Update the prompt to reflect your own taxonomy. Filter fetched training data from gotoHuman by reviewer so the writer adapts to their personalized tone and preferences. Add more context to the AI email writer (calendar events, FAQs, product docs) to improve reply quality.
By gotoHuman