Webflow to Google Sheets, leads logged and shared
Your Webflow form is doing its job. The problem is what happens after. Leads land in an inbox, get buried under “quick questions,” and somehow the hottest submissions are always the ones you notice two days later.
This is where Webflow lead logging turns into real leverage. Marketing managers get cleaner reporting, sales reps get faster follow-up, and founders stop playing detective in old email threads.
This workflow captures every Webflow submission, writes it to Google Sheets, then pings your team in Twake (and optional channels) so the right person sees it fast. You’ll also learn what to watch for, and how to adapt it to your routing rules.
How This Automation Works
The full n8n workflow, from trigger to final output:
n8n Workflow Template: Webflow to Google Sheets, leads logged and shared
flowchart LR
n0["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/webflow.svg' width='40' height='40' /></div><br/>Webflow Trigger"]
%% Styling
classDef trigger fill:#e8f5e9,stroke:#388e3c,stroke-width:2px
classDef ai fill:#e3f2fd,stroke:#1976d2,stroke-width:2px
classDef aiModel fill:#e8eaf6,stroke:#3f51b5,stroke-width:2px
classDef decision fill:#fff8e1,stroke:#f9a825,stroke-width:2px
classDef database fill:#fce4ec,stroke:#c2185b,stroke-width:2px
classDef api fill:#fff3e0,stroke:#e65100,stroke-width:2px
classDef code fill:#f3e5f5,stroke:#7b1fa2,stroke-width:2px
classDef disabled stroke-dasharray: 5 5,opacity: 0.5
class n0 trigger
classDef customIcon fill:none,stroke:none
class n0 customIcon
The Problem: Webflow Leads Slip Through the Cracks
Webflow forms look simple on the surface: someone fills out a field, you get a notification, done. In practice, it’s chaos. One person replies from their inbox, another copies details into a spreadsheet “later,” and the third tags someone in chat with zero context. Then you try to reconcile what happened for reporting, and you realize you can’t even answer basic questions like “Which campaign brought the most qualified leads?” without digging through multiple tools. It’s annoying. It’s also expensive, because slow follow-up kills deals.
The friction compounds. Here’s where it breaks down most often.
- A single missed Webflow email notification can mean a lead never gets contacted.
- Manual logging into a spreadsheet is inconsistent, so your pipeline data becomes untrustworthy.
- Routing is usually “whoever sees it first,” which is a bad system when you’re busy.
- Follow-ups happen in scattered threads, so nobody has a shared source of truth.
The Solution: Capture, Log, and Alert Automatically
This n8n workflow turns every Webflow form submission into an organized, trackable lead record that your team actually sees. It starts the moment a user submits your Webflow form. n8n grabs the submission details, checks the data (so you can treat “Contact Sales” differently than “Newsletter Signup”), and then writes a clean row into Google Sheets. After the lead is logged, the workflow posts a notification into Twake so someone can respond right away, with the key fields included. If you want more coverage, the same pattern can also notify Mattermost, or kick off downstream actions via HTTP requests.
The workflow begins with a Webflow trigger, then processes each submission through simple logic. Google Sheets becomes your running lead log, and Twake becomes your “eyes on it now” channel so nothing sits quietly in a forgotten inbox.
What You Get: Automation vs. Results
| What This Workflow Automates | Results You’ll Get |
|---|---|
|
|
Example: What This Looks Like
Say your site generates 20 form leads a week. Manually, you might spend about 5 minutes per lead copying fields into a sheet, plus another 2 minutes posting a message in chat so sales sees it. That’s roughly 2 to 3 hours a week of busywork. With this workflow, the “work” is basically instant: the lead is logged automatically and the Twake alert posts right away, so you spend your time only on the follow-up, not the admin.
What You’ll Need
- n8n instance (try n8n Cloud free)
- Self-hosting option if you prefer (Hostinger works well)
- Webflow to trigger on new form submissions.
- Google Sheets to store a shared lead log.
- Twake to notify the right person instantly.
Skill level: Beginner. You’ll connect accounts, map a few form fields, and test one submission end-to-end.
Don’t want to set this up yourself? Talk to an automation expert (free 15-minute consultation).
How It Works
A Webflow form submission triggers the workflow. The moment someone hits submit, n8n pulls in the fields you care about (name, email, message, source page, and anything custom you’ve added).
The lead data gets cleaned and checked. Using simple “If” logic and batching, you can normalize odd inputs, avoid blank rows, and decide what counts as a sales lead versus a low-priority request.
Google Sheets becomes the system of record. n8n writes the submission into a single row so your team can filter, sort, assign ownership, and track status without asking engineering to build a mini-CRM.
Twake (and optional channels) get alerted. The workflow posts a message into Twake with the key details so follow-up starts quickly, and you can also reuse the same payload for Mattermost or an HTTP request to other tools.
You can easily modify the routing rules to send different leads to different Twake channels based on form name, country, or “work email vs. free email.” See the full implementation guide below for customization options.
Common Gotchas
- Google Sheets permissions can block writes. If rows stop appearing, check the connected Google account access and the target spreadsheet sharing settings first.
- If you’re using Wait nodes or external processing, timing can bite you. Bump up the wait duration if downstream nodes fail because they received an empty payload.
- Twake messages can look messy when fields are inconsistent. Default text templates are generic, so add your formatting and brand voice early or you’ll keep rewriting alerts.
Frequently Asked Questions
About 30 minutes if your accounts are already connected.
No. You’ll mainly map form fields to Google Sheets and customize the Twake message.
Yes. n8n has a free self-hosted option and a free trial on n8n Cloud. Cloud plans start at $20/month for higher volume. You’ll also want to account for any paid tool limits (for example, Webflow plan limits or Google account restrictions), but there’s no per-lead fee baked into this workflow.
Two options: n8n Cloud (managed, easiest setup) or self-hosting on a VPS. For self-hosting, Hostinger VPS is affordable and handles n8n well. Self-hosting gives you unlimited executions but requires basic server management.
Yes, and it’s usually the first tweak people make. You can route based on form name (Contact vs. Demo), company size, country, or even email domain by adjusting the “If” logic before the Twake message step. You can also change the destination from one Twake room to multiple rooms by branching the workflow and sending different message templates. If you’d rather store leads somewhere else, you can replace the Google Sheets step with Airtable or a CRM via HTTP Request.
Most of the time it’s an expired token or the wrong site selected in your Webflow credentials. Reconnect Webflow in n8n, then confirm the form is actually on that project and still active. If it fails only during high volume, you may be hitting rate limits; spacing executions with batching helps. Also check that your trigger is pointing to the right form, not a duplicate used for testing.
A lot for small teams. On n8n Cloud, it depends on your monthly execution limit, and each submission typically counts as one execution (more if you branch heavily). If you self-host, there’s no hard execution cap, but your server size and Google Sheets API limits become the practical ceiling.
Sometimes, yes. n8n is better when you want branching logic, multiple destinations (Sheets plus Twake plus something else), or you expect volume and don’t want pricing to spike with every extra step. It’s also nice that self-hosting is an option, which means you can run unlimited executions if your server can handle it. Zapier or Make can be simpler for a basic two-step “Webflow → Sheets” setup, and that’s totally fine. If you’re on the fence, Talk to an automation expert and describe your lead volume and routing rules.
Once this is running, lead capture stops being a fragile process held together by memory and good intentions. The workflow handles the repetitive parts so you can focus on responding, qualifying, and closing.
Need Help Setting This Up?
Our automation experts can build and customize this workflow for your specific needs. Free 15-minute consultation—no commitment required.
