Lemlist Email Reply Classifier with HubSpot & Slack Integration

High-Level Summary

This workflow automates the processing of email replies from Lemlist campaigns by classifying them using OpenAI, then taking appropriate actions in HubSpot and Slack. When a lead replies to your email campaign, the workflow captures the reply, uses AI to categorize it as "interested", "out of office", "unsubscribe", or "other", and then executes different actions based on the classification. This saves sales teams hours of manual triage and ensures no lead falls through the cracks.

Step-by-Step Node Breakdown

  1. Lemlist - Lead Replied (Webhook Trigger) — This is a Lemlist trigger node that listens for the emailsReplied event. It activates the workflow whenever a lead replies to one of your Lemlist campaign emails. The isFirst option is set to true, meaning it only triggers on the first reply from each lead. (No auth required for trigger; Lemlist sends data via webhook)

  2. OpenAI (AI Classification) — Receives the email reply text from the trigger and classifies it into one of four categories: interested, Out of office, unsubscribe, or other. The prompt instructs the AI to analyze the reply content and return the appropriate category. Parameters: temperature: 0 (deterministic output), maxTokens: 6 (short response), topP: 1. (API Key auth — requires OpenAI API credentials)

  3. Merge (Data Combination) — Combines the original trigger data (from input 1) with the AI classification result (from input 0) using mergeByPosition mode. This ensures downstream nodes have both the original lead data and the classification. (No auth)

  4. Switch (Routing) — Routes the workflow based on the AI classification. It takes the trimmed text from the merged data and compares it against three rules:

    • Output 0: "Unsubscribe"
    • Output 1: "Interested"
    • Output 2: "Out of Office"
    • Fallback (Output 3): Any other classification ("other") (No auth)
  5. Lemlist - Unsubscribe (Output 0) — If the reply is classified as "Unsubscribe", this node unsubscribes the lead from the Lemlist campaign using the lead's email and campaign ID from the trigger data. (Lemlist API Key auth)

  6. lemlist - Mark as interested (Output 1) — If the reply is "Interested", this HTTP Request node sends a POST request to the Lemlist API to mark the lead as interested in the campaign. The URL uses the lead's email and requires a campaign ID placeholder (YOUR_CAMPAIGN_ID). (Lemlist API Key auth via predefinedCredentialType)

  7. HubSpot - Get contact ID (Output 1) — Also triggered for "Interested" replies, this node looks up the lead in HubSpot by email and creates/updates the contact with first and last name. (OAuth2 auth — requires HubSpot OAuth credentials)

  8. HubSpot - Create Deal (Output 1 continued) — After finding/creating the contact, this node creates a new deal in HubSpot associated with that contact. The deal name includes the contact's email, and it's placed in a specific deal stage (ID: 79009480). (OAuth2 auth)

  9. Slack (Output 1 notification) — Sends a notification to a Slack channel (configured as "Your channel name") with a message that a new lead is interested, including a link to the deal in HubSpot. (OAuth2 auth — requires Slack OAuth credentials)

  10. HubSpot - Get contact ID1 (Output 2) — For "Out of Office" replies, this node looks up the lead in HubSpot by email, similar to step 7. (OAuth2 auth)

  11. follow up task (Output 2 continued) — Creates a follow-up task in HubSpot associated with the contact. The task subject includes the lead's first and last name with "OOO - Follow up" prefix, reminding the sales team to follow up after the lead returns. (OAuth2 auth)

  12. Slack1 (Output 3 - Fallback) — For any other classification ("other"), this node sends a Slack notification with a link to the Lemlist campaign report, alerting the team to review the reply manually. (OAuth2 auth)

Setup Instructions

To use this workflow, you'll need accounts and credentials for the following services:

  • Lemlist: You need a Lemlist account with an active campaign. Create a Lemlist API key from your Lemlist settings (API section). You'll also need to replace YOUR_CAMPAIGN_ID in the "lemlist - Mark as interested" node with your actual campaign ID.
  • OpenAI: Sign up for OpenAI and generate an API key from the OpenAI dashboard. This workflow uses the GPT-3.5/4 model for classification.
  • HubSpot: You need a HubSpot account with OAuth app credentials. Create a private app in HubSpot Developer settings to get Client ID and Client Secret, then configure OAuth2 in n8n.
  • Slack: Create a Slack app with OAuth permissions to post messages. Add the chat:write scope and install the app to your workspace. Use the OAuth token in n8n.

