Back to Catalog

Search business prospects with natural language using Claude AI and Explorium MCP

exploriumexplorium
1178 views
2/3/2026
Official Page

Explorium Prospects Search Chatbot

Template

Download the following json file and import it to a new n8n workflow:

mcp_to_prospects_to_csv.json

<br />

Overview

This n8n workflow creates a chatbot that understands natural language requests for finding business prospects and automatically:

  • Interprets your query using AI (Claude Sonnet 3.7)
  • Converts it to proper Explorium API filters
  • Validates the API request structure
  • Fetches prospect data from Explorium
  • Exports results as a downloadable CSV file

Perfect for sales teams, recruiters, and business development professionals who need to quickly find and export targeted prospect lists without learning complex API syntax.

Key Features

  • Natural Language Interface: Simply describe who you're looking for in plain English
  • Smart Query Translation: AI converts your request to valid API parameters
  • Built-in Validation: Ensures API calls meet Explorium's requirements
  • Error Recovery: Automatically retries with corrections if validation fails
  • Pagination Support: Handles large result sets automatically
  • CSV Export: Clean, formatted output ready for CRM import
  • Conversation Memory: Maintains context for follow-up queries

Example Queries

The chatbot understands queries like:

  • "Find marketing directors at SaaS companies in New York with 50-200 employees"
  • "Get me CTOs from fintech startups in California"
  • "Show me sales managers at healthcare companies with revenue over $10M"
  • "Find engineers at Microsoft with 3-5 years experience"
  • "Get customer service leads from e-commerce companies in Europe"

Prerequisites

Before setting up this workflow, ensure you have:

  1. n8n instance with chat interface enabled
  2. Anthropic API key for Claude
  3. Explorium API credentials (Bearer token) - Get explorium api key
  4. Basic understanding of n8n chat workflows

Supported Filters

The chatbot can search using these criteria:

Company Filters

  • Size: 1-10, 11-50, 51-200, 201-500, 501-1000, 1001-5000, 5001-10000, 10001+ employees
  • Revenue: Ranges from $0-500K up to $10T+
  • Age: 0-3, 3-6, 6-10, 10-20, 20+ years
  • Location: Countries, regions, cities
  • Industry: Google categories, NAICS codes, LinkedIn categories
  • Name: Specific company names

Prospect Filters

  • Job Level: CXO, VP, Director, Manager, Senior, Entry, etc.
  • Department: Sales, Marketing, Engineering, Finance, HR, etc.
  • Experience: Total months and current role duration
  • Location: Country and region codes
  • Contact Info: Filter by email/phone availability

Installation & Setup

Step 1: Import the Workflow

  1. Copy the workflow JSON from the template
  2. In n8n: WorkflowsAdd WorkflowImport from File
  3. Paste the JSON and click Import

Step 2: Configure Anthropic Credentials

  1. Click on the Anthropic Chat Model1 node
  2. Under Credentials, click Create New
  3. Add your Anthropic API key
  4. Name: "Anthropic API"
  5. Save credentials

Step 3: Configure Explorium Credentials

You'll need to set up Explorium credentials in two places:

For MCP Client:

  1. Click on the MCP Client node
  2. Under Credentials, create new Header Auth
  3. Add your authentication header (usually Authorization: Bearer YOUR_TOKEN)
  4. Save credentials

For API Calls:

  1. Click on the Prospects API Call node
  2. Use the same Header Auth credentials created above
  3. Verify the API endpoint is correct

Step 4: Activate the Workflow

  1. Save the workflow
  2. Click the Active toggle to enable it
  3. The chat interface will now be available

Step 5: Access the Chat Interface

  1. Click on the When chat message received node
  2. Copy the webhook URL
  3. Access this URL in your browser to start chatting

How It Works

Workflow Architecture

  1. Chat Trigger: Receives natural language queries from users
  2. Memory Buffer: Maintains conversation context
  3. AI Agent: Interprets queries and generates API parameters
  4. Validation: Checks API structure against Explorium requirements
  5. API Call: Fetches prospect data with pagination
  6. Data Processing: Formats results for CSV export
  7. File Conversion: Creates downloadable CSV file

