CRM

Outlook Reply Intent to Salesforce Opportunity Updater

Reads inbound Outlook replies, scores buyer intent and sentiment, and updates the linked Salesforce opportunity stage, close-date risk, and next-step task.

CategoryCRM
Enginesim
Difficultyintermediate
Triggerevent
Steps6
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerNew inbound reply in Outlook mailboxOutlook
  • ActionMatch opportunity in Salesforce by contactSalesforce
  • ActionClassify intent and score sentimentOpenAI
  • LogicDecide advance, hold, or flag risk
  • ActionUpdate opportunity stage and risk flagSalesforce
  • OutputCreate follow-up task for the ownerSalesforce

What it does

This workflow watches a sales inbox in Outlook, classifies each reply for intent and sentiment, and pushes the result into Salesforce — updating the opportunity stage, flagging close-date risk when momentum stalls, and creating a follow-up task assigned to the owner.

When to use it

Use it when your team lives in Outlook but reports in Salesforce, and forecast accuracy suffers because opportunity stages and close dates lag behind what buyers are actually saying.

How it works

  1. 1An inbound reply arrives in the monitored Outlook mailbox.
  2. 2The thread is matched to a Salesforce opportunity via the contact's email.
  3. 3OpenAI returns an intent label, a sentiment score, and a recommended next action.
  4. 4A logic branch decides whether to advance the stage, hold, or raise a close-date risk flag.
  5. 5Salesforce is updated with the new stage and risk flag, and a dated follow-up task is created for the opportunity owner.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect OutlookMail, calendar, contacts.
  2. 2
    Connect SalesforceAccounts, opportunities, cases.
  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.