Text sales reps the moment a high-priority HubSpot deal lands
When a new deal hits HubSpot, an agent decides if it clears the priority bar, then texts the rep and posts a summary to your Slack deal-flow channel.
Integrations
HubSpot
Twilio
Slack Bot
Type
Categories
- Sales
- Operations
Build me an agent that texts my sales reps the moment a high-priority deal lands in HubSpot, and also posts a team summary into a Slack deal-flow channel for every new deal (priority or not).
Trigger: a HubSpot poll trigger on new deals created (deals_created).
For each new deal the agent should:
1. Call HubSpot Get Deal to read the deal name, amount, stage, deal source / hs_analytics_source, close date, and the associated primary contact and company.
2. Call HubSpot Get Contact on the associated contact to pull the contact's full name and phone number.
3. Call HubSpot Get Owner on the deal's hubspot_owner_id to pull the assigned rep's name, email, and mobile phone.
4. Decide whether the deal is high priority. Default rule: deal amount is at least $10,000, OR deal source is one of an inbound demo request, partner referral, or any source the user marks high-intent. Make the threshold and the high-intent source list configurable inputs on the workflow.
5. If the deal is high priority AND the assigned rep has a mobile number on their HubSpot user record: send an SMS via Twilio Send a Message to the rep's mobile. The SMS should be one or two sentences, name the company and dollar amount, and include one piece of context the rep should know before calling back (for example the lead source, the contact's title, or the stage). Keep it under 320 characters. Use E.164 format for the To number.
6. If the deal is high priority but no rep mobile number is on file: skip the SMS and add a clear note in the Slack summary that the rep number was missing.
7. Always post a richer summary to a configurable Slack channel via Slack Bot Send a Message. The summary should include: company name, deal amount, stage, deal source, the assigned rep (tagged or named), the contact's name and title if available, and a one-line take on why the deal looks promising. For low-priority deals, post a shorter line so the channel still has full visibility but it stays scannable.
Inputs the workflow should expose: the Twilio sending phone number, the priority dollar threshold (default $10,000), the list of high-intent deal sources, the Slack channel to post the team summary to, and an optional quiet-hours window where SMS is suppressed (still post to Slack).
Constraints: never text the contact, only the rep. Never send more than one SMS per deal. If the same deal fires twice for any reason, dedupe on the HubSpot deal id.
What it does
- Watches HubSpot for newly created deals and reads the amount, stage, source, contact, and assigned rep.
- Decides whether the deal clears a priority bar you set, like a minimum dollar amount or a high-intent lead source.
- Texts the assigned rep a tight one or two sentence SMS naming the company, the deal size, and one piece of context to know before calling back.
- Posts a richer summary into a shared Slack deal-flow channel so the whole team has visibility, with low-priority deals logged quietly and without a text.
What you’ll need
- A HubSpot account where new deals are created with an assigned owner.
- A Twilio account with a phone number that can send SMS in your reps' countries.
- Mobile numbers for your reps stored on their HubSpot user record.
- A Slack workspace with a deal-flow channel for the team summary.
How to customize it
- Set the priority bar that triggers an SMS, for example a minimum deal size in dollars or a list of lead sources like inbound demo or partner referral.
- Change the SMS wording, what context line gets included, and how the rep is addressed.
- Pick which Slack channel the team summary goes to and whether low-priority deals still get logged there.
Use cases
- Notifications & Alerts
- Lead Enrichment
