CRM

Outlook Reply Intent Classifier to HubSpot Stage Router

Classifies the intent of inbound Outlook replies on open deals and automatically advances or regresses the HubSpot deal stage and writes the next step.

CategoryCRM
Enginesim
Difficultyintermediate
Triggerevent
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerNew inbound reply in Outlook mailboxOutlook
  • ActionMatch deal in HubSpot by sender emailHubSpotHubSpot
  • ActionClassify reply intent and draft next stepOpenAI
  • LogicMap intent label to target deal stage
  • OutputUpdate HubSpot stage, next step, and noteHubSpotHubSpot

What it does

When a prospect replies to a sales thread in Outlook, this workflow reads the reply, classifies the buyer's intent (interested, needs pricing, objection, not now, unsubscribe, etc.), and updates the matching HubSpot deal — moving the stage forward or back and setting a concrete next step on the deal record.

When to use it

Use it when reps forget to update the CRM after a reply, deals go stale in the wrong stage, and you want pipeline hygiene to happen automatically the moment a buyer responds.

How it works

  1. 1A new inbound message lands in the rep's Outlook mailbox and fires the trigger.
  2. 2The deal is matched in HubSpot by the sender's email address.
  3. 3OpenAI classifies the reply into one intent label plus a one-line suggested next step.
  4. 4A logic branch maps each intent to a target stage (e.g. objection -> Negotiation, not now -> Nurture).
  5. 5The HubSpot deal stage and next-step field are updated, and an internal note is logged.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect OutlookMail, calendar, contacts.
  2. 2
    Connect HubSpotCRM, deals, marketing, support.
  3. 3
    Connect OpenAIModels, embeddings, files.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.