Ai-powered lead research & qualification using Relevance AI
Lead Qualification & Smart Outreach β Automated Scoring System
Automate your lead intake, scoring, and outreach pipeline.
This workflow collects leads from forms, enriches and scores them using Relevance AI, routes them by quality, and triggers the right follow-up β all without manual busywork.
π What it Does
- Collects leads from your forms in real-time.
- Enriches each lead (individual + company) for better context.
- Scores leads automatically using Relevance AI templates.
- Routes leads into HOT / WARM / COLD tiers for prioritization.
- Drafts or sends personalized outreach emails for each tier.
- Logs all leads and outcomes into your CRM or Google Sheets.
- Notifies your team (e.g., via Slack) when a hot lead arrives.
π§© Why Use It
- Save time: stop manually sorting through raw leads.
- Focus on the best opportunities: route only top leads to your sales team.
- Personalized outreach: automated but tailored by lead quality.
- Scalable & repeatable: works for startups, agencies, or larger teams.
- Adaptable: swap CRMs, forms, or email providers easily.
π§ Prerequisites & Setup
Before importing or running the workflow, set up these connections:
-
Relevance AI
Clone the tools (Resources provided in the workflow) for lead scoring and company scoring, and copy your API key into the HTTP Request nodes. -
Form Intake
Use n8nβs built-in form trigger or connect Typeform, Tally, HubSpot Forms, or any webhook-based intake. -
CRM or Database
Start with Google Sheets (included in the sample workflow) or connect HubSpot, Salesforce, Pipedrive, Zoho, Airtable, Notion, or any SQL/NoSQL DB. -
Email Provider
Use Gmail (included), or swap in Outlook, HubSpot Email, SendGrid, Mailgun, etc. -
Team Notifications (Optional)
Configure Slack (or other tools) for instant alerts on hot leads.
βοΈ How It Works (Simplified Flow)
- Lead Intake: Collects leads from your form or CRM.
- Lead Enrichment: Uses Relevance AI to score:
- Individual Fit: role, expertise, influence.
- Company Fit: size, industry, market relevance.
- Scoring & Insights: Combines both into a final lead score with labels and notes.
- Routing: Splits leads into HOT / WARM / COLD tiers.
- Outreach:
- HOT β drafts a review-ready email for your team.
- WARM / COLD β auto-sends appropriate follow-up emails.
- Logging & Alerts: Saves structured data to your CRM or sheet and notifies your team of hot leads.
πββοΈ Who is This For
- Startups & SaaS teams that need to prioritize a flood of inbound leads.
- Agencies & consultancies qualifying prospects from ads or webinars.
- Small sales teams that want to spend time only on the best leads.
- Freelancers or solopreneurs who want a lightweight but effective qualification process.
- Automation newbies who want a production-ready system to sell for 1k-3k
π‘ Why It Stands Out
- Real intelligence: uses data-driven Relevance AI scoring rather than static rules.
- Action-oriented: routes and triggers the right next step immediately.
- Personalized yet scalable: adapts outreach to each lead tier.
- Flexible integrations: works with most popular CRMs, forms, and email tools.
π₯ Best Practices & Tips
- Adjust the weighting of individual vs. company scores in your Relevance AI template (default: 40% vs 60%).
- Tune Router thresholds (e.g., HOT β₯ 80, WARM 60-79, COLD < 60) to match your sales goals.
- Add a human approval step for high-value deals.
- Expand with enrichment APIs (e.g., Clearbit, Apollo) for richer lead data.
- Keep all API keys private and out of screenshots or repos.
π With this workflow, Sales teams can focus on building relationships β while the system qualifies and organizes leads automatically OR You can sell to sales teams for ~3k
Note:
Demo data is pinned in some nodes to help you understand what the data looks like. Make sure to unpin those nodes when using for production.
AI-Powered Lead Research & Qualification Workflow
This n8n workflow automates the process of researching and qualifying leads from a Google Sheet using an AI chat model (Google Gemini or OpenRouter) and then notifying the team via Slack or email based on the lead's qualification status.
What it does
This workflow streamlines your lead management by:
- Triggering on Form Submission: Initiates when a new entry is submitted via an n8n form.
- Preparing Lead Data: Takes the submitted lead information and formats it for AI processing.
- AI-Powered Qualification: Sends the lead data to a configured AI chat model (Google Gemini or OpenRouter) to perform research and qualify the lead based on predefined criteria.
- Parsing AI Output: Extracts structured qualification results (e.g., "qualified" or "not qualified") from the AI's response.
- Conditional Notification:
- If the lead is qualified, it sends a notification to a designated Slack channel.
- If the lead is not qualified, it sends an email notification.
- Logging to Google Sheets: Appends the original lead data along with the AI's qualification status to a Google Sheet for record-keeping.
Prerequisites/Requirements
To use this workflow, you will need:
- n8n Instance: A running n8n instance.
- Google Sheets Account: For storing lead data.
- Google Sheets Credential: Configured in n8n to access your spreadsheet.
- AI Chat Model Credential:
- Google Gemini Credential: If using the Google Gemini Chat Model.
- OpenRouter Credential: If using the OpenRouter Chat Model.
- Slack Account: For qualified lead notifications.
- Slack Credential: Configured in n8n.
- Gmail Account: For unqualified lead notifications.
- Gmail Credential: Configured in n8n.
Setup/Usage
- Import the Workflow: Download the provided JSON and import it into your n8n instance.
- Configure Credentials:
- Set up your Google Sheets credential.
- Set up your preferred AI Chat Model credential (Google Gemini or OpenRouter).
- Set up your Slack credential.
- Set up your Gmail credential.
- Customize the n8n Form Trigger:
- Access the "On form submission" node.
- Define the fields for your lead submission form (e.g.,
companyName,website,contactEmail). - Copy the webhook URL to use for your form submissions.
- Adjust the "Edit Fields (Set)" Node:
- Ensure the fields being passed to the AI model are correctly mapped from your form submission.
- Configure the AI Chat Model:
- In the "Basic LLM Chain" node, select either "Google Gemini Chat Model" or "OpenRouter Chat Model" based on your preference and configured credentials.
- Review and adjust the prompt to define your lead qualification criteria for the AI.
- Configure the "Structured Output Parser":
- Ensure the output schema matches the expected response format from your AI model for qualification status.
- Customize the "Switch" Node:
- Verify the conditions for routing qualified vs. unqualified leads based on the AI's output.
- Configure Slack Notification:
- In the "Slack" node, specify the channel and message content for qualified leads.
- Configure Gmail Notification:
- In the "Gmail" node, specify the recipient, subject, and body for unqualified lead emails.
- Configure Google Sheets Output:
- In the "Google Sheets" node, select your spreadsheet and sheet name.
- Map the data fields (including the AI's qualification status) to the correct columns in your sheet.
- Activate the Workflow: Once configured, activate the workflow to start processing lead submissions.
Related Templates
Automate Dutch Public Procurement Data Collection with TenderNed
TenderNed Public Procurement What This Workflow Does This workflow automates the collection of public procurement data from TenderNed (the official Dutch tender platform). It: Fetches the latest tender publications from the TenderNed API Retrieves detailed information in both XML and JSON formats for each tender Parses and extracts key information like organization names, titles, descriptions, and reference numbers Filters results based on your custom criteria Stores the data in a database for easy querying and analysis Setup Instructions This template comes with sticky notes providing step-by-step instructions in Dutch and various query options you can customize. Prerequisites TenderNed API Access - Register at TenderNed for API credentials Configuration Steps Set up TenderNed credentials: Add HTTP Basic Auth credentials with your TenderNed API username and password Apply these credentials to the three HTTP Request nodes: "Tenderned Publicaties" "Haal XML Details" "Haal JSON Details" Customize filters: Modify the "Filter op ..." node to match your specific requirements Examples: specific organizations, contract values, regions, etc. How It Works Step 1: Trigger The workflow can be triggered either manually for testing or automatically on a daily schedule. Step 2: Fetch Publications Makes an API call to TenderNed to retrieve a list of recent publications (up to 100 per request). Step 3: Process & Split Extracts the tender array from the response and splits it into individual items for processing. Step 4: Fetch Details For each tender, the workflow makes two parallel API calls: XML endpoint - Retrieves the complete tender documentation in XML format JSON endpoint - Fetches metadata including reference numbers and keywords Step 5: Parse & Merge Parses the XML data and merges it with the JSON metadata and batch information into a single data structure. Step 6: Extract Fields Maps the raw API data to clean, structured fields including: Publication ID and date Organization name Tender title and description Reference numbers (kenmerk, TED number) Step 7: Filter Applies your custom filter criteria to focus on relevant tenders only. Step 8: Store Inserts the processed data into your database for storage and future analysis. Customization Tips Modify API Parameters In the "Tenderned Publicaties" node, you can adjust: offset: Starting position for pagination size: Number of results per request (max 100) Add query parameters for date ranges, status filters, etc. Add More Fields Extend the "Splits Alle Velden" node to extract additional fields from the XML/JSON data, such as: Contract value estimates Deadline dates CPV codes (procurement classification) Contact information Integrate Notifications Add a Slack, Email, or Discord node after the filter to get notified about new matching tenders. Incremental Updates Modify the workflow to only fetch new tenders by: Storing the last execution timestamp Adding date filters to the API query Only processing publications newer than the last run Troubleshooting No data returned? Verify your TenderNed API credentials are correct Check that you have setup youre filter proper Need help setting this up or interested in a complete tender analysis solution? Get in touch π LinkedIn β Wessel Bulte
π How to transform unstructured email data into structured format with AI agent
This workflow automates the process of extracting structured, usable information from unstructured email messages across multiple platforms. It connects directly to Gmail, Outlook, and IMAP accounts, retrieves incoming emails, and sends their content to an AI-powered parsing agent built on OpenAI GPT models. The AI agent analyzes each email, identifies relevant details, and returns a clean JSON structure containing key fields: From β senderβs email address To β recipientβs email address Subject β email subject line Summary β short AI-generated summary of the email body The extracted information is then automatically inserted into an n8n Data Table, creating a structured database of email metadata and summaries ready for indexing, reporting, or integration with other tools. --- Key Benefits β Full Automation: Eliminates manual reading and data entry from incoming emails. β Multi-Source Integration: Handles data from different email providers seamlessly. β AI-Driven Accuracy: Uses advanced language models to interpret complex or unformatted content. β Structured Storage: Creates a standardized, query-ready dataset from previously unstructured text. β Time Efficiency: Processes emails in real time, improving productivity and response speed. *β Scalability: Easily extendable to handle additional sources or extract more data fields. --- How it works This workflow automates the transformation of unstructured email data into a structured, queryable format. It operates through a series of connected steps: Email Triggering: The workflow is initiated by one of three different email triggers (Gmail, Microsoft Outlook, or a generic IMAP account), which constantly monitor for new incoming emails. AI-Powered Parsing & Structuring: When a new email is detected, its raw, unstructured content is passed to a central "Parsing Agent." This agent uses a specified OpenAI language model to intelligently analyze the email text. Data Extraction & Standardization: Following a predefined system prompt, the AI agent extracts key information from the email, such as the sender, recipient, subject, and a generated summary. It then forces the output into a strict JSON structure using a "Structured Output Parser" node, ensuring data consistency. Data Storage: Finally, the clean, structured data (the from, to, subject, and summarize fields) is inserted as a new row into a specified n8n Data Table, creating a searchable and reportable database of email information. --- Set up steps To implement this workflow, follow these configuration steps: Prepare the Data Table: Create a new Data Table within n8n. Define the columns with the following names and string type: From, To, Subject, and Summary. Configure Email Credentials: Set up the credential connections for the email services you wish to use (Gmail OAuth2, Microsoft Outlook OAuth2, and/or IMAP). Ensure the accounts have the necessary permissions to read emails. Configure AI Model Credentials: Set up the OpenAI API credential with a valid API key. The workflow is configured to use the model, but this can be changed in the respective nodes if needed. Connect the Nodes: The workflow canvas is already correctly wired. Visually confirm that the email triggers are connected to the "Parsing Agent," which is connected to the "Insert row" (Data Table) node. Also, ensure the "OpenAI Chat Model" and "Structured Output Parser" are connected to the "Parsing Agent" as its AI model and output parser, respectively. Activate the Workflow: Save the workflow and toggle the "Active" switch to ON. The triggers will begin polling for new emails according to their schedule (e.g., every minute), and the automation will start processing incoming messages. --- Need help customizing? Contact me for consulting and support or add me on Linkedin.
Tax deadline management & compliance alerts with GPT-4, Google Sheets & Slack
AI-Driven Tax Compliance & Deadline Management System Description Automate tax deadline monitoring with AI-powered insights. This workflow checks your tax calendar daily at 8 AM, uses GPT-4 to analyze upcoming deadlines across multiple jurisdictions, detects overdue and critical items, and sends intelligent alerts via email and Slack only when immediate action is required. Perfect for finance teams and accounting firms who need proactive compliance management without manual tracking. ποΈπ€π Good to Know AI-Powered: GPT-4 provides risk assessment and strategic recommendations Multi-Jurisdiction: Handles Federal, State, and Local tax requirements automatically Smart Alerts: Only notifies executives when deadlines are overdue or critical (β€3 days) Priority Classification: Categorizes deadlines as Overdue, Critical, High, or Medium priority Dual Notifications: Critical alerts to leadership + daily summaries to team channel Complete Audit Trail: Logs all checks and deadlines to Google Sheets for compliance records How It Works Daily Trigger - Runs at 8:00 AM every morning Fetch Data - Pulls tax calendar and company configuration from Google Sheets Analyze Deadlines - Calculates days remaining, filters by jurisdiction/entity type, categorizes by priority AI Analysis - GPT-4 provides strategic insights and risk assessment on upcoming deadlines Smart Routing - Only sends alerts if overdue or critical deadlines exist Critical Alerts - HTML email to executives + Slack alert for urgent items Team Updates - Slack summary to finance channel with all upcoming deadlines Logging - Records compliance check results to Google Sheets for audit trail Requirements Google Sheets Structure Sheet 1: TaxCalendar DeadlineID | DeadlineName | DeadlineDate | Jurisdiction | Category | AssignedTo | IsActive FED-Q1 | Form 1120 Q1 | 2025-04-15 | Federal | Income | John Doe | TRUE Sheet 2: CompanyConfig (single row) Jurisdictions | EntityType | FiscalYearEnd Federal, California | Corporation | 12-31 Sheet 3: ComplianceLog (auto-populated) Date | AlertLevel | TotalUpcoming | CriticalCount | OverdueCount 2025-01-15 | HIGH | 12 | 3 | 1 Credentials Needed Google Sheets - Service Account OAuth2 OpenAI - API Key (GPT-4 access required) SMTP - Email account for sending alerts Slack - Bot Token with chat:write permission Setup Steps Import workflow JSON into n8n Add all 4 credentials Replace these placeholders: YOURTAXCALENDAR_ID - Tax calendar sheet ID YOURCONFIGID - Company config sheet ID YOURLOGID - Compliance log sheet ID C12345678 - Slack channel ID tax@company.com - Sender email cfo@company.com - Recipient email Share all sheets with Google service account email Invite Slack bot to channels Test workflow manually Activate the trigger Customizing This Workflow Change Alert Thresholds: Edit "Analyze Deadlines" node: Critical: Change <= 3 to <= 5 for 5-day warning High: Change <= 7 to <= 14 for 2-week notice Medium: Change <= 30 to <= 60 for 2-month lookout Adjust Schedule: Edit "Daily Tax Check" trigger: Change hour/minute for different run time Add multiple trigger times for tax season (8 AM, 2 PM, 6 PM) Add More Recipients: Edit "Send Email" node: To: cfo@company.com, director@company.com CC: accounting@company.com BCC: archive@company.com Customize Email Design: Edit "Format Email" node to change colors, add logo, or modify layout Add SMS Alerts: Insert Twilio node after "Is Critical" for emergency notifications Integrate Task Management: Add HTTP Request node to create tasks in Asana/Jira for critical deadlines Troubleshooting | Issue | Solution | |-------|----------| | No deadlines found | Check date format (YYYY-MM-DD) and IsActive = TRUE | | AI analysis failed | Verify OpenAI API key and account credits | | Email not sending | Test SMTP credentials and check if critical condition met | | Slack not posting | Invite bot to channel and verify channel ID format | | Permission denied | Share Google Sheets with service account email | π Professional Services Need help with implementation or customization? Our team offers: π― Custom workflow development π’ Enterprise deployment support π Team training sessions π§ Ongoing maintenance π Custom reporting & dashboards π Additional API integrations Discover more workflows β Get in touch with us