Webflow Form Lead Agent with Claude Code
The work here is two lookups before a single judgement: the form definition, which is what turns field-3 back into the budget question, and HubSpot, which decides whether anybody gets created. Claude Code gathers the surrounding context before writing anything, and that is the right order for a template where the meaning of the answers arrives after the answers do.
Watch it work before it's live
Run a staged conversation — no account needed. The agent handles it for real while a simulated world answers its tool calls; nothing touches real accounts, and nothing is actually sent.
New response
Contact Sales
Email: ines.marchetti@caravella-hotels.it. Company: Caravella Hotels. How can we help: we open four properties in Sicily next spring and need one booking site running all of them in Italian, English and German. Budget: 25,000 to 40,000 EUR. When do you need this live: first property by March, all four by June. Where did you find us: saw the Palermo project on your work page.
Ines Marchetti · studioverde.com/pricing
Set up in minutes
Using this template drops you into a guided setup. It asks exactly this, nothing else:
Connect Webflow
One sign-in. The agent acts through your account, scoped to what this template uses.
Connect HubSpot
One sign-in. The agent acts through your account, scoped to what this template uses.
Connect Slack
One sign-in. The agent acts through your account, scoped to what this template uses.
Routing criteria
Which submissions count as leads and who owns each kind, written against the questions your forms actually ask, plus what marks a submission as junk. Anything outside it is unknown to the agent.
Runs on Claude Code
Preselected for this page — connect your Claude Code account during setup, or switch to NoClick's built-in models with one click.
Watch it handle a test run
A staged conversation against a simulated world — then it’s live.
Why Claude Code for this agent
Labels before answers
A submission read without its form is a list of ids with strings attached. Fetching the definition first is what makes routing possible at all.
Three outcomes on the lookup
One match, no match, or several. The third means attach nothing and name the records that collided, which is the outcome most integrations quietly get wrong.
Before you fork
Can it reply to somebody who filled in the form?
There is no send operation in the workflow, so no. It writes to HubSpot and posts to Slack, and a reply always leaves from a person's own mailbox. That is deliberate on a public form, since anything that answers automatically confirms to every spammer that the address is live and monitored.
Run it with a different agent
Put Webflow Form Lead Agent to work on Claude Code
Free to start. Guided setup, a test run against staged conversations, and it's live.