After setting up credentials in n8n:

  1. Import this workflow
  2. Configure the Lemlist webhook trigger by copying the webhook URL from n8n and adding it to your Lemlist account under Integrations > Webhooks
  3. Replace YOUR_CAMPAIGN_ID in the HTTP Request node with your actual Lemlist campaign ID
  4. Update the Slack channel names in both Slack nodes
  5. Test with a sample email reply

Use Cases and Variations

Primary Use Case: Sales teams running cold email campaigns can automatically triage replies without manual intervention. Interested leads get fast-tracked into HubSpot deals and Slack notifications, unsubscribes are handled automatically, and OOO replies trigger follow-up tasks.

Variations:

  • Different CRM: Replace HubSpot nodes with Salesforce, Pipedrive, or any other CRM supported by n8n
  • Custom Categories: Modify the OpenAI prompt to classify replies into different categories (e.g., "pricing question", "demo request", "not interested")
  • Multi-channel Notifications: Add email notifications via Gmail/SMTP or SMS via Twilio for critical replies
  • Lead Scoring: After classification, add a node to update lead scores in your CRM based on reply sentiment
  • A/B Testing: Route different campaign replies to different Slack channels or teams based on campaign ID
  • Analytics: Add a Google Sheets node to log all classifications and actions for reporting
12 nodesmanual triggerSales
LemlistHubspotSwitchMergeHTTP RequestSlackOpen AI

Workflow JSON

