Does Outreach integrate with Salesforce and HubSpot?

Default works with Outreach and either CRM in 1 workflow: Match Record finds the person in HubSpot or Salesforce, Create Record or Update Record writes the routed rep as owner, and Add to Outreach Sequence enrolls them from that rep's mailbox. Natively, Outreach syncs with Salesforce, and HubSpot's data sync app connects HubSpot contacts to Outreach.

How do you add inbound leads to an Outreach sequence automatically?

Default enrolls them with the Add to Outreach Sequence node, after a Round-Robin node picks the rep and Create Record or Update Record writes that rep as the CRM owner. Set Sending mailbox to Latest assigned user, and map each rep's Outreach Mailbox ID in Default so the sequence sends from them.

What happens if the prospect is already in an Outreach sequence?

Default keeps the workflow running when Outreach rejects the enrollment: the Add to Outreach Sequence node's success output is false and its error says why, so a Multi-Branch node can send the lead to another step, such as a Slack alert to the owner. A Match Record node before routing also catches repeat submissions once the record exists.

More than an Outreach HubSpot integration

Send routed leadsinto Outreach sequences

Default adds routed leads who don't book to an Outreach sequence from their rep's mailbox.

Request a Demo

Form, Enrich Data, Round-Robin, and Add to Outreach Sequence nodes, sending from the assigned rep's mailbox

Sender follows routing

Set Sending mailbox to Latest assigned user, and the sequence sends from the routed rep's Outreach mailbox.

Display Scheduler Not booked branch leading to an Add to Outreach Sequence node

Not booked, then sequenced

A lead who submits the form but closes the calendar without booking goes into an Outreach sequence.

HubSpot contact owner and Outreach sending mailbox showing the same rep

Owner and sender match

The same run writes the rep as the HubSpot or Salesforce owner, so the CRM and Outreach name the same person.

Outreach sequencing routed leads from HubSpot or Salesforce, with HubSpot, Salesforce, Slack, and Round-Robin cards around it

Works with both CRMs

Match and create records in HubSpot or Salesforce before the lead goes into Outreach.

Leads who don't bookgo into a sequence

On the Not booked branch, Add to Outreach Sequence enrolls the person, so a lead who drops off still hears from their rep. Outreach finds the prospect by email or creates one.

Workflow sending a lead who closed the calendar to an Outreach sequence on the Not booked branch

Sequencing docs

Sequencing

Pick the sequence, the sending mailbox, and the lead's email, 1 person per run.

Unbooked leads docs

Follow up on unbooked leads

The branch runs when the visitor closes the calendar or the timeout passes.

The sequence sends fromthe rep who owns the lead

Set Sending mailbox to Latest assigned user, and Default maps the rep to their Outreach mailbox. Write the owner to the CRM in the same run, so every system names the same person.

Round-Robin picking a rep, Outreach sending from that rep's mailbox, and the same rep as HubSpot contact owner

Sequence handoff docs

Routed leads to sequences

Route the lead, write the owner, and enroll the person in 1 workflow.

Queues docs

Queues

Members, weights, and calendar checks decide which rep is next.

FAQ

Questions about the Outreach HubSpot integration

Default works with Outreach and either CRM in 1 workflow: Match Record finds the person in HubSpot or Salesforce, Create Record or Update Record writes the routed rep as owner, and Add to Outreach Sequence enrolls them from that rep's mailbox. Natively, Outreach syncs with Salesforce, and HubSpot's data sync app connects HubSpot contacts to Outreach.
Default enrolls them with the Add to Outreach Sequence node, after a Round-Robin node picks the rep and Create Record or Update Record writes that rep as the CRM owner. Set Sending mailbox to Latest assigned user, and map each rep's Outreach Mailbox ID in Default so the sequence sends from them.
Default keeps the workflow running when Outreach rejects the enrollment: the Add to Outreach Sequence node's success output is false and its error says why, so a Multi-Branch node can send the lead to another step, such as a Slack alert to the owner. A Match Record node before routing also catches repeat submissions once the record exists.