Typeform Lead Router Agent

A form response is only worth collecting if it reaches the person who should call. This agent reads every Typeform submission, routes it by rules you write in plain English, and files the contact in HubSpot with the answers quoted in the lead's own words. Slack hears about the ones that got routed, with the owner named first, so nobody has to sit watching the form.

What people use it for

• Route by product or region - Teams selling more than one thing lose leads at the handoff. The agent reads the answers, picks the owner your rules name, and puts that name at the front of the Slack message so the pickup is never ambiguous.
• Every response reaches the CRM - Contacts are matched or created in HubSpot with the answers attached as a note, on the day the form was filled in. Nobody has to paste a form export into the CRM on Friday afternoon.
• Reps open with their words - The note keeps what the lead actually typed rather than a summary of it. That is the difference between a first call that starts cold and one that starts halfway in.
• Junk stops at the CRM - Test entries and throwaway addresses are logged and marked, never pinged. The Slack channel stays a list of people worth calling instead of a feed of form noise.

Before you fork

What do I need to connect before it runs?

The Typeform whose responses you want routed, a HubSpot credential that can search contacts, create contacts, and write notes, and the Slack channel that should receive the pings. Then you write two things in your own words: your routing rules with an owner for each route, and what your reps want to see in a summary. The test runs let you watch a full route happen before a real response ever arrives.

Can it email the lead or change my HubSpot records?

No to both. It has no send tool of any kind, so a submitter never hears from it. In HubSpot it searches by email address first and only creates a contact when there is no match, and it writes notes rather than editing properties, deals, or lifecycle stages, so your pipeline reporting is untouched.

What does it cost to run?

One short run per form response, so the cost follows your form volume rather than a seat count. Junk submissions finish faster because they stop at the HubSpot note and never reach Slack. Nothing runs while the form is quiet.