Turn LeadsForge positive replies into HubSpot deals and Slack alerts

Build an agent workflow that turns a LeadsForge positive reply into a full CRM handoff so the assigned rep can act on it immediately.

Trigger: subscribe to a LeadsForge (Salesforge) outgoing webhook for the positive_reply event. The workflow should only run when that event fires. The webhook payload will include the thread id, contact info, and the sequence the reply came from.

On fire, the agent should do the following in order:

1. Call LeadsForge Get Thread using the thread id from the webhook to pull the full reply thread, the sender's name and email, the assigned mailbox or owner, and the sequence name and metadata. Use the thread body to reason about what the prospect actually said.

2. Look the prospect up in HubSpot using Get Contact with idProperty=email. If they do not exist, use Create Contact to add them with the name and email from the LeadsForge thread. If they already exist, reuse that contact id.

3. Use HubSpot Create Deal to open a new deal associated with that contact. Name the deal after the prospect and the sequence, stamp a custom source property with the LeadsForge sequence name, and drop it into the pipeline and initial stage the user specifies at setup time.

4. Use HubSpot Create Task to create a follow-up task associated with the same contact and deal, assigned to the LeadsForge sequence owner. Read the reply and pick one of three intents, and tune the task subject and due date to match:

- Booking intent (the prospect wants a call or a demo): task subject like "Book a call with <name>", due today or same business day.

- Question (the prospect is interested but wants information first): task subject like "Reply to <name> with <topic>", due within one business day.

- Soft not-yet (positive but wants to reconnect later): task subject like "Nurture <name> - not ready yet", due at the reconnect date the prospect mentions, or three business days out if unspecified.

5. Post a Slack Send a Message to the deals channel the user nominates at setup time. The message should include: the prospect name and company, a one to two sentence summary of what they said, the classified intent (booking, question, soft not-yet), the sequence name, the number of prior touches in the thread, the rep assigned, and a link to the newly created HubSpot deal. Format it with Slack mrkdwn so it is easy to scan.

Setup inputs the user should be asked for: the target HubSpot pipeline id and initial deal stage, the Slack channel id for alerts, and optionally an override for how soon booking-intent tasks are due.

Guardrails: if the contact lookup fails for any reason other than not-found, log and skip contact creation rather than duplicating. If any HubSpot write fails, still post the Slack alert with what was gathered so the rep is not silently blocked. Use idempotent lookups so a redelivered webhook does not create duplicate deals for the same reply thread.