← All templates

Web Design

Website Form to CRM & Studio

A web studio’s own enquiry form is usually the least automated thing they own. This workflow takes the Webflow submission, creates or updates the CRM contact and deal so nothing is retyped, opens a Notion project stub carrying the answers a first call needs, alerts the studio channel, and sends an acknowledgement that qualifies gently by stating the minimum engagement.

6 stepsRequires Zapier Starter or higher20 minEasy
WebflowHubSpotNotionDiscord

What you get

Enquiries land in the CRM as real deals, not as an inbox to be retyped.
A project stub exists before the first call, carrying what the client already told you.
Budget expectations are set in the acknowledgement, before anyone spends an hour on a call.

Workflow blueprint

WE
When this happens
WebflowForm Submission
1HU
HubSpotCreate or Update Contact
2HU
HubSpotCreate Deal
3NO
NotionCreate Database Item
4DI
DiscordSend Channel Message
5HU
HubSpotSend Email

The full blueprint — every field mapping, example value and the written copy for each message — is included with purchase.

Getting it into Zapier

Build this one from the recipe. The blueprint gives you the exact trigger, action events and field mapping for all 6 steps, so it is a copy-and-paste job rather than a design job.

You need your own Zapier account. Zapier’s Free plan runs single-step Zaps only; multi-step Zaps need a paid plan, and Paths and Webhooks need Professional. How this works →

Not on Zapier?

n8n — import and go

An n8n workflow JSON ships with this template. Import it and all 6 steps arrive on the canvas wired in order, and 1 of the 6 nodes arrive with their fields already filled in — the subject lines, the message copy, the delays, the column names. Every step maps to a native n8n node.

What an import cannot carry is your credentials, and the IDs that only exist inside your own account — which spreadsheet, which channel, which board. Those stay in a sticky note under the node, listing what is already done so you do not retype it, and what is left so you can see it.

Make — build guide

A Make-specific guide ships with this template: every module in order, every field value, and the concept translations that catch people out — filters live on the links between modules, and the schedule lives on the scenario rather than in a trigger module.

Self-hosted n8n has no per-task fee, which is worth knowing if this workflow runs at volume. Platform coverage →

Setup steps

1
Capture the Webflow submission

Configure this step using the field mapping in the blueprint.

2
Create or update the CRM contact

Configure this step using the field mapping in the blueprint.

3
Open the deal

Configure this step using the field mapping in the blueprint.

4
Create the project stub

Configure this step using the field mapping in the blueprint.

5
Alert the studio

Configure this step using the field mapping in the blueprint.

6
Acknowledge and set expectations

Configure this step using the field mapping in the blueprint.

Implementation notes

  • State the minimum engagement in the acknowledgement. It costs a few unqualified enquiries and saves a great many unqualified calls, which is the better trade by a distance.
  • Create-or-update the contact, never create. Returning enquirers are common and a split history is worse than no history.
  • The pre-call checklist in the Notion stub is the difference between a first call that wins work and one that gathers requirements. Do the site review before, always.
  • Squarespace, WordPress, Framer and plain HTML forms all substitute for Webflow; Pipedrive, Close and Attio all substitute for HubSpot.