Is the HubSpot integration available yet?

Not yet — it’s in active development. Because Ember’s CRM layer is provider-agnostic, HubSpot will reuse the same sync and grounding behavior already live for Attio.

Will Ember write back to HubSpot?

Yes. As with Attio, Ember will read contacts, notes, and history to ground drafts, and write email activity back so your CRM stays current.

How is this different from HubSpot sequences?

Sequences enroll contacts into a fixed series of templated emails. Ember reasons about each contact individually — it reads the actual relationship history and drafts the specific email that fits where things stand, for your approval. One is built for volume; the other for relationships you intend to keep.

Do I have to leave HubSpot to use Ember?

No. Ember is designed to work alongside your CRM, not against it. HubSpot stays your system of record; Ember does the outreach work on top and keeps the record current.

Integration · Coming soon

Ember + HubSpot

Relationship-driven outreach on top of your HubSpot data.

Ember’s CRM layer is provider-agnostic. HubSpot support uses the same sync and grounding behavior as Attio: read contacts, notes, and history to write context-aware drafts, and write activity back.

What it does

Contact and activity sync
Grounds drafts in HubSpot notes and history
Activity written back to HubSpot

How it works

1Connect HubSpot through its official OAuth — secure and revocable.
2Ember reads your contacts, notes, and history to understand each relationship.
3It grounds every draft in that real context before queuing it for your approval.
4Email activity is written back to HubSpot so the record stays current.

What syncs

Ember reads

Contacts and core properties
Notes and engagement history
Activity timeline context

Ember writes

Email activity logged to the contact
Updates that keep HubSpot current

Why it matters

Ember’s CRM layer is provider-agnostic, so HubSpot uses the same read-then-write behavior as the live Attio integration: it grounds drafts in your real notes and history, and logs activity back so the record stays accurate.

HubSpot is excellent at holding your go-to-market data — and like every CRM, it still depends on someone doing the follow-up. Sequences cover the high-volume end, but the relationship-driven deals in your pipeline need something different: an email that reflects the last call, the open question, the commitment someone made. Ember reads that context out of HubSpot and your inbox, writes the email, and logs the activity back — so the contact record stays current and the deal actually moves.

HubSpot support is in active development — we’ll ship it when it’s genuinely solid, not before. Attio is fully supported today if you need a relationship-driven CRM sync now, and Ember works from your connected inbox either way.

Frequently asked

Is the HubSpot integration available yet?: Not yet — it’s in active development. Because Ember’s CRM layer is provider-agnostic, HubSpot will reuse the same sync and grounding behavior already live for Attio.
Will Ember write back to HubSpot?: Yes. As with Attio, Ember will read contacts, notes, and history to ground drafts, and write email activity back so your CRM stays current.
How is this different from HubSpot sequences?: Sequences enroll contacts into a fixed series of templated emails. Ember reasons about each contact individually — it reads the actual relationship history and drafts the specific email that fits where things stand, for your approval. One is built for volume; the other for relationships you intend to keep.
Do I have to leave HubSpot to use Ember?: No. Ember is designed to work alongside your CRM, not against it. HubSpot stays your system of record; Ember does the outreach work on top and keeps the record current.