Processing Flow

User Query → AI Interpretation → Validation → API Call → CSV Export
     ↑                                  ↓
     └──── Error Correction Loop ←──────┘

Validation Rules

The workflow validates:

  • Filter keys are allowed by Explorium API
  • Values match expected formats (e.g., valid country codes)
  • Range filters have proper gte/lte values
  • No duplicate values in arrays
  • Required structure is maintained

Usage Guide

Basic Conversation Flow

  1. Start with your query:

    "Find me VPs of Sales at software companies in the US"
    
  2. Bot processes and responds:

    • Generates API filters
    • Validates the structure
    • Fetches data
    • Returns CSV download link
  3. Refine if needed:

    "Can you also include directors and filter for companies with 100+ employees?"
    

Query Tips

  • Be specific: Include job titles, departments, company details
  • Use standard terms: "CTO" instead of "Chief Technology Officer"
  • Specify locations: Use country names or standard codes
  • Include size/revenue: Helps narrow results effectively

Advanced Queries

Combine multiple criteria:

"Find engineering managers and senior engineers at B2B SaaS companies 
in New York and California with 50-500 employees and revenue over $5M 
who have been in their role for at least 1 year"

Output Format

The CSV file includes:

  • Prospect ID
  • Name (first, last, full)
  • Location (country, region, city)
  • LinkedIn profile
  • Experience summary
  • Skills and interests
  • Company details
  • Job information
  • Business ID

Troubleshooting

Common Issues

"Validation failed" errors

  • Check that your query uses supported filter values
  • Ensure location names are spelled correctly
  • Verify company sizes/revenues match allowed ranges

No results returned

  • Broaden your search criteria
  • Check if the company exists in Explorium's database
  • Verify filter combinations aren't too restrictive

Chat not responding

  • Ensure workflow is activated
  • Check all credentials are properly configured
  • Verify webhook URL is accessible

Large result sets timing out

  • Try adding more specific filters
  • Limit results by location or company size
  • Use the size parameter (max 10,000)

Error Messages

The bot provides clear feedback:

  • Invalid filters: Shows which filters aren't supported
  • Value errors: Lists correct options for each field
  • API failures: Explains connection or authentication issues

Performance Optimization

Best Practices

  1. Start broad, then narrow: Begin with basic criteria and add filters
  2. Use business IDs: When targeting specific companies
  3. Limit by contact info: Add has_email: true for actionable leads
  4. Batch by location: Process regions separately for large searches

API Limits

  • Maximum 10,000 results per search
  • Pagination handles up to 100 records per page
  • Rate limits apply based on your Explorium subscription

Customization Options

Modify AI Behavior

Edit the AI Agent system message to:

  • Change response format
  • Add custom filters
  • Adjust interpretation logic
  • Include additional instructions

Extend Functionality

Add nodes to:

  • Send results via email
  • Import directly to CRM
  • Schedule recurring searches
  • Create custom reports

Integration Ideas

  • Connect to Slack for team queries
  • Add to CRM workflows
  • Create lead scoring systems
  • Build automated outreach campaigns

Security Considerations

  • API credentials are stored securely in n8n
  • Chat sessions are isolated
  • No prospect data is stored permanently
  • CSV files are generated on-demand

Support Resources

For issues with:

  • n8n platform: Check n8n documentation
  • Explorium API: Contact Explorium support
  • Anthropic/Claude: Refer to Anthropic docs
  • Workflow logic: Review node configurations

n8n Workflow: Search Business Prospects with Natural Language using Claude AI and Explorium MCP

This n8n workflow empowers you to find business prospects using natural language queries, leveraging the power of Claude AI for understanding your request and the Explorium Model Context Protocol (MCP) Client for data retrieval. It streamlines the process of converting a natural language search into actionable business data.

What it does

