Revenue
- Revenue
- Category
- OAuth
- Connection
- Contacts and deals
- Lands in memory
What agents do
The work that stays in HubSpot.
Brief the next email from the contact
The draft uses the company, the last meeting, and the open deal — not a blank template.
Draft the deal update
Stage and notes are proposed from the thread. HubSpot changes after you approve.
List the deals that went quiet
The agent builds the follow-up list from deals that stalled, ready for a send you confirm.
Put pipeline next to support
The contact's ticket and the deal share one record, so a reply does not ignore the account.
Draft the note in your voice
Call notes land on the contact as a draft. You approve before they are saved.
Keep marketing and sales on one account
Campaign context and the live deal sit in the same project memory.
How you connect
Connect once. The brain starts from there.
- 01
Connect the account
One click into HubSpot, where the tool allows it. Morrow inherits that person's access — nothing wider.
- 02
Work writes itself in
The HubSpot records you scope to the project land in the company brain.
- 03
Agents act after you approve
Mor drafts the HubSpot update. Nothing is written back until you confirm.
In practice
What teams ask for
Follow-up after the demo
The sales agent drafts the email and the HubSpot note from the call. You send and save.
Quiet pipeline, one list
Deals with no recent activity become a list with a suggested note on each.
Support sees the account
A reply draft knows the deal stage, so the answer matches what sales already promised.
Before you connect
Questions about this connection
Does Morrow replace HubSpot?
No. HubSpot stays the system of record. Morrow reads it and drafts writes you approve.
Can it email contacts by itself?
It drafts the email. Sending waits for approval.
What access does the connection use?
The account of the person who connects. Nothing wider.
Often used with
