AI-powered lead generation with Apollo, GPT-4, and Telegram to database
AI-Powered Lead Generation with Apollo, GPT-4, and Telegram to Database
Overview
This intelligent lead generation workflow transforms voice commands or text input into verified prospect lists through automated Apollo.io scraping. The system processes natural language requests, extracts search parameters using AI, and delivers clean, verified contact data directly to your database.
Key Features
🎤 Voice & Text Input Processing
- Voice Recognition: Converts audio messages to text using OpenAI's transcription API
- Natural Language Processing: AI agent interprets requests and extracts search criteria
- Flexible Input: Supports both voice commands and text messages
🔍 Smart Lead Scraping
- Apollo.io Integration: Automated scraping using official Apollo.io API
- Dynamic URL Generation: Builds search URLs based on extracted parameters
- Intelligent Parsing: Processes location, industry, and job title criteria
✅ Email Verification & Filtering
- Verified Emails Only: Filters results to include only verified email addresses
- Duplicate Prevention: Compares against existing database to avoid duplicates
- Data Quality Control: Ensures high-quality prospect data
📊 Automated Data Management
- Database Integration: Automatic storage in PostgreSQL/Supabase
- Structured Data: Organizes contacts with complete profile information
- Real-time Updates: Instant database updates with new prospects
How It Works
- Input Processing: Receive voice message or text command
- AI Analysis: Extract search parameters (location, industry, job titles)
- URL Construction: Build Apollo.io search URL with extracted criteria
- Data Scraping: Retrieve prospect data via Apollo.io API
- Email Verification: Filter for verified email addresses only
- Duplicate Check: Compare against existing database records
- Data Storage: Save new prospects to database
- Confirmation: Send success notification with count of new leads
Supported Search Parameters
- Location: City, state, country combinations
- Industry: Business sectors and verticals
- Job Titles: Executive roles, departments, seniority levels
- Company Size: Organization scale and employee count
Data Fields Extracted
Contact Information
- First Name & Last Name
- Email Address (verified only)
- LinkedIn Profile URL
- Phone Number (when available)
Professional Details
- Current Job Title
- Company Name
- Industry
- Seniority Level
- Employment History
Location Data
- City & State
- Country
- Full Location String
Company Information
- Website URL
- Business Industry
- Organization Details
Technical Architecture
Core Components
- n8n Workflow Engine: Orchestrates the entire process
- OpenAI Integration: Powers voice transcription and AI analysis
- Apollo.io API: Source for prospect data
- PostgreSQL/Supabase: Database storage and management
API Integrations
- OpenAI Whisper API for voice transcription
- OpenAI GPT for natural language processing
- Apollo.io API for lead data retrieval
- Supabase API for database operations
Use Cases
Sales Teams
- Quickly build prospect lists for outreach campaigns
- Target specific industries or job roles
- Maintain clean, verified contact databases
Marketing Professionals
- Generate targeted lead lists for campaigns
- Research prospects in specific markets
- Build comprehensive contact databases
Business Development
- Identify potential partners or clients
- Research competitive landscapes
- Generate contact lists for networking
Recruitment
- Find candidates in specific locations
- Target particular job roles or industries
- Build talent pipeline databases
Benefits
⚡ Speed & Efficiency
- Voice commands for instant lead generation
- Automated processing eliminates manual work
- Batch processing for large prospect lists
🎯 Precision Targeting
- AI-powered parameter extraction
- Flexible search criteria combinations
- Industry and role-specific filtering
📈 Data Quality
- Verified email addresses only
- Duplicate prevention
- Structured, consistent data format
🔄 Automation
- End-to-end automated workflow
- Real-time database updates
- Instant confirmation notifications
Setup Requirements
Prerequisites
- n8n workflow platform
- OpenAI API access
- Apollo.io API credentials
- PostgreSQL or Supabase database
- Messaging platform integration
Configuration Steps
- Import workflow into n8n
- Configure API credentials
- Set up database connections
- Customize search parameters
- Test with sample voice/text input
Customization Options
Search Parameters
- Modify location formats
- Add custom industry categories
- Adjust job title variations
- Set result limits
Data Processing
- Customize field mappings
- Add data validation rules
- Implement additional filters
- Configure output formats
Integration Options
- Connect to CRM systems
- Add email marketing tools
- Integrate with sales platforms
- Export to various formats
Success Metrics
- Processing Speed: Voice-to-database in under 30 seconds
- Data Accuracy: 95%+ verified email addresses
- Automation Level: 100% hands-free operation
- Scalability: Process 500+ leads per request
Transform your lead generation process with intelligent automation that understands natural language and delivers verified prospects directly to your database.
AI-Powered Lead Generation with Apollo, GPT-4, and Telegram to Database
This n8n workflow automates the process of generating leads, enriching them with AI, and storing them in a database, with human-in-the-loop approval via Telegram. It's designed to streamline lead acquisition by leveraging Apollo.io for initial discovery, OpenAI's GPT-4 for lead qualification and data extraction, and a database (PostgreSQL or Supabase) for storage, all while providing a Telegram interface for lead approval.
What it does
- Triggers on Telegram Message: The workflow starts when a specific command or message is received in Telegram.
- Initial Lead Search (No-Op): A placeholder "No Operation" node is present, which could be extended to initiate a lead search in a tool like Apollo.io based on the Telegram input.
- Human-in-the-Loop Approval (Telegram): Sends a message to a Telegram chat for human review and approval of the generated lead data. This allows for manual verification before proceeding.
- Filters Approved Leads: Based on the Telegram response, it filters for approved leads.
- Processes Approved Leads with AI Agent:
- AI Agent (Langchain): Utilizes an AI agent (likely GPT-4 via OpenAI Chat Model) to process the lead data.
- Simple Memory: Incorporates a memory buffer to maintain context during the AI agent's operation.
- Structured Output Parser: Ensures the AI agent's output is parsed into a structured format (e.g., JSON) for consistent data handling.
- OpenAI (GPT-4): Interacts with the OpenAI API to perform tasks such as lead qualification, extracting specific data points, or generating summaries.
- Edits Fields (Set): Transforms and renames fields to match the target database schema.
- Compares with Existing Data (Compare Datasets): Checks if the new lead already exists in the database to prevent duplicates.
- Filters for New Leads: Only new and unique leads are passed to the next step.
- Stores Leads in Database:
- PostgreSQL: Inserts or updates the lead data in a PostgreSQL database.
- Supabase: Alternatively, inserts or updates the lead data in a Supabase database.
- Limits Output: A "Limit" node is present, potentially to control the number of items processed or stored in a single run.
- Code Execution: A "Code" node allows for custom JavaScript logic, which could be used for advanced data manipulation, validation, or integration.
Prerequisites/Requirements
- n8n Account/Instance: A running n8n instance.
- Telegram Bot: A Telegram bot token and chat ID for sending and receiving messages.
- OpenAI API Key: An API key for OpenAI (GPT-4 or similar models).
- PostgreSQL Database OR Supabase Project: Access to a PostgreSQL database or a Supabase project for storing lead data.
- Apollo.io Account (Optional, for full lead generation): While not explicitly configured in the provided JSON, the workflow name suggests integration with Apollo.io for lead sourcing. This would require an Apollo.io API key or similar access.
Setup/Usage
- Import the Workflow: Import the provided JSON into your n8n instance.
- Configure Credentials:
- Telegram: Set up your Telegram Bot API credentials.
- OpenAI: Configure your OpenAI API Key.
- PostgreSQL / Supabase: Set up credentials for your chosen database.
- Configure Telegram Trigger:
- Set the "Telegram Trigger" node to listen for specific commands or messages that should initiate the lead generation process.
- Customize AI Agent:
- Adjust the "AI Agent" and "OpenAI Chat Model" nodes to define the specific prompts, models, and parameters for lead qualification and data extraction.
- Modify the "Structured Output Parser" to match the expected output format from your AI model.
- Map Data Fields:
- In the "Edit Fields (Set)" node, map the extracted AI data to your desired database schema.
- Configure Database Nodes:
- In the "Postgres" or "Supabase" node, specify the table name and the fields to insert/update.
- Activate the Workflow: Once configured, activate the workflow to start processing Telegram messages and generating leads.
- Initiate from Telegram: Send the configured command or message to your Telegram bot to trigger the workflow.
- Approve Leads: Respond to the Telegram approval messages to guide the workflow.
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.
By Ranjan DailataGenerate 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 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://<your-instance>.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.
By Le Nguyen