Automate web research & analysis with Oxylabs & GPT for comprehensive reports
Fully automate deep research from start to finish: scrape Google Search results, select relevant sources, scrape & analyze each source in parallel, and generate a comprehensive research report.
Who is this for?
This workflow is for anyone who needs to research topics quickly and thoroughly: content creators, marketers, product managers, researchers, journalists, students, or anyone seeking deep insights without spending hours browsing websites. If you find yourself opening dozens of browser tabs to piece together information, this template will automate that entire process and deliver comprehensive reports in minutes.
How it works
- Submit your research questions through n8n's chat interface (include as much context as you need)
- AI generates strategic search queries to explore different angles of your topic (customize the number of queries as needed)
- Oxylabs scrapes Google Search results for each query (up to 50 results per query)
- AI evaluates and selects sources that are the most relevant and authoritative
- Content extraction runs in parallel as Oxylabs scrapes each source and AI extracts key insights
- Summaries are collected in n8n's data table for final processing
- AI synthesizes everything into a comprehensive research report with actionable insights
See the complete step-by-step tutorial on the n8n blog.
Requirements
- Oxylabs AI Studio API key – Get a free API key with 1000 credits
- OpenAI API key (or use alternatives like Claude, Gemini, and local Ollama LLMs)
Setup
- Install Oxylabs AI Studio as shown on this page
- Set your API keys:
- Oxylabs AI Studio
- OpenAI
- Create a data table
- Select the table name in each data table node
- Create a sub-workflow:
- Select the 3 nodes (Scrape content, Summarize content, Insert row)
- Right-click
- Select “Convert 3 nodes to sub-workflow”
- Edit the sub-workflow settings for for parallel execution:
- Mode: Run once for each item
- Options → Add Option → disable “Wait For Sub-Workflow Completion”
Once you finish all these setup steps, you can run the workflow through n8n's chat interface. For example, send the following message:
I'm planning to build a wooden summer house and would appreciate guidance on the process. What are the key considerations I should keep in mind from planning through completion? I'm particularly interested in the recommended construction steps and which materials will ensure long-term durability and quality.
Customize this workflow for your needs
Feel free to modify the workflow to fit the scale and final output your project requires:
- To reuse this workflow, clear the data table after the final analysis by adding a Data table node with the Delete row(s) action
- Scale up by processing more search queries, increasing results per query beyond 10, and selecting additional relevant URLs
- Enable JavaScript rendering in Oxylabs AI Studio (Scraper) node to ensure all content is gathered
- Adjust the system prompts in LLM nodes to fit your specific research goals
- Explore other AI Studio apps like Browser Agent for interactive browser control or Crawler for mapping entire websites
- Connect other nodes like Google Sheets, Notion, Airtable, or webhooks to route results where you need them
n8n Workflow: Basic Chat Trigger with OpenAI and Data Handling
This n8n workflow demonstrates a fundamental interaction pattern: receiving a chat message, processing it with OpenAI, and then handling the response through conditional logic and data manipulation. It serves as a starting point for building more complex AI-driven chat automations.
Description
This workflow automates the process of taking an incoming chat message, sending it to OpenAI for processing, and then conditionally routing the AI's response for further actions or data structuring. It includes steps for data transformation, conditional logic, and a delay mechanism.
What it does
- Listens for Chat Messages: The workflow is triggered whenever a chat message is received.
- Processes with OpenAI: The received chat message is sent to OpenAI for AI-powered processing (e.g., generating a response, summarizing, classifying).
- Edits Fields: The data from the OpenAI response is then passed through an "Edit Fields" (Set) node, likely to transform or select specific parts of the AI's output.
- Conditional Routing: An "If" node evaluates the processed data, allowing the workflow to take different paths based on specific conditions (e.g., if a certain keyword is present, or a sentiment score is above a threshold).
- Introduces a Delay: A "Wait" node pauses the workflow execution for a specified duration, useful for rate limiting or staggering subsequent actions.
- Splits Data: A "Split Out" node is included, which typically breaks down an array of items into individual items, allowing for per-item processing.
- Aggregates Data: An "Aggregate" node is present, which combines multiple items into a single item or a structured list, often used after splitting or for final output formatting.
- Displays Data: A "Data table" node is used, likely for visualizing or structuring the final processed data, useful for debugging or presenting results.
Prerequisites/Requirements
- n8n Instance: A running n8n instance (cloud or self-hosted).
- OpenAI Account & API Key: An OpenAI account with an active API key configured as a credential in n8n.
- Chat Platform Integration: The "Chat Trigger" node implies an underlying chat platform integration (e.g., Slack, Telegram, Discord, etc.) configured to send messages to this n8n workflow.
Setup/Usage
- Import the Workflow: Import the provided JSON into your n8n instance.
- Configure Credentials:
- Set up your OpenAI API Key as an n8n credential.
- Ensure your chat platform (e.g., Slack, Telegram) is correctly configured to send messages to the "Chat Trigger" webhook URL.
- Customize Nodes:
- Chat Trigger: Ensure it's correctly linked to your desired chat platform.
- OpenAI: Configure the specific OpenAI model and prompt you wish to use for processing chat messages.
- Edit Fields: Adjust the fields to be edited or added based on your desired output from OpenAI.
- If: Define the conditions for routing the workflow based on the OpenAI response.
- Wait: Adjust the delay duration as needed.
- Split Out / Aggregate: Configure these nodes if you need to process or combine multiple items from the OpenAI response or subsequent steps.
- Data table: Configure the columns and data you wish to display.
- Activate the Workflow: Once configured, activate the workflow.
- Test: Send a message to your configured chat platform to trigger the workflow and observe its execution.
Related Templates
Track competitor SEO keywords with Decodo + GPT-4.1-mini + Google Sheets
This workflow automates competitor keyword research using OpenAI LLM and Decodo for intelligent web scraping. Who this is for SEO specialists, content strategists, and growth marketers who want to automate keyword research and competitive intelligence. Marketing analysts managing multiple clients or websites who need consistent SEO tracking without manual data pulls. Agencies or automation engineers using Google Sheets as an SEO data dashboard for keyword monitoring and reporting. What problem this workflow solves Tracking competitor keywords manually is slow and inconsistent. Most SEO tools provide limited API access or lack contextual keyword analysis. This workflow solves that by: Automatically scraping any competitor’s webpage with Decodo. Using OpenAI GPT-4.1-mini to interpret keyword intent, density, and semantic focus. Storing structured keyword insights directly in Google Sheets for ongoing tracking and trend analysis. What this workflow does Trigger — Manually start the workflow or schedule it to run periodically. Input Setup — Define the website URL and target country (e.g., https://dev.to, france). Data Scraping (Decodo) — Fetch competitor web content and metadata. Keyword Analysis (OpenAI GPT-4.1-mini) Extract primary and secondary keywords. Identify focus topics and semantic entities. Generate a keyword density summary and SEO strength score. Recommend optimization and internal linking opportunities. Data Structuring — Clean and convert GPT output into JSON format. Data Storage (Google Sheets) — Append structured keyword data to a Google Sheet for long-term tracking. Setup Prerequisites If you are new to Decode, please signup on this link visit.decodo.com n8n account with workflow editor access Decodo API credentials OpenAI API key Google Sheets account connected via OAuth2 Make sure to install the Decodo Community node. Create a Google Sheet Add columns for: primarykeywords, seostrengthscore, keyworddensity_summary, etc. Share with your n8n Google account. Connect Credentials Add credentials for: Decodo API credentials - You need to register, login and obtain the Basic Authentication Token via Decodo Dashboard OpenAI API (for GPT-4o-mini) Google Sheets OAuth2 Configure Input Fields Edit the “Set Input Fields” node to set your target site and region. Run the Workflow Click Execute Workflow in n8n. View structured results in your connected Google Sheet. How to customize this workflow Track Multiple Competitors → Use a Google Sheet or CSV list of URLs; loop through them using the Split In Batches node. Add Language Detection → Add a Gemini or GPT node before keyword analysis to detect content language and adjust prompts. Enhance the SEO Report → Expand the GPT prompt to include backlink insights, metadata optimization, or readability checks. Integrate Visualization → Connect your Google Sheet to Looker Studio for SEO performance dashboards. Schedule Auto-Runs → Use the Cron Node to run weekly or monthly for competitor keyword refreshes. Summary This workflow automates competitor keyword research using: Decodo for intelligent web scraping OpenAI GPT-4.1-mini for keyword and SEO analysis Google Sheets for live tracking and reporting It’s a complete AI-powered SEO intelligence pipeline ideal for teams that want actionable insights on keyword gaps, optimization opportunities, and content focus trends, without relying on expensive SEO SaaS tools.
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
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