Score product-qualified leads with Amplitude, Claude & PDL for sales routing

Connor Provines

97 views

2/3/2026

Download Automation Email File System Attachment

Official Page

AI-Powered Product-Qualified Lead (PQL) Scoring & Sales Routing

One-Line Description

Automatically score product usage signals from Amplitude cohorts and route hot leads to sales with enriched context.

Detailed Description

What it does:

This workflow transforms behavioral data into sales-ready leads by instantly detecting when users hit your PQL threshold, enriching their profile with company intelligence, and using AI to score their conversion potential. Hot leads are routed directly to sales with personalized conversation starters, while warm and cold leads enter appropriate nurture sequences.

Who it's for:

Product-led growth (PLG) teams bridging the gap between product adoption and sales conversion
Sales development teams needing real-time alerts on high-intent users with actionable context
Revenue operations professionals optimizing lead handoff processes between product and sales

Key Features:

Real-time PQL detection - Triggers instantly when users enter Amplitude behavior cohorts, eliminating manual lead review
Multi-source enrichment - Combines product usage data with company intelligence from People Data Labs and AI-powered research
AI-driven scoring - Evaluates usage intensity, ICP fit, intent signals, and timing to produce 0-10 lead scores with breakdown reasoning
Smart routing logic - Automatically categorizes leads as hot (8-10), warm (5-7), or cold (0-4) for appropriate follow-up workflows
Sales enablement context - Provides conversation starters, key insights, red flags, and handoff recommendations tailored to each lead
Customizable criteria - References external Google Doc for PQL rules, allowing non-technical teams to update scoring logic

How it works:

Trigger: Amplitude fires webhook when user enters predefined PQL cohort based on product usage patterns
Enrichment: Pulls company data from People Data Labs and conducts AI research on company stage, tech sophistication, and budget indicators
AI Scoring: Agent evaluates combined usage + enrichment data against ICP criteria stored in Google Docs, producing structured scoring output
Routing: High-scoring leads (hot) generate formatted Slack alerts for immediate sales outreach; warm/cold leads could trigger email sequences (not shown in this template)

Setup Requirements

Prerequisites:

Amplitude account with cohort webhook capability (Growth plan or higher)
People Data Labs API key for company/person enrichment (paid credits required)
Perplexity API for AI-powered company research
Anthropic Claude API for PQL scoring logic
Google Gemini API for Slack message formatting
Slack workspace with OAuth app configured for posting messages
Google Docs containing your PQL criteria and ICP definition (publicly readable or authenticated access)

Estimated Setup Time:

45-60 minutes including API credential configuration, Amplitude cohort definition, and PQL criteria document creation

Installation Notes

Amplitude cohort setup: Define your PQL cohort using behavioral criteria (e.g., "Users who viewed 5+ pages AND invited team members in last 7 days"). Configure webhook to fire on cohort entry.
PQL criteria document: Create a Google Doc outlining your scoring components (usage intensity factors, ICP requirements, intent signals). Update the Google Docs Tool node with your document URL.
Free email filtering: The workflow includes logic to flag free email domains (Gmail, Yahoo, etc.) which you may want to route differently
Testing tip: Use Amplitude's "Test Webhook" feature to send sample payloads before going live

Customization Options

Replace People Data Labs with Clearbit, Apollo, or other enrichment providers by swapping the HTTP Request node
Add CRM integration to automatically create opportunities or update lead scores in Salesforce/HubSpot
Extend routing paths by adding branches for warm/cold leads (e.g., trigger email sequences via Customer.io, Braze)
Adjust scoring weights by modifying the AI agent prompt or criteria document without touching workflow logic
Multi-channel alerts by duplicating output nodes to send to email, SMS, or CRM tasks in addition to Slack

Use Case Examples

SaaS PLG companies: Automatically escalate free trial users who hit usage milestones (API calls, integrations connected, team invites sent) to sales for upgrade conversations
Developer tools: Identify enterprise-ready accounts based on team size growth, deployment patterns, and GitHub integration usage, routing to enterprise sales team
B2B marketplaces: Surface buyers showing high-intent behavior (multiple searches, saved items, pricing page views) to account executives with company context for proactive outreach

Score Product Qualified Leads with Amplitude, Claude, & PDL for Sales Routing

This n8n workflow automates the process of scoring Product Qualified Leads (PQLs) by enriching lead data, generating a PQL score using an AI agent, and routing high-scoring leads to sales via Slack. It simplifies lead qualification, ensuring sales teams focus on the most promising prospects.

What it does

This workflow performs the following steps:

Receives Lead Data: It starts by listening for incoming lead data via a webhook. This data is expected to contain an email address.
Enriches Lead Data with PDL: It uses the PDL (People Data Labs) API to enrich the lead's profile based on their email, gathering additional professional and demographic information.
Enriches Lead Data with Amplitude: It queries the Amplitude API to retrieve usage data and behavioral insights for the lead's user ID.
Merges Data: It combines the enriched data from PDL and Amplitude into a single dataset.
Prepares Data for AI Agent: It processes the merged data to extract relevant fields and formats them into a concise summary suitable for an AI agent.
Generates PQL Score with AI Agent (Claude & Perplexity):
- It utilizes an AI Agent powered by an Anthropic Chat Model (Claude) to analyze the combined lead data.
- The AI Agent is equipped with a "Think" tool to reason through the data and a "Perplexity" tool to perform external searches if needed.
- It generates a PQL score and a brief justification based on the provided lead and usage data.
Filters High-Scoring Leads: It filters the leads, allowing only those with a PQL score above a predefined threshold (e.g., 70) to proceed.
Notifies Sales on Slack: For high-scoring PQLs, it sends a detailed notification to a specified Slack channel, including the PQL score, justification, and key lead details.

Prerequisites/Requirements

To use this workflow, you will need:

n8n Instance: A running n8n instance.
Webhook: An endpoint configured to send lead data (at minimum, an email address) to the n8n webhook.
PDL (People Data Labs) API Key: For lead data enrichment.
Amplitude API Key: For user behavior and usage data.
Anthropic API Key: For the Claude AI model used by the AI Agent.
Perplexity API Key: For the Perplexity search tool used by the AI Agent.
Slack Account & API Token: To post notifications to a Slack channel.

Setup/Usage

Import the Workflow: Import the provided JSON into your n8n instance.
Configure Credentials:
- Set up credentials for PDL, Amplitude, Anthropic, and Perplexity within n8n.
- Configure your Slack credential.
Activate Webhook: Once imported, activate the "Webhook" node and copy its URL. This is the endpoint where you will send your lead data.
Configure Nodes:
- HTTP Request (PDL): Ensure the API key is correctly configured in the credentials.
- HTTP Request (Amplitude): Ensure the API key and any necessary Amplitude project/organization IDs are configured.
- AI Agent:
  - Verify the "Anthropic Chat Model" is correctly linked to your Anthropic credential.
  - Verify the "Perplexity" tool is correctly linked to your Perplexity credential.
  - Review the prompt for the AI Agent to ensure it aligns with your PQL scoring criteria.
- Filter: Adjust the PQL score threshold (item.json.pqlScore > 70) in the "Filter" node if desired.
- Slack: Configure the Slack channel ID where you want to receive PQL notifications.
Test the Workflow: Send a test lead payload to the webhook URL to ensure the workflow runs as expected and notifications are sent to Slack for qualified leads.

This workflow provides a robust and intelligent way to qualify leads, leveraging data enrichment and AI to streamline your sales processes.

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