Create and triage support tickets with HubSpot, reCAPTCHA and Gmail
Ready for 3.0Ready for 3.0. This template uses no nodes that n8n 3.0 removes. No removed nodes, versions or helpers found. Static check, last run 2026-10-19.
What this workflow does
This workflow has 20 nodes and runs when an HTTP POST request hits its webhook URL. Along the way it connects HubSpot and Gmail. It also calls google.com and api.hubapi.com over HTTP.
How it runs
Trigger: When an HTTP POST request hits its webhook URL.
- Data Sorting (Edit Fields (Set)): sets 7 fields: email, firstname, lastname…
- Google-captcha (HTTP Request): calls google.com (POST)
- If: checks a condition and branches into true / false
- Create or update a contact (HubSpot): uses HubSpot
- Respond to Webhook: sends the response back to the webhook caller
- Find if Ticket Exit (HTTP Request): calls an HTTP API
- Build Email Payload (New) (Code): runs custom JavaScript code
- Code: runs custom JavaScript code
- Send Email – Customer (Gmail): uses Gmail
- Send Email – CS Team (Gmail): uses Gmail
…plus 9 more steps. See the full node list below.
Services it uses
HTTP calls to: google.com, api.hubapi.com
Before you upgrade to n8n 3.0
Nothing in this workflow is removed in n8n 3.0, so it should import and run after the upgrade.
Nodes used (9)
- HubSpot
n8n-nodes-base.hubspot - Edit Fields (Set)
n8n-nodes-base.set - Code
n8n-nodes-base.code - If
n8n-nodes-base.if - Send Email
n8n-nodes-base.emailSend - HTTP Request
n8n-nodes-base.httpRequest - Webhook
n8n-nodes-base.webhook - Respond to Webhook
n8n-nodes-base.respondToWebhook - Gmail
n8n-nodes-base.gmail
From the author
Quick Overview This webhook-based workflow validates form submissions with Google reCAPTCHA, creates or updates a contact in HubSpot, checks for an existing open ticket, and either creates a new HubSpot ticket or flags it as a duplicate, then emails support…