{
  "meta": {
    "instanceId": "f0a68da631efd4ed052a324b63ff90f7a844426af0398a68338f44245d1dd9e5"
  },
  "nodes": [
    {
      "id": "44b2e0ac-1ec9-4acd-bf00-7e280378b8df",
      "name": "Lemlist - Unsubscribe",
      "type": "n8n-nodes-base.lemlist",
      "position": [
        1300,
        -180
      ],
      "parameters": {
        "email": "={{ $json[\"leadEmail\"] }}",
        "resource": "lead",
        "operation": "unsubscribe",
        "campaignId": "={{$json[\"campaignId\"]}}"
      },
      "credentials": {
        "lemlistApi": {
          "id": "45",
          "name": "Lemlist - \"lemlist\" team API key"
        }
      },
      "typeVersion": 1
    },
    {
      "id": "75dd6db8-5e59-4521-a4be-2272e2914494",
      "name": "follow up task",
      "type": "n8n-nodes-base.hubspot",
      "position": [
        1520,
        640
      ],
      "parameters": {
        "type": "task",
        "metadata": {
          "subject": "=OOO - Follow up with {{ $json[\"properties\"][\"firstname\"][\"value\"] }} {{ $json[\"properties\"][\"lastname\"][\"value\"] }}"
        },
        "resource": "engagement",
        "authentication": "oAuth2",
        "additionalFields": {
          "associations": {
            "contactIds": "={{ $json[\"vid\"] }}"
          }
        }
      },
      "credentials": {
        "hubspotOAuth2Api": {
// ... truncated (copy to see full JSON)

How to Import This Workflow

  1. 1Copy the workflow JSON above using the Copy Workflow JSON button.
  2. 2Open your n8n instance and go to Workflows.
  3. 3Click Import from JSON and paste the copied workflow.

Don't have an n8n instance? Start your free trial at n8nautomation.cloud

Related Templates

AI-Powered Competitor Price RAG Pipeline with Logging

Overview This workflow implements a Retrieval-Augmented Generation (RAG) pipeline for processing and analyzing competitor pricing data. It is triggered via a webhook (e.g., by an external scraper), splits incoming text into chunks, generates embeddings using OpenAI, stores them in a Supabase vector store, and then allows an Anthropic-powered AI agent to query that context. Results are appended to a Google Sheet for record-keeping, and any errors trigger a Slack alert to a designated channel. This setup is ideal for teams that need to automate the ingestion of structured or unstructured competitor data, enable natural language queries against that data, and maintain an audit log—all without manual intervention. Node-by-Node Breakdown Sticky Note — A visual note in the editor (not executed). Webhook Trigger (No auth) — Listens for incoming POST requests at the path . This is the entry point; an external service (e.g., a custom scraper) should send data here. Text Splitter (No auth) — Splits the incoming text into chunks of 400 characters with 40 character overlap. This ensures the embeddings are meaningful and context windows are manageable. Embeddings (API Key auth — OpenAI) — Uses the model to convert each text chunk into a vector embedding. Requires an OpenAI API key. Supabase Insert (API Key auth — Supabase) — Inserts the generated embeddings into the Supabase vector store under the index . This stores the data for future retrieval. Supabase Query (API Key auth — Supabase) — Queries the same Supabase vector index to retrieve relevant chunks based on a question or input from the agent. Vector Tool (No auth) — Wraps the Supabase query as a tool that the AI agent can call to fetch contextual data. Window Memory (No auth) — Provides conversational memory (buffer window) so the agent can maintain context across multiple interactions. Chat Model (API Key auth — Anthropic) — The language model that powers the AI agent. Uses Anthropic’s Claude model (selected via credentials). Requires an Anthropic API key. RAG Agent (No auth) — The core AI agent that receives the incoming data, uses the vector tool to retrieve relevant context, and generates a response using the chat model. The system message is set to "You are an assistant for Competitor Price Scraper". Append Sheet (OAuth2 — Google Sheets) — Appends the agent’s response (from the node) to a Google Sheet named . You must specify the Google Sheet ID and sheet name in the node parameters. Slack Alert (OAuth2 — Slack) — Triggered only on error from the RAG Agent. Sends a message to the channel with the error details. Setup Instructions Accounts & Credentials – You will need: - An OpenAI account (for embeddings). Create an API key and add it in n8n as an OpenAI credential. - An Anthropic account (for the chat model). Create an API key and add it as an Anthropic credential. - A Supabase project. Enable the pgvector extension, create a table for embeddings, and get the Supabase URL + anon/public API key. Add these as a Supabase credential in n8n. - A Google Cloud project with the Sheets API enabled. Generate OAuth2 credentials (or use a service account) and add them as a Google Sheets OAuth2 credential in n8n. - A Slack workspace. Create a Slack app with chat:write permission and install it to your workspace. Add the bot token as a Slack OAuth2 credential in n8n. Configure the Webhook – The webhook path is . You can change this as needed. Expose this endpoint (e.g., via n8n’s public URL or a tunnel) so your scraper can POST data to it. Set the Google Sheet ID and sheet name – In the Append Sheet node, replace with the actual ID of your Google Sheet and ensure the sheet is named (or update the parameter). Adjust Slack Channel – In the Slack Alert node, set the channel name (default ) to one that exists in your Slack workspace. Test the workflow – Send a sample POST request with some competitor price text to the webhook URL. Check the Google Sheet for logged responses and test error handling by sending malformed data. Use Cases & Variations Competitive Intelligence – Automate the ingestion of price lists, product descriptions, or news articles from competitors. Use the AI agent to answer questions like “Which competitor has the lowest price on product X?”. Document Q&A – Adapt this pipeline for any document type (PDFs, support tickets, internal memos). Replace the webhook with a file trigger and use the same RAG flow. Multi-Source Ingestion – Add an HTTP Request node before the Text Splitter to fetch data from an API or RSS feed instead of relying on a webhook. Custom Output – Instead of a Google Sheet, send the agent’s response via email, SMS, or directly into a CRM. Scheduled Runs – Swap the Webhook Trigger for a Schedule Trigger to run the ingestion on a regular basis (e.g., daily).

12 nodes

Extract Google Maps Business Leads via Dumpling AI to Google Sheets

Overview This workflow automates the extraction of business listings from Google Maps using Dumpling AI's search-maps API and logs the results into a structured Google Sheet. It's ideal for lead generation, market research, or competitive analysis — allowing you to quickly gather data like business names, ratings, addresses, phone numbers, websites, and booking links without manual browsing. Workflow Steps Trigger: Manual Test Run (Manual Trigger) — Starts the workflow on demand for testing. No authentication required. Search Google Maps via Dumpling AI (HTTP Request) — Sends a POST request to with a JSON body containing the search query (e.g., ) and language. Authentication uses Header Auth — you must provide a Dumpling AI API key as a header (configured in n8n credentials). The response returns an array of places with details like title, rating, address, phone, website, price level, and booking links. Split Places List for Processing (Split Out) — Splits the array from the HTTP response into individual items so each place can be processed separately. No authentication needed. Save Results to Google Sheet (Place Info) (Google Sheets) — Appends each place's data (name, address, rating, price level, type, website, phone, position, booking link) to a specified sheet in a Google Sheets document. Uses OAuth2 authentication (Google account). The sheet name is set to "Google Maps" and the document ID points to a spreadsheet named "Places". Setup Instructions Dumpling AI Account: Sign up at dumplingai.com and obtain an API key. In n8n, create a new Header Auth credential with the key name (e.g., ) and value . Google Sheets: Create a Google Sheet (or use the one referenced in the workflow). In n8n, create a Google Sheets OAuth2 credential by connecting your Google account. Ensure the sheet has a tab named "Google Maps" (or update the sheet name in the node). Customize Query: Edit the of the HTTP Request node to change the search query (e.g., ) or language. Run: Click "Execute Workflow" to test. The first run will prompt you to authorize Google Sheets access. Use Cases & Variations Lead Generation: Replace the query with industry-specific terms (e.g., "dentists in Los Angeles") to build a targeted prospect list. Competitor Analysis: Search for competitors in a niche and analyze their ratings, price levels, and online presence. Real Estate / Local Business Research: Extract data for multiple locations by chaining queries or using a loop. Automation: Replace the Manual Trigger with a Schedule Trigger to run daily/weekly, and add a Set node to dynamically pass queries from a spreadsheet or webhook. Enrichment: Add nodes to clean data, send notifications (Slack/Email), or integrate with a CRM like HubSpot.

5 nodes

Auto-Qualify Google Sheets Leads with OpenAI GPT-4

Overview This workflow automatically qualifies new leads submitted via Google Forms (or directly entered) into a Google Sheet. Using OpenAI's GPT-4, it evaluates each lead against custom criteria (e.g., decision-maker role, team size, email domain) and updates the sheet with a qualification rating and explanation. This saves manual review time and ensures consistent lead scoring for sales teams or community managers. Node-by-Node Breakdown Check for new entries (Google Sheets Trigger – OAuth2) - Listens for new rows added to a specific Google Sheet (connected to a Google Form or standalone). - Configured to poll every minute (adjustable). - Requires: A Google Sheet document ID and sheet name. Qualify leads with GPT (OpenAI – API Key auth) - Uses the chat model. - A system message defines qualification rules (decision-maker, team size, corporate email). - A user message injects the lead's name, email, business area, and team size from the trigger output. - Temperature set to 0.3 for consistent, deterministic responses. - Instructed to reply with a JSON object: . Extract JSON reply (Set Node – no auth) - Parses the from OpenAI's response using . - Stores the resulting object in a new field for downstream nodes. Merge (Merge Node – no auth) - Combines the original lead data (from the trigger) with the parsed GPT reply. - Uses “Combine” mode with “Merge by position” to join the two inputs horizontally. - Input 0 (from trigger) holds the row data; Input 1 (from Extract JSON reply) holds the GPT rating. Update lead status (Google Sheets – OAuth2) - Updates the same Google Sheet with the GPT's rating and explanation. - Matches rows by the column (to avoid updating the wrong row). - Writes the rating into a column (and optionally the explanation if you extend the schema). Setup Instructions Google Cloud / Sheets API - Create a Google Cloud project, enable the Google Sheets API, and create OAuth2 credentials (Desktop app or Web application). - In n8n, add a new Google Sheets credential (OAuth2) using your client ID and secret. OpenAI API Key - Sign up at OpenAI and create an API key. - In n8n, add a new OpenAI credential with your API key. Google Sheet - Use the provided template or create your own with columns: Timestamp, Email Address, Your name, Your business area, Your team size, Rating. - If using Google Forms, submissions will automatically populate the sheet. Configure the workflow - After importing, select each Google Sheets node and choose your credential and the correct sheet/document. - Adjust the polling interval if needed (default: every minute). - Modify the GPT system message to fit your own lead qualification criteria. Use Cases & Adaptations Sales lead scoring: Replace the criteria with your ICP (ideal customer profile) – e.g., industry, company size, budget. Community membership approval: Automatically accept or reject join requests based on responses. Event registration filtering: Qualify attendees for VIP access or follow-up. Extend output: Store the explanation in a separate column by adding it to the Update node's column mapping. Add notifications: Insert a Slack or email node after the Merge to alert your team when a high-quality lead is detected. Use a different model: Switch to for lower cost or for faster responses. This template is a starting point – tweak the prompt, polling frequency, and output columns to match your exact process.

9 nodes

Ready to automate with n8n?

Get affordable managed n8n hosting with 24/7 support.