What happens when you stop doing it manually.

Challenge

Four website forms (audit, contact, checklist, discovery) were sending email notifications through EmailJS. No CRM. No structured contact records. Every lead had to be copied into a spreadsheet by hand.

Solution

We added n8n webhook calls to all 4 forms, running alongside the existing EmailJS sends. The n8n workflow splits the full name, tags which form the lead came from, creates or updates a HubSpot contact with company, phone, and industry fields, then fires a Slack message to #leads in seconds.

Challenge

The site already had an AI chatbot answering questions about our services. But every visitor who chatted was anonymous. No contact info, no way to follow up. Helpful conversations that went nowhere.

Solution

We updated the chatbot's system prompt so it asks for name, email, and pain point during conversation, without forms or pop-ups. When the bot has all three, it appends a hidden marker to its response. The client-side JS strips the marker and fires the same n8n webhook our forms use. HubSpot contact created, Slack alert sent, seconds later.

Challenge

Wanted a chatbot on a static HTML/CSS/JS site. No React, no Node server. Most chatbot vendors charge $50-200/month and look generic.

Solution

A Netlify Edge Function (Deno) proxies the Anthropic streaming API. Client-side JS handles SSE streaming, session persistence, rate limiting by IP and daily cap, input sanitization, and prompt injection guardrails. About 300 lines total.

Challenge

The site started with EmailJS notifications and a spreadsheet. No CRM, no alerting, no source tracking. Every follow-up was manual.

Solution

One n8n webhook that all 5 sources feed into: audit form, contact form, checklist form, discovery questionnaire, and AI chat. It normalizes fields, tags the source, creates or updates a HubSpot contact, and fires a Slack alert. Same pipeline regardless of entry point.