Apollo data enrichment using Company Id, Google Sheets & Telegram

67 views

2/3/2026

AI Natural Language Processing Event Creation Automation Google Calendar

Apollo Data Enrichment Using Company Id to automatically finds contacts for companies listed in your Google Sheet, enriches each person with emails and phone numbers via Apollo’s API, and writes verified contacts back to your procurement sheet while notifying your team on Telegram.

Screenshot 20250819 at 18.54.11.png

It removes the manual copy-paste scavenger hunt and turns hours of research into minutes like hiring a tireless intern who never asks for coffee.

💡 Why Use Apollo Data Enrichment Based Using Company Id?

Save time: Automates enrichment of contacts from company IDs so you stop spending hours looking up emails and phone numbers.
Solve noisy data: Only queries relevant titles and email status filters so your outbound team sees fewer dead leads.
Improve outcomes: Ensures enriched, outreach ready contacts (emails/phones) land in your sheet. Faster follow-up, higher reply rates.
Competitive edge: Targets granular procurement roles (manager/head/lead/director) and marks processed companies to avoid duplicate work makes your outreach becomes smarter and cleaner.

⚡ Perfect For

Outbound/BDR teams: who need contacts ready for outreach
Data ops / Growth teams: who maintain lead lists and enrichment pipelines

🔧 How It Works

⏱ Trigger: Scheduled trigger “Run Every X Minutes” that periodically picks unprocessed companies.
📎 Process: Reads companies from the Google Sheet, fetches the Apollo Company ID, builds title/seniority/email-status filters, calls Apollo mixed_people/search and then people/match for full contact details.
🤖 Smart Logic: Title Converter separates seniority from core titles, the Build Search Filters code node constructs precise Apollo query strings, and an If node branches when no people are found.
💌 Output: Writes enriched contacts into the Purchasing / Procurement Roles Google Sheet, updates Leadsfeeder to mark companies as processed, accepts phone updates via webhook and notifies via Telegram.

🔐 Quick Setup

Import JSON file to your n8n instances
Add credentials: Google Sheets OAuth2, Apollo API Key (HTTP Header Auth), Telegram Bot Token
Customize: adjust person titles array, person_seniorities, contact_email_status, Page and Per Page settings in the Define Search Settings / Title Converter nodes
Update: Google Sheet Data
Test: run the workflow with a small set of companies and verify rows appear in the sheet and Telegram notifications arrive

🧩 You'll Need

Active n8n instances
Google account with access to spreadsheet id
Apollo API Key (HTTP Header Auth)
Telegram Bot token (for alerts)
Webhook enabled

🛠️ Level Up Ideas

Push enriched contacts directly into your CRM (HubSpot, Pipedrive, Salesforce) to start sequences automatically
Add deduplication and scoring (e.g., prefer “verified” or “likely to engage” emails) and deprioritize unverified ones
Respect rate limits and add exponential backoff + request batching for large company lists

Support

Made by: Khaisa Studio Category: lead generation, data enrichment pipeline, apollo.io enrichment

Need custom work? Contact Us!

Apollo Data Enrichment and Notification Workflow

This n8n workflow automates the process of enriching company data from Apollo.io, updating a Google Sheet, and sending notifications via Telegram. It's designed to handle a list of company IDs, fetch their details, and keep a central spreadsheet updated.

What it does

This workflow streamlines the process of data enrichment by:

Triggering on a Schedule: The workflow can be configured to run at specified intervals (e.g., daily, weekly) to process new or updated data.
Reading Company IDs from Google Sheets: It fetches a list of company IDs from a designated Google Sheet.
Iterating through Company IDs: Each company ID is processed individually to fetch its details.
Enriching Data with Apollo.io: For each company ID, it makes an API call to Apollo.io to retrieve comprehensive company information.
Transforming Data: The fetched data is transformed and formatted to extract relevant fields for the Google Sheet and Telegram message.
Conditional Processing: It checks if the Apollo.io API call was successful and if company data was found.
Updating Google Sheets: If company data is found, it updates the Google Sheet with the enriched information.
Sending Telegram Notifications:
- If company data is successfully enriched and updated, a success message is sent to a Telegram chat.
- If a company ID is not found in Apollo.io, a notification is sent to Telegram.
- If the Apollo.io API call fails, an error message is sent to Telegram.
Error Handling: An error workflow is triggered if any part of the main workflow fails, allowing for robust error notifications.

Prerequisites/Requirements

To use this workflow, you will need:

n8n Instance: A running n8n instance.
Google Sheets Account: With a spreadsheet containing a list of company IDs.
Apollo.io API Key: An API key for Apollo.io to access company data.
Telegram Bot Token and Chat ID: A Telegram bot set up and the chat ID where notifications should be sent.
n8n Credentials: Configured credentials for Google Sheets (OAuth 2.0 or API Key), Apollo.io (HTTP Basic Auth or API Key), and Telegram (Bot Token).

Setup/Usage

Import the Workflow: Download the provided JSON and import it into your n8n instance.
Configure Credentials:
- Google Sheets: Set up a Google Sheets credential. Ensure the service account or OAuth application has read/write access to your target spreadsheet.
- Apollo.io: Create an HTTP Request credential for Apollo.io. This will likely involve setting your Apollo.io API key in the headers or as a query parameter as required by their API documentation.
- Telegram: Set up a Telegram credential using your bot token.
Configure Nodes:
- Schedule Trigger (ID: 839): Adjust the schedule as needed (e.g., daily, hourly).
- Google Sheets (ID: 18):
  - Specify the Spreadsheet ID and Sheet Name where your company IDs are located.
  - Configure the "Read" operation to fetch the column containing company IDs.
- HTTP Request (ID: 19):
  - Update the URL to the Apollo.io company enrichment endpoint.
  - Configure the Headers or Query Parameters to include your Apollo.io API key.
  - Ensure the request body or parameters are correctly mapped to send the company ID from the Google Sheet.
- Edit Fields (Set) (ID: 38): Review and adjust the fields being set to match the data structure you expect from Apollo.io and the format required for your Google Sheet.
- If (ID: 20):
  - Verify the conditions for checking successful API responses and the presence of company data.
- Google Sheets (ID: 18 - Update):
  - Configure this node to Update the Google Sheet.
  - Map the enriched data fields to the correct columns in your spreadsheet, using the company ID as the lookup key.
- Telegram (ID: 49):
  - Enter your Chat ID for notifications.
  - Customize the success, "not found", and error messages as desired.
- Error Trigger (ID: 12): This node is typically used in a separate error workflow. If you want specific error handling, ensure you have an error workflow configured in n8n that starts with this node.
Activate the Workflow: Once configured, activate the workflow to start the automated data enrichment process.

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 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

By 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://<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

942