HumationHuman + Automation
Back to Catalog

Generate AI search visibility datasets with Claude and GPT for tracking platforms

Niclas AuninNiclas Aunin
44 views
2/3/2026
Record ManagementGoogle SheetsWebhookData LookupAPI Automation
Official Page

This n8n workflow automatically generates a comprehensive dataset of 50 AI search prompts tailored to a specific company.

It combines AI-powered company research with structured prompt generation to create monitoring queries for tracking brand visibility across AI search engines like ChatGPT, Perplexity, Claude, and Gemini.

The dataset is ready for use and can be uploaded to any major AI search analytics platforms (like ALLMO.ai,...) or used in your own model.

Who's it for & Use Cases SEO/GEO Marketing teams, Growth Managers, GTM engineers and Founders who want to:

  • Create custom prompt datasets for visibility tracking platforms like ALLMO.ai
  • Generate industry-specific search queries for AI model monitoring

How It Works

Phase 1: Company Research

  1. Start the workflow via the form and input your company name and website URL
  2. GPT-5 Mini with web search collects company information, including buyer personas, key features, and value proposition

Phase 2: Prompt Generation

  1. Claude Sonnet 4.5 generates and refines natural language prompts based on Phase 1 findings
  2. English prompts are automatically translated into German

Phase 3: Export & Implementation

  1. Wait for processing (~total of 2-5 minutes depending on website complexity)
  2. English and German prompt sets are merged with metadata and structured into table format
  3. Download the CSV file containing 50 prompts ready for import into AI Search monitoring systems (allmo.ai, etc.)

How to Setup

  • Just enter your API credentials in the Claude and ChatGPT Nodes.

How to Expand

You can update the system prompts for the "prompt writing engine" to create more prompts. You can update or add more translations.

Output Structure:

  • 25 English prompts + 25 German prompts (can be changed flexibly).
  • Each prompt tagged with: company name, industry, category, language, and AI model for simple tracking.
  • Ready for direct import into any GEO/ALLMO visibility tracking system.

Requirements

API Credentials:

  • Anthropic API (Claude Sonnet 4.5)
  • OpenAI API (GPT-5 Mini with web search capability)

Data Input:

  • Valid company website URL (publicly accessible)
  • Company name as it should appear in tracking

Generate AI Search Visibility Datasets with Claude and GPT for Tracking Platforms

This n8n workflow automates the process of generating AI-powered search visibility datasets, leveraging both Anthropic's Claude and OpenAI's GPT models. It's designed to streamline the creation of structured data for tracking platforms, enabling deeper insights into search performance.

What it does

This workflow, when triggered by a form submission, performs the following key steps:

  1. Receives Form Data: It listens for incoming data from an n8n form submission, which likely contains parameters or prompts for the AI models.
  2. Edits and Prepares Data: It processes and transforms the incoming form data using a "Set" node, preparing it for the subsequent AI requests.
  3. Executes Custom Code: A "Code" node is used to execute custom JavaScript logic. This step likely involves dynamic data manipulation, formatting, or conditional logic based on the input.
  4. Makes HTTP Request: It sends an HTTP request, potentially to an external API or service, using the prepared data. This could be for fetching additional information or interacting with other systems.
  5. Generates AI Content with Anthropic (Claude): It utilizes the Anthropic node to interact with the Claude AI model, generating content or insights based on the processed data. This is a core step for creating the "AI search visibility dataset."
  6. Merges Data: It combines data from different branches or steps using a "Merge" node. This ensures that all necessary information is consolidated before the final output.
  7. Converts to File: The final processed data is converted into a file format (e.g., CSV, JSON) using the "Convert to File" node, making it ready for export or use in tracking platforms.

Prerequisites/Requirements

To use this workflow, you will need:

  • n8n Instance: A running instance of n8n.
  • n8n Form Trigger: The workflow is initiated by an n8n form submission. You'll need to configure this form with the necessary input fields.
  • Anthropic API Key: For the "Anthropic" node to interact with Claude.
  • OpenAI API Key (Implied): While not explicitly shown in the provided JSON, the workflow name "generate-ai-search-visibility-datasets-with-claude-and-gpt-for-tracking-platforms" suggests that an OpenAI (GPT) node might be intended or used in a parallel branch not included in this specific JSON snippet. If GPT is intended, an OpenAI API Key will be required.
  • Custom Code Logic: The "Code" node will require specific JavaScript logic tailored to your data processing needs.
  • HTTP Request Endpoint: If the "HTTP Request" node targets an external service, you'll need access to that service and its API.

