Inbound forms land in one inbox and someone has to read each one and decide where it goes. That delay loses warm leads. This router reads every submission and sorts it into the right lane before a human sees it.
sonnet3 daysWebhookOpenAIHubSpotSlack
Claude
87ROI
83Scale
$3k91Saved
ROI for
README.md
Why this subagent
Inbound forms land in one inbox and someone has to read each one and decide where it goes. That delay loses warm leads. This router reads every submission and sorts it into the right lane before a human sees it.
It normalizes fields across your forms, classifies intent, checks the CRM for an existing contact, then files the lead in the correct pipeline and pings the owning team. You get every form routed in seconds with a confidence score on each call.
How it runs
Used at step 01 to kick off the pipeline.
Write
Used at step 01 to kick off the pipeline.
WebFetch
Used at step 01 to kick off the pipeline.
WebSearch
Used at step 01 to kick off the pipeline.
Read the message body and metadata, then classify it into a lane such as sales, support, or partnership.
pending
Look up whether the email already exists in the CRM and pick create-or-update accordingly.
pending
Write the lead into the matching CRM pipeline and notify the owning team in Slack.
pending
Sample output
json
// Sample output
// (generated when the pipeline finishes)
Given a normalized form submission, classify it into one CRM lane and return a JSON object with lane, confidence, matched contact id, and the routing action taken.
Unlock the rest
The full agent definition, install snippet, and starter task are gated for community members.
Members get the full `.md` agent file, the npm / pnpm install one-liners, a starter prompt that we've tuned against real runs, and the open-source repo when this automation ships there. One email, magic link, done.