Slack alerts and HubSpot logs for HeyReach replies

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.