Setup/Usage

  1. Import the Workflow: Download the JSON and import it into your n8n instance.
  2. Configure Credentials:
    • Add your Anthropic API Key to the "Anthropic" node's credentials.
    • (If applicable) Add your OpenAI API Key to any OpenAI nodes you might add or activate.
  3. Configure the n8n Form Trigger:
    • Set up the n8n form with the input fields required for your search visibility dataset generation.
    • Ensure the form is publicly accessible or integrated as needed.
  4. Customize "Edit Fields (Set)" Node: Adjust the fields and values in the "Edit Fields (Set)" node to correctly map and transform your incoming form data.
  5. Customize "Code" Node: Modify the JavaScript code within the "Code" node to implement your specific data manipulation, API call preparation, or conditional logic.
  6. Configure "HTTP Request" Node: Update the URL, method, headers, and body of the "HTTP Request" node to interact with your desired external service.
  7. Configure "Anthropic" Node: Define the prompt and model parameters for the Claude AI to generate the desired search visibility data.
  8. Configure "Convert to File" Node: Specify the desired file format (e.g., CSV, JSON) and how the output data should be structured.
  9. Activate the Workflow: Once configured, activate the workflow.
  10. Trigger the Workflow: Submit data through the configured n8n form to initiate the dataset generation process.

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

Automate RSS to social media pipeline with AI, Airtable & GetLate for multiple platforms

Overview Automates your complete social media content pipeline: sources articles from Wallabag RSS, generates platform-specific posts with AI, creates contextual images, and publishes via GetLate API. Built with 63 nodes across two workflows to handle LinkedIn, Instagram, and Bluesky—with easy expansion to more platforms. Ideal for: Content marketers, solo creators, agencies, and community managers maintaining a consistent multi-platform presence with minimal manual effort. How It Works Two-Workflow Architecture: Content Aggregation Workflow Monitors Wallabag RSS feeds for tagged articles (to-share-linkedin, to-share-instagram, etc.) Extracts and converts content from HTML to Markdown Stores structured data in Airtable with platform assignment AI Generation & Publishing Workflow Scheduled trigger queries Airtable for unpublished content Routes to platform-specific sub-workflows (LinkedIn, Instagram, Bluesky) LLM generates optimized post text and image prompts based on custom brand parameters Optionally generates AI images and hosts them on Imgbb CDN Publishes via GetLate API (immediate or draft mode) Updates Airtable with publication status and metadata Key Features: Tag-based content routing using Wallabag's native system Swappable AI providers (Groq, OpenAI, Anthropic) Platform-specific optimization (tone, length, hashtags, CTAs) Modular design—duplicate sub-workflows to add new platforms in \~30 minutes Centralized Airtable tracking with 17 data points per post Set Up Steps Setup time: \~45-60 minutes for initial configuration Create accounts and get API keys (\~15 min) Wallabag (with RSS feeds enabled) GetLate (social media publishing) Airtable (create base with provided schema—see sticky notes) LLM provider (Groq, OpenAI, or Anthropic) Image service (Hugging Face, Fal.ai, or Stability AI) Imgbb (image hosting) Configure n8n credentials (\~10 min) Add all API keys in n8n's credential manager Detailed credential setup instructions in workflow sticky notes Set up Airtable database (\~10 min) Create "RSS Feed - Content Store" base Add 19 required fields (schema provided in workflow sticky notes) Get Airtable base ID and API key Customize brand prompts (\~15 min) Edit "Set Custom SMCG Prompt" node for each platform Define brand voice, tone, goals, audience, and image preferences Platform-specific examples provided in sticky notes Configure platform settings (\~10 min) Set GetLate account IDs for each platform Enable/disable image generation per platform Choose immediate publish vs. draft mode Adjust schedule trigger frequency Test and deploy Tag test articles in Wallabag Monitor the first few executions in draft mode Activate workflows when satisfied with the output Important: This is a proof-of-concept template. Test thoroughly with draft mode before production use. Detailed setup instructions, troubleshooting tips, and customization guidance are in the workflow's sticky notes. Technical Details 63 nodes: 9 Airtable operations, 8 HTTP requests, 7 code nodes, 3 LangChain LLM chains, 3 RSS triggers, 3 GetLate publishers Supports: Multiple LLM providers, multiple image generation services, unlimited platforms via modular architecture Tracking: 17 metadata fields per post, including publish status, applied parameters, character counts, hashtags, image URLs Prerequisites n8n instance (self-hosted or cloud) Accounts: Wallabag, GetLate, Airtable, LLM provider, image generation service, Imgbb Basic understanding of n8n workflows and credential configuration Time to customize prompts for your brand voice Detailed documentation, Airtable schema, prompt examples, and troubleshooting guides are in the workflow's sticky notes. Category Tags social-media-automation, ai-content-generation, rss-to-social, multi-platform-posting, getlate-api, airtable-database, langchain, workflow-automation, content-marketing

Mikal Hayden-GatesBy Mikal Hayden-Gates
188