Inbound Lead Routing
New leads get scored the moment they arrive and the hot ones land in #sales while your reps are still at their desks. A ModuleX agent rates buying intent, posts the strong leads to Slack, and files every contact in HubSpot.
HubSpot
Slack
5 steps2 integrationsRuns on every new lead
Strong leads cool off in the pile. What qualifying by hand looks like, and why the Friday lead waits until Monday.
- 01Inbound leads arrive at all hours, and most are noise: students, competitors, tire-kickers.
- 02A rep reads every one to find the few worth a call, while the strong leads cool off.
- 03The good lead that lands at 6pm on Friday is not seen until Monday.
- New leadVP Ops · 240 seats
- Score intent84 · above threshold
- Post to Slack#sales · with the reason
- Update CRMcreate_contact · updated
One workflow, five steps. ModuleX drafts this graph from a single sentence, and every step stays editable.
- 01Catch the new lead as it arrivesModuleX
- 02Score buying intent against your thresholdModuleX
- 03Post hot leads to #sales with the reasonSlack
- 04Search HubSpot for an existing contactHubSpot
- 05Create or update the record with the scoreHubSpot
The workflow is an editable graph. Scoring is read-only and runs freely; the #sales post and the HubSpot write wait for your opt-in approval until you loosen them. The graph is the receipt.
Hot leads, routed. Paste this into ModuleX chat, or hit Use this workflow. It drafts the graph, connects your accounts, and schedules it.
When a new lead comes in, score it from 0 to 100 for buying intent, post any lead above 70 to #sales in Slack with the reason, and create or update the contact in HubSpot with the score. Ask me before posting anywhere else.
to: composerOr skip the workflow entirely. Ask the assistant in chat and it runs the same job agentically: it picks the right actions, chains them, and reports back. The composer is for when you want it repeatable.
Score this new lead for buying intent from 0 to 100. If it is above 70, post it to #sales in Slack with the reason, and create or update the contact in HubSpot with the score.
- hubspot · search_contacts · by email
- slack · post_message · #sales
- hubspot · create_contact · score 84
Scored 84: VP Ops at a 240-seat company, asking about SSO and pricing. Posted to #sales with the reasoning and created the HubSpot contact with the score attached.
Where this fits. The tools it runs on, and the teams that run it.
Keep the momentum. Nearby workflows that reuse the accounts you just connected.
Enrich a new lead before anyone calls itA lead record with the basics already filled in, and a note of where each field came from. Built for a sales team where half the inbound records arrive as a name and an email.
Draft a follow-up that knows where the deal standsA short, context-aware reply waiting in your drafts, with the ask made explicit. Built for an account executive with a dozen replies to write between calls, and no time to re-read every thread.
Import a contact list into your CRM without the cleanupContacts in the CRM with the fields mapped, and a list of the rows that needed a human decision. Built for whoever inherits the spreadsheet after a conference.
About this use case.
A model scores each lead and the agent compares it to a threshold you set in the prompt. You can change both the scoring instructions and the cutoff at any time, so the definition of a strong lead stays yours.