This workflow performs the following steps:

  1. Listens for a chat message: It is triggered by an incoming chat message containing your natural language query for business prospects.
  2. Processes the query with an AI Agent: The AI Agent, powered by an Anthropic Chat Model (Claude), interprets your natural language request.
  3. Utilizes a Structured Output Parser: The AI Agent's output is then parsed into a structured format, ensuring the subsequent steps receive well-defined data.
  4. Leverages the Explorium MCP Client Tool: The parsed query is fed to the Explorium MCP Client Tool, which interacts with the Explorium platform to search for business prospects based on the interpreted criteria.
  5. Handles potential errors or no results:
    • If the Explorium MCP Client Tool returns results, the workflow proceeds to process them.
    • If no results are found or an error occurs, it provides a fallback message.
  6. Transforms and prepares data:
    • The raw data from Explorium is converted into a file (e.g., CSV) for easy consumption.
    • If multiple prospects are found, the data is split out into individual items for further processing.
  7. Responds with results or an error message: The workflow sends back the generated file containing the prospect data or an informative message if no prospects were found or an error occurred.

Prerequisites/Requirements

To use this workflow, you will need:

  • n8n Instance: A running instance of n8n.
  • Anthropic API Key: For the Anthropic Chat Model (Claude AI). This will need to be configured as an n8n credential.
  • Explorium Account & API Key: For the Explorium MCP Client Tool. This will need to be configured as an n8n credential.

Setup/Usage

  1. Import the workflow: Download the JSON provided and import it into your n8n instance.
  2. Configure Credentials:
    • Set up your Anthropic API Key as an Anthropic Chat Model API credential in n8n.
    • Set up your Explorium API Key as an Explorium MCP Client API credential in n8n.
  3. Activate the workflow: Once the credentials are set, activate the workflow.
  4. Send a chat message: Send a natural language message to the configured chat trigger (e.g., "Find me tech companies in California with more than 500 employees").
  5. Receive results: The workflow will process your request and respond with a file containing the business prospects or a message indicating no results were found.

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.

Ranjan DailataBy Ranjan Dailata
161

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

Daniel NkenchoBy Daniel Nkencho
601

Automate invoice processing with OCR, GPT-4 & Salesforce opportunity creation

