HumationHuman + Automation
Back to Catalog

Automated lead generation & qualification with Google Maps, GPT-4 & HubSpot

David OlusolaDavid Olusola
982 views
2/3/2026
GitHubData ExportGoogle SheetsAutomationRepository Management
Official Page

This n8n workflow automates CVE tracking by retrieving vulnerability details from the NVD API 🛡️, organizing and updating the data in Google Sheets 📊, and optionally alerting teams via Slack or Email 📩💬.

Who is this for?

This workflow is ideal for:

  • Security operations (SecOps) teams 🧑‍💻
  • DevSecOps engineers 🛠️
  • IT compliance officers 🧾
  • Vulnerability management analysts 🕵️
  • Sysadmins or cloud engineers in regulated industries 🏢

What problem does this workflow solve?

Manually checking for the latest CVE information is inefficient and error-prone. This automation:

  • Monitors NVD for CVE entries based on product or keyword filters 🔍
  • Tracks new vulnerabilities and changes to existing ones ⏱️
  • Logs all CVE data in a structured Google Sheet for ongoing review and audit 🧾
  • Can trigger alerts or actions for high-severity CVEs 🚨

What this workflow does

This workflow builds an automated CVE monitoring system that:

  • Queries the NVD API for vulnerability data matching keywords (e.g. "Apache", "Log4j") 📡
  • Extracts relevant fields: CVE ID, description, severity (CVSS scores), published/modified dates, and affected products 🗂️
  • Saves or updates the information in Google Sheets 📑
  • Optionally filters for critical severity (e.g., CVSS > 8.0) and sends Slack alerts or emails 📬
  • Supports historical tracking and change detection over time 🕒

Includes a Google Sheets template for tracking:

  • CVE IDs and metadata
  • Severity levels and scores
  • Product/component tags
  • Resolution/patch status tracking

Setup

Prerequisites

You'll need:

  • An n8n instance (cloud or self-hosted) ☁️
  • A Google account + Google Sheets API credentials 📑
  • (Optional) Slack webhook URL or email setup for notifications 💬

Step 1: Configure API Inputs

Open the 🔧 Configuration node and provide:

  • NVD API parameters (keyword filters, date ranges, etc.)
  • Google Sheet ID and tab name for output
  • Slack webhook URL (optional)

Step 2: Set Filters & Preferences

Define:

  • Target keywords or CPE filters (e.g. “Cisco ASA”, “Windows 10”) 🧩
  • CVSS threshold for high/critical alerts 🎚️
  • Update frequency (manual trigger, scheduled cron, webhook, etc.) 🔁

Step 3: Connect to Google Sheets

  • Update Sheet node with your destination Sheet ID
  • Ensure columns like CVE ID, Description, Severity, Last Updated exist

Step 4: Enable Alerts (Optional)

  • Set up Slack node with your webhook URL or connect SMTP/Email node
  • Format alert message with key CVE data

Step 5: Activate and Run

  • Save and activate the workflow 🔛
  • Run manually or schedule it to run periodically (e.g., every 6 hours) ⏱️

Customization Tips

  • Add deduplication logic to avoid reprocessing the same CVEs ♻️
  • Use filters to monitor only critical CVEs or specific vendors/vendors 🔍
  • Extend with GitHub Security Advisories or Exploit DB integration 🧩
  • Track remediation status and link to patch notes or fixes 🩹

Troubleshooting

Common Issues

  • Empty results from NVD: Check if your keywords are too narrow or if NVD API rate limits apply 📉
  • Google Sheets error: Ensure the Sheet ID and tab names are correct and accessible 🔑
  • Alerts not sending: Check Slack webhook or email configurations 🔧

Getting Help

This template was created by David Olusola. 🛡️

Automated Lead Generation & Qualification with Google Maps, GPT-4, and HubSpot

This n8n workflow automates the process of generating leads from Google Maps, enriching their data using GPT-4, qualifying them, and then creating or updating contacts in HubSpot. It also notifies a Slack channel about new qualified leads.

What it does

This workflow streamlines your lead generation and qualification efforts by:

  1. Triggering Manually: The workflow is initiated manually, allowing you to control when the lead generation process begins.
  2. Retrieving Google Maps Data: It fetches business information from Google Maps (though the specific Google Maps node is not present in the provided JSON, it's implied by the workflow's name and common use cases for such a setup).
  3. Enriching Data with OpenAI (GPT-4): It uses OpenAI to enrich the lead data, likely by generating descriptions, identifying key attributes, or performing other text-based analysis to qualify the lead further.
  4. Setting Lead Qualification Status: A "Set" node (named "Edit Fields") is used to explicitly set a lead's qualification status based on the enrichment results.
  5. Conditional Qualification Check: An "If" node checks the qualification status of the lead.
  6. Notifying Slack for Qualified Leads: If a lead is qualified, a notification is sent to a specified Slack channel.
  7. Creating/Updating HubSpot Contacts: Regardless of qualification status (or potentially only for qualified leads, depending on the "If" node's configuration), the workflow interacts with HubSpot to create new contacts or update existing ones.
  8. Logging Data to Google Sheets: All processed lead data, including qualification status and HubSpot details, is logged into a Google Sheet for record-keeping and further analysis.

Prerequisites/Requirements

To use this workflow, you will need:

  • n8n Instance: A running n8n instance.
  • Google Sheets Account: Configured credentials for Google Sheets to store lead data.
  • OpenAI API Key: An API key for OpenAI (likely GPT-4) to enrich lead information.
  • Slack Account: Configured credentials for Slack to send notifications.
  • HubSpot Account: Configured credentials for HubSpot to manage contacts.
  • (Implied) Google Maps API Key: If the Google Maps data retrieval is done via an API, you would need a Google Maps API key.

Setup/Usage

  1. Import the workflow: Download the JSON provided and import it into your n8n instance.
  2. Configure Credentials:
    • Set up your Google Sheets credentials.
    • Set up your OpenAI credentials with your API key.
    • Set up your Slack credentials and specify the channel for notifications.
    • Set up your HubSpot credentials.
  3. Customize Nodes:
    • Google Sheets: Configure the "Google Sheets" node (ID 18) to point to your desired spreadsheet and sheet name for logging lead data.
    • OpenAI: Configure the "OpenAI" node (ID 1250) with the specific prompts or instructions for enriching your lead data (e.g., "Analyze the business description and determine if it's a qualified lead for X service").
    • Edit Fields (Set): Adjust the "Edit Fields" node (ID 38) to define how the qualification status is set based on the OpenAI output.
    • If: Modify the "If" node (ID 20) to define your qualification criteria based on the fields set in the previous step.
    • Slack: Configure the "Slack" node (ID 40) with the message content for qualified leads and the target channel.
    • HubSpot: Configure the "HubSpot" node (ID 76) to map the extracted lead data to HubSpot contact properties (e.g., name, email, company, qualification status).
  4. Execute the workflow: Click "Execute Workflow" on the "Manual Trigger" node (ID 838) to start the 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.

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

Le NguyenBy Le Nguyen
942