lemlist <> GPT-3: Supercharge your sales workflows
Needs changesNeeds changes. This template uses 1 thing(s) that n8n 3.0 removes: OpenAI (legacy). 1 breaking item(s) found. Static check, last run 2026-10-19.
What this workflow does
This workflow has 12 nodes and runs on Lemlist events (emails replied). Along the way it connects Lemlist, HubSpot and Slack.
How it runs
Trigger: On Lemlist events (emails replied).
- OpenAI: uses OpenAI
- Merge: merges the data from its input branches
- Switch: routes items into 3 branches
- Lemlist: unsubscribe (lead)
- lemlist - Mark as interested (HTTP Request): calls an HTTP API
- HubSpot: work with contact
- HubSpot: work with contact
- Slack: uses Slack
- HubSpot: uses HubSpot
- follow up task (HubSpot): work with engagement
…plus 1 more step. See the full node list below.
Services it uses
Before you upgrade to n8n 3.0
1 thing in this workflow is removed in n8n 3.0. Fix it before you upgrade:
- OpenAI (legacy) in OpenAI: replace with OpenAI node (AI section).
| Removed in 3.0 | Replace with |
|---|---|
| OpenAI (legacy) OpenAI | OpenAI node (AI section) |
Nodes used (8)
- Lemlist
n8n-nodes-base.lemlist - HubSpot
n8n-nodes-base.hubspot - Switch
n8n-nodes-base.switch - Merge
n8n-nodes-base.merge - HTTP Request
n8n-nodes-base.httpRequest - Slack
n8n-nodes-base.slack - Lemlist Trigger
n8n-nodes-base.lemlistTrigger - OpenAI
n8n-nodes-base.openAi
From the author
Use GPT-3 to classify email responses in lemlist. And automate: - Slack alerts when a lead is interested - the creation of tasks when a lead is OOO - unsubscription of leads when they request it