PDF Invoice Extractor (AI) End-to-end pipeline: Watch Drive ➜ Download PDF ➜ OCR text ➜ AI normalize to JSON ➜ Upsert Buyer (Account) ➜ Create Opportunity ➜ Map Products ➜ Create OLI via Composite API ➜ Archive to OneDrive. --- Node by node (what it does & key setup) 1) Google Drive Trigger Purpose: Fire when a new file appears in a specific Google Drive folder. Key settings: Event: fileCreated Folder ID: google drive folder id Polling: everyMinute Creds: googleDriveOAuth2Api Output: Metadata { id, name, ... } for the new file. --- 2) Download File From Google Purpose: Get the file binary for processing and archiving. Key settings: Operation: download File ID: ={{ $json.id }} Creds: googleDriveOAuth2Api Output: Binary (default key: data) and original metadata. --- 3) Extract from File Purpose: Extract text from PDF (OCR as needed) for AI parsing. Key settings: Operation: pdf OCR: enable for scanned PDFs (in options) Output: JSON with OCR text at {{ $json.text }}. --- 4) Message a model (AI JSON Extractor) Purpose: Convert OCR text into strict normalized JSON array (invoice schema). Key settings: Node: @n8n/n8n-nodes-langchain.openAi Model: gpt-4.1 (or gpt-4.1-mini) Message role: system (the strict prompt; references {{ $json.text }}) jsonOutput: true Creds: openAiApi Output (per item): $.message.content → the parsed JSON (ensure it’s an array). --- 5) Create or update an account (Salesforce) Purpose: Upsert Buyer as Account using an external ID. Key settings: Resource: account Operation: upsert External Id Field: taxid_c External Id Value: ={{ $json.message.content.buyer.tax_id }} Name: ={{ $json.message.content.buyer.name }} Creds: salesforceOAuth2Api Output: Account record (captures Id) for downstream Opportunity. --- 6) Create an opportunity (Salesforce) Purpose: Create Opportunity linked to the Buyer (Account). Key settings: Resource: opportunity Name: ={{ $('Message a model').item.json.message.content.invoice.code }} Close Date: ={{ $('Message a model').item.json.message.content.invoice.issue_date }} Stage: Closed Won Amount: ={{ $('Message a model').item.json.message.content.summary.grand_total }} AccountId: ={{ $json.id }} (from Upsert Account output) Creds: salesforceOAuth2Api Output: Opportunity Id for OLI creation. --- 7) Build SOQL (Code / JS) Purpose: Collect unique product codes from AI JSON and build a SOQL query for PricebookEntry by Pricebook2Id. Key settings: pricebook2Id (hardcoded in script): e.g., 01sxxxxxxxxxxxxxxx Source lines: $('Message a model').first().json.message.content.products Output: { soql, codes } --- 8) Query PricebookEntries (Salesforce) Purpose: Fetch PricebookEntry.Id for each Product2.ProductCode. Key settings: Resource: search Query: ={{ $json.soql }} Creds: salesforceOAuth2Api Output: Items with Id, Product2.ProductCode (used for mapping). --- 9) Code in JavaScript (Build OLI payloads) Purpose: Join lines with PBE results and Opportunity Id ➜ build OpportunityLineItem payloads. Inputs: OpportunityId: ={{ $('Create an opportunity').first().json.id }} Lines: ={{ $('Message a model').first().json.message.content.products }} PBE rows: from previous node items Output: { body: { allOrNone:false, records:[{ OpportunityLineItem... }] } } Notes: Converts discount_total ➜ per-unit if needed (currently commented for standard pricing). Throws on missing PBE mapping or empty lines. --- 10) Create Opportunity Line Items (HTTP Request) Purpose: Bulk create OLIs via Salesforce Composite API. Key settings: Method: POST URL: https://&lt;your-instance&gt;.my.salesforce.com/services/data/v65.0/composite/sobjects Auth: salesforceOAuth2Api (predefined credential) Body (JSON): ={{ $json.body }} Output: Composite API results (per-record statuses). --- 11) Update File to One Drive Purpose: Archive the original PDF in OneDrive. Key settings: Operation: upload File Name: ={{ $json.name }} Parent Folder ID: onedrive folder id Binary Data: true (from the Download node) Creds: microsoftOneDriveOAuth2Api Output: Uploaded file metadata. --- Data flow (wiring) Google Drive Trigger → Download File From Google Download File From Google → Extract from File → Update File to One Drive Extract from File → Message a model Message a model → Create or update an account Create or update an account → Create an opportunity Create an opportunity → Build SOQL Build SOQL → Query PricebookEntries Query PricebookEntries → Code in JavaScript Code in JavaScript → Create Opportunity Line Items --- Quick setup checklist 🔐 Credentials: Connect Google Drive, OneDrive, Salesforce, OpenAI. 📂 IDs: Drive Folder ID (watch) OneDrive Parent Folder ID (archive) Salesforce Pricebook2Id (in the JS SOQL builder) 🧠 AI Prompt: Use the strict system prompt; jsonOutput = true. 🧾 Field mappings: Buyer tax id/name → Account upsert fields Invoice code/date/amount → Opportunity fields Product name must equal your Product2.ProductCode in SF. ✅ Test: Drop a sample PDF → verify: AI returns array JSON only Account/Opportunity created OLI records created PDF archived to OneDrive --- Notes & best practices If PDFs are scans, enable OCR in Extract from File. If AI returns non-JSON, keep “Return only a JSON array” as the last line of the prompt and keep jsonOutput enabled. Consider adding validation on parsing.warnings to gate Salesforce writes. For discounts/taxes in OLI: Standard OLI fields don’t support per-line discount amounts directly; model them in UnitPrice or custom fields. Replace the Composite API URL with your org’s domain or use the Salesforce node’s Bulk Upsert for simplicity.

Le NguyenBy Le Nguyen
942