Webflow Form Lead Agent with Codex
Read a submission, read its form, search a CRM, create or annotate a contact, post a message. Each of those is an API call with a clear success condition, and Codex is strong at API and data manipulation, which covers most of this template between the two moments that need judgement.
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 Codex
Preselected for this page — connect your Codex 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 Codex for this agent
Search then write, in order
The HubSpot lookup has to happen before anything is created. Sequencing calls correctly is where a harness comfortable with APIs saves you from a duplicate record.
Under 150 words, every time
The note has a length limit and a fixed order: question, answer, page, time, route, reason. Bounded output on a repeating task is an easy target for this harness.
Before you fork
How do we know the routing matches what we wrote?
Run the three staged submissions before connecting anything live. Hotel Group Rebuild should route with an owner named, Blog Reader Question should not route at all, and Backlink Pitch should reach HubSpot marked as spam and never touch Slack. If all three behave, your criteria are doing what you believe they are.
Run it with a different agent
Put Webflow Form Lead Agent to work on Codex
Free to start. Guided setup, a test run against staged conversations, and it's live.