Book a demo
HubSpot Inbox

Reply from HubSpot. Send from your outbound domains.

Your reps answer outbound replies right inside HubSpot. Master Inbox routes each reply out through the secondary sending domain the thread started on, so threads and headers stay intact. Better deliverability, higher reply rates.

Book a demo See pricing

No forwarding. No CCing your main inbox. No broken threads.

Master Inbox integrations: HubSpot, sequencers and LinkedIn tools connected in one workspace

What moves, and which way

One connection, running constantly in both directions. No forwarding rules, no CSV, no middleware.

HubSpot
Where your reps and your reporting already live.
← Activities up, into HubSpot

Contacts created or matched, emails logged as sent and received, LinkedIn messages logged as native LinkedIn activities rather than generic notes, including messages sent through HeyReach, and meetings on the timeline.

→ Replies down, into Master Inbox

Anything your rep writes on the record, plus HubSpot Calendar bookings, reschedules and cancellations.

↔ Properties, both ways

Any Master Inbox field to any HubSpot property and back, labels to lead status, fixed values, and masterinbox_prospect_id on every synced contact.

Master Inbox
Where every reply lands, from every sequencer and LinkedIn tool.

Unlimited two-way sync. No per-action fees, no caps, no metering, and a notification with HubSpot's exact reason if a sync ever fails.

Reply from where you already live

Your rep never opens another tab. The reply still leaves from the domain the prospect answered.

Real recording: the Master Inbox card on a HubSpot contact record, replying to an outbound thread.

What happens on send

One reply, two hops, no broken thread

The card is on the record your rep already works. Sending from it does not send from HubSpot's connected inbox.

  • Your rep replies in HubSpotWrites the answer on the contact record, with formatting, links and their mailbox signature.
  • Master Inbox routes it outSends through the exact secondary sending domain the thread started on, with the original headers.
  • The prospect sees one threadSame domain, same conversation. Deliverability holds, and the sequence stops itself so follow-ups never talk over a live reply.
Formatting: type **bold** or *italic* and paste links. They arrive formatted in the email your prospect receives.

Start without writing a single property

Match-only mode is how teams trial this on a production portal.

Match only

Master Inbox finds and links existing HubSpot contacts, and writes nothing to them. You see the conversation on the record, your data stays exactly as it was.

What it does

Links, never writes

Prospects are matched to existing contacts by email address or LinkedIn profile. No new records, no property updates, no duplicates.

Why teams start here

Zero risk to a live portal

Ops teams who guard their CRM can see exactly what the integration would touch before anything is written.

When you are ready

Open it one field at a time

Switch on the properties you want, pick which mailboxes and channels sync at all, and leave the rest closed.

What is on the card

Add it to the main record area, the right sidebar, or both.

On the card
What your rep sees
The conversation

Email and LinkedIn history in one thread, formatted with bold, links and bullet points, and quoted reply chains dimmed so the new message stands out.

Who they are

Name, email, company, the channel the conversation runs on, any labels applied, and whether they are currently in an outreach sequence.

The reply box

Write and send in place. Email replies thread onto the existing conversation and include your mailbox signature automatically.

Sequence control

Replying from HubSpot removes that person from any active sequence, so automated follow-ups never talk over a live conversation.

Booking

HubSpot Calendar booking without leaving the record.

Every channel your outreach runs on

The card sends through whichever channel the conversation started on, from the same sender, so replies land in the existing thread instead of starting a new one. Master Inbox is post-send: your sequencer keeps doing the sending.

EmailGoogleOutlookZohoCustom IMAP/SMTPInstantlyReply.ioSmartlead
LinkedInLinkedInHeyReachLeadBirdAimfoxExpandiSalesFlowSalesRobot
BothLemlistGetSales

Settings and mapping, under your control

  • Field mapping. Send any Master Inbox field to any HubSpot property. Works both ways: HubSpot values can fill in gaps on the Master Inbox side.
  • Fixed values. Always write a set value to a HubSpot property, useful for tagging where a contact came from.
  • Labels to lead status. When a label is applied in Master Inbox, the contact's lead status updates in HubSpot.
  • Campaign source. Map campaign_source to report on the tool a reply actually came from, Instantly, HeyReach and others, rather than the mailbox it arrived through.
  • Match-only mode. Find and link existing HubSpot contacts without ever writing data to them.
  • Channel selection. Choose which mailboxes and channels sync at all.
Every synced contact carries a masterinbox_prospect_id property, so you can always trace a HubSpot record back to the conversation it came from.
Pricing
+$400/mo

On any plan. Included in Unlimited, Revenue and Enterprise.

See full pricing →

Questions we get

Do I have to forward or CC replies into HubSpot?
No. That is the point. Replies sync into HubSpot on their own, and when a rep answers from HubSpot, Master Inbox sends it out through the right sending domain automatically.
Why route through the secondary sending domain?
The prospect replied to your outbound domain. Answering from a different address breaks the thread and looks like a new sender to spam filters. Keeping the reply on the same domain keeps the thread, the headers, and the deliverability you built.
Does this replace my sequencer?
No. Your sequencer keeps sending. Master Inbox handles everything after the reply comes in, including replies your reps write inside HubSpot.
Is the sync metered?
No. Unlimited two-way sync with no per-action fees and no caps.
What does setup look like?
One connection, one app. Connect from Master Inbox, Settings, Integrations, HubSpot. Approving the permissions switches on the sync and the contact card together. Nothing else to set up and no keys to copy between systems. If a sync ever fails, Master Inbox notifies you with the exact reason HubSpot gave.
Will the sync eat my HubSpot API limits or trigger per-action fees?
No. The sync is unmetered on our side: no per-action fees, no sync caps. It uses HubSpot's standard app framework, the same way any certified integration does.
Can it link contacts without writing to them?
Yes. Match-only mode finds and links existing HubSpot contacts without ever writing data to them, which is the safe way to trial the integration on a production portal.
What about Salesforce?
Native Salesforce is on the roadmap. Today, teams push replies into Salesforce by webhook, or run attribution-grade syncing through our OutboundSync partnership.
Something you want the integration to do that it doesn't yet?
Email us at [email protected]. We'd like to hear it.

See it on your own portal

Book a demo and watch a reply written in HubSpot leave from your outbound domain, on a live thread. Free 7-day POC.

Book a demo