Draft AI-powered Help Scout replies with HubSpot and SMS customer 360 context
Needs changesWhat this workflow does
This workflow has 15 nodes and runs when an HTTP POST request hits its webhook URL. It uses only n8n's built-in nodes. It also calls api.hubapi.com over HTTP.
How it runs
Trigger: When an HTTP POST request hits its webhook URL.
- Parse Event (Code): runs custom JavaScript code
- Extract Data (Code): runs custom JavaScript code
- Fetch HubSpot Context (HTTP Request): calls api.hubapi.com (POST)
- Fetch SMS History (HTTP Request): calls an HTTP API
- Merge: merges the data from its input branches
- Build Shared Context Layer (Code): runs custom JavaScript code
- AI Draft Generator (OpenAI): uses OpenAI
- AI QA & Sentiment Check (OpenAI): uses OpenAI
- Parse QA Output (Code): runs custom JavaScript code
- Sentiment Router (Switch): routes items into 2 branches
…plus 4 more steps. See the full node list below.
HTTP calls to: api.hubapi.com
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 AI Draft Generator, AI QA & Sentiment Check: replace with OpenAI node (AI section).
| Removed in 3.0 | Replace with |
|---|---|
| OpenAI (legacy) AI Draft Generator, AI QA & Sentiment Check | OpenAI node (AI section) |
Nodes used (8)
- Webhook
n8n-nodes-base.webhook - Code
n8n-nodes-base.code - HTTP Request
n8n-nodes-base.httpRequest - Merge
n8n-nodes-base.merge - OpenAI
n8n-nodes-base.openAi - Switch
n8n-nodes-base.switch - If
n8n-nodes-base.if - Respond to Webhook
n8n-nodes-base.respondToWebhook
From the author
Description Categories Customer Support Automation, AI Agents, CRM Integration, SaaS Operations --- Build an AI-Driven Cross-Platform Support Context Engine with n8n This workflow creates an AI-powered middleware layer that unifies customer context across…