Enrich event registrations with HubSpot, Clearbit, LinkedIn and Gemini AI
Ready for 3.0What this workflow does
This AI workflow has 38 nodes and runs when an HTTP POST request hits its webhook URL (plus 2 other triggers). Along the way it connects HubSpot, Slack and Google Gemini Chat Model. It also calls milobravo1.app.n8n.cloud and serpapi.com over HTTP.
How it runs
Trigger: When an HTTP POST request hits its webhook URL (plus 2 other triggers).
- Parse Promo Code (Code): runs custom JavaScript code
- Validate Registration Data (Code): runs custom JavaScript code
- Log Beacon to Data Table (Data table): uses Data table
- Lookup Promo Code (HTTP Request): calls milobravo1.app.n8n.cloud
- Check Validation Result (If): checks a condition and branches into true / false
- Respond OK to Beacon (Respond to Webhook): sends the response back to the webhook caller
- Validate Promo Code (Code): runs custom JavaScript code
- Create or Update HubSpot Contact (HubSpot): uses HubSpot
- Respond Validation Error (Respond to Webhook): sends the response back to the webhook caller
- Log Promo Code to Data Table (Data table): uses Data table
…plus 24 more steps. See the full node list below.
Services it uses
HTTP calls to: milobravo1.app.n8n.cloud, serpapi.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 (11)
- Webhook
n8n-nodes-base.webhook - Data table
n8n-nodes-base.dataTable - Respond to Webhook
n8n-nodes-base.respondToWebhook - Code
n8n-nodes-base.code - If
n8n-nodes-base.if - HubSpot
n8n-nodes-base.hubspot - Send Email
n8n-nodes-base.emailSend - Slack
n8n-nodes-base.slack - HTTP Request
n8n-nodes-base.httpRequest - Information Extractor
@n8n/n8n-nodes-langchain.informationExtractor - Google Gemini Chat Model
@n8n/n8n-nodes-langchain.lmChatGoogleGemini
From the author
Event Registration + Auto-Enrichment Intelligence Who is this for? Event organizers, conference planners, and marketing teams fighting registration drop-off who want 4-field forms with LinkedIn-level attendee intelligence. What problem is this workflow…