Revenue
- Revenue
- Category
- OAuth
- Connection
- Accounts and deals
- Lands in memory
What agents do
The work that stays in Salesforce.
Brief the call from the opportunity
The next conversation starts from the deal, the last note, and the thread — not a blank CRM tab.
Draft the field update
Stage, amount, and next step are proposed from the call. Salesforce changes only after approval.
Write the note back
What was said becomes a note draft on the account, so the next person does not re-ask.
Flag the quiet deal
The agent notices the opportunity that stalled and drafts the follow-up you can send.
Keep pipeline next to the work
The deal shares memory with the ticket and the Slack thread that closed it.
Stay inside the records you connect
Morrow inherits the connecting user's access. It does not widen the org.
How you connect
Connect once. The brain starts from there.
- 01
Connect the account
One click into Salesforce, where the tool allows it. Morrow inherits that person's access — nothing wider.
- 02
Work writes itself in
The Salesforce records you scope to the project land in the company brain.
- 03
Agents act after you approve
Mor drafts the Salesforce update. Nothing is written back until you confirm.
In practice
What teams ask for
Prep before the customer call
Sales gets a short brief: stage, last objection, and the open ticket on the account.
CRM updated from the live thread
A Slack conversation becomes a proposed note and a stage change. You confirm both.
Follow-up for the deal that went quiet
The agent drafts the email from the opportunity, ready to send from your mail after approval.
Before you connect
Questions about this connection
Does Morrow see every object in Salesforce?
It sees what the connecting user can see, inside the project you invite it to.
Will it overwrite fields on its own?
No. Field updates and notes are drafts until a person approves them.
Can HubSpot and Salesforce both be connected?
Yes. They write into the same company brain, scoped to the projects you choose.
Often used with
