Slack alerts and HubSpot logs for HeyReach replies

When a prospect replies to a HeyReach campaign, get an instant Slack alert with the intent, the suggested next step, and a fresh note logged on their HubSpot contact.

Agentic Task
HeyReachSlack BotHubSpotSalesNotifications & AlertsLead EnrichmentData Sync

Build an agent workflow that triages new HeyReach campaign replies in real time, alerts our sales team in Slack, logs the conversation on the matching HubSpot contact, and auto-stops dead sequences.

Trigger: a webhook from HeyReach. The agent should subscribe to the MESSAGE_REPLY_RECEIVED and INMAIL_REPLY_RECEIVED event types from HeyReach's outgoing webhooks. Both events deliver the lead name, company, LinkedIn profile URL, email if known, campaign ID, and the reply text.

On every reply, the agent should:

1. Classify the reply intent into one of: positive interest, objection, referral, out of office, not interested, or unsubscribe. If the webhook payload is thin, use HeyReach's Get Chatroom to pull the surrounding conversation history before classifying. Also produce a one-line suggested next action for the rep (for example: book a discovery call, send case study, route to the referred contact, snooze for 2 weeks, mark closed-lost).

2. Post a Slack message to our sales triage channel using the Slack Bot Send a Message action. The message should include: lead name, company, LinkedIn profile URL, the reply text in quotes, the detected intent, the campaign name it came from, and the suggested next action. Format it so reps can skim a dozen of these per morning.

3. In parallel, sync the reply into HubSpot. First search HubSpot contacts by email (if present) or by LinkedIn profile URL. If no match is found, use HubSpot's Create Contact with the available identity fields. Then use HubSpot's Create Note to attach a note to that contact summarizing the reply text, the campaign it came from, the detected intent, and the suggested next action. The note should be associated to the contact so it shows up on their CRM timeline.

4. If the detected intent is "not interested" or "unsubscribe", call HeyReach's Stop Lead In Campaign so the sequence stops automatically and we never message that prospect again from that campaign.

Make the Slack channel, the auto-stop intents, and the intent taxonomy easy to edit at the top of the workflow so the user can tune it without touching the rest. Keep error handling graceful: if HubSpot fails, still post to Slack; if Slack fails, still write the HubSpot note; log any failures so they can be retried.

Additional information

What does this prompt do?
  • Catches every prospect reply from your HeyReach LinkedIn campaigns, including regular messages and InMail responses, the moment they come in.
  • Reads the reply, classifies the intent (positive interest, objection, referral, out of office, not interested, or unsubscribe), and recommends a next step.
  • Posts a clean Slack message to your sales channel with the lead name, company, LinkedIn profile, the reply text, the intent, and the suggested action.
  • Finds or creates the matching HubSpot contact and attaches a note with the reply, the campaign it came from, and the intent so your CRM stays in sync.
  • Automatically stops the HeyReach sequence when someone replies with not interested or unsubscribe so you stop messaging cold prospects.
What do I need to use this?
  • A HeyReach account with at least one active LinkedIn outreach campaign.
  • A Slack workspace and a channel where your sales team triages new replies.
  • A HubSpot account with permission to view and create contacts and notes.
How can I customize it?
  • Change the Slack channel, or send replies to different channels based on intent (hot leads to one channel, objections to another).
  • Tweak the intent categories or the suggested next actions to match how your team runs its playbook.
  • Decide which intents should auto-stop the HeyReach sequence, or turn off auto-stop entirely and leave it to the rep.

Frequently asked questions

Does this work for both LinkedIn messages and InMails?
Yes. The workflow listens for both regular message replies and InMail replies from HeyReach, so any time a prospect responds the team gets pinged.
What happens if the prospect is not already in HubSpot?
If we cannot match them by email or LinkedIn profile, a new contact is created so the reply still gets logged in your CRM.
Can I stop the auto-stop behavior for unsubscribes?
Yes. The auto-stop is a knob you can turn off, or scope it to only a subset of intents like unsubscribe.
Will every reply show up in Slack, even off-topic ones?
Every reply triggers a Slack message by default, but the intent tag makes it easy to skim. You can also route low-priority intents like out of office to a quieter channel.
Does this overwrite existing HubSpot contact properties?
No. We only add a new note on the contact and create the contact if it does not exist. Existing properties are left alone.

Never miss a hot LinkedIn reply again.

Connect HeyReach, Slack, and HubSpot once, and Geni triages every prospect reply the moment it lands.