Outlook to Salesforce
About this source
Gen8
Source: Outlook to Salesforce
Managed AI service for SMEs. We set up, connect and manage; you stay in control.
© 2026 Gen8 VOF · Dutch Chamber of Commerce 92978789 · Delft
Capability · route: configured
Customer conversations from Outlook back into Salesforce, without retyping
The conversation is in Outlook, the source of truth belongs in Salesforce, and between them sits a person who retypes or forgets it. This workflow assesses the messages you authorize and proposes what should be added to Salesforce for each. The account manager approves; only then does anything go to the CRM.
- Scoping first, then a proposal
- EU hosting
- You stay in control
At a glance
Route: configured
Control: human approval
Systems: Outlook, Salesforce
What happens
From signal to proposal
The workflow gets access to an agreed Outlook mailbox or folder. For each message, it determines whether it belongs to an existing account, contact or opportunity, and what should change in Salesforce: an activity log, note, changed stage or follow-up task with a deadline.
This is presented as a proposal to the opportunity owner, who approves, edits or rejects. Salesforce is updated only after approval, always with a reference to the message behind the change, so a colleague can later verify why a field changed. The general email-to-CRM structure is described in email to CRM.
Access
You authorize a specific mailbox or folder. The workflow reads nothing outside that boundary.
Match
Does this message belong to an existing account or opportunity? Without a clear match, nothing is guessed and the message goes to the reviewer as an open question.
Proposal
A concrete proposed change: which field, value and follow-up task, and the message it is based on.
Approval
The opportunity owner approves, edits or rejects. Every decision is logged, including rejection.
Record
After approval, Salesforce is updated and the source remains visible with the record.
Limits
Where it stops
The workflow does not email on your behalf. It changes no stage transitions or closed deals without a person's case-by-case approval, and never deletes anything. Fields you designate as protected are only read, never written. If your qualification rule conflicts with the model's proposal, the rule wins. And the workflow reads no mailboxes you have not explicitly authorized.
Evidence
What we can demonstrate
Outlook mail and Salesforce each have their own integration in the platform, so this workflow does not need to work around a missing integration. What is configured per organization is the translation: which mailbox is authorized, which fields the workflow may propose, which qualification rule takes precedence and who signs off. That is why the route here is configured rather than native.
Does the Outlook side require a separate build?
No. Outlook mail has its own integration, just like Salesforce. What is configured per environment is which mailbox is authorized and which fields the workflow may propose.
Does this work with a shared mailbox too?
Yes, provided that mailbox is explicitly authorized. You separately agree who reviews proposals, because in a shared mailbox that is rarely one person.
Can the workflow move a deal to the next stage itself?
Only if you configure and approve that per stage. By default it proposes the transition rather than moving it itself.
How can I later find out why a field changed?
Every approved change retains the reference to the original message, along with who approved it and when.