Connect Outreach

Connect Outreach and you can dial your due call tasks, all of them or one sequence’s, straight from the dialer. Every call you log lands on the prospect, completes the task and moves the sequence to its next step. Your Outreach sequences keep running on time, and reps never mark a call task done by hand.

Before you start

An Outreach profile that allows API access for each rep who connects.
Salesfinity allowed in Outreach, if your Outreach admin limits which apps a role may authorize.
A default call purpose in mind. Many Outreach orgs require one on every call.

Go to Settings › Connections › Integrations, find the Outreach card and click Connect. Sign in to Outreach and approve the permissions. If the page fails before you reach Outreach’s approval screen, ask your Outreach admin to allow Salesfinity.

Set a default call purpose

In the integration’s settings, choose the Default call purpose. It goes on every logged call unless you pick another one while logging. Set this first.

Map dispositions and fields

Use the automatic suggestion to map each Salesfinity disposition to an Outreach call disposition. Then map prospect fields to Salesfinity fields, and add any custom prospect or account fields you want on the contact card.

Test with one call

Import your due tasks, dial one prospect and log the call. In Outreach, the prospect should have a new call, the task should be complete and the sequence should be on its next step.

You are done when a test call shows on the prospect in Outreach with the right disposition and purpose, and its call task is complete.

What Salesfinity imports

Every Outreach import is built from call tasks. A prospect is imported only when they have an incomplete call task owned by you, due today or earlier.

One sequence
All tasks

Pick a sequence. Salesfinity imports the prospects in it who have such a task. Prospects in the sequence with no call task due are not imported. The list is named after the sequence.

Before the import finishes, Salesfinity removes the phone numbers your Outreach org has marked invalid. You do not dial numbers Outreach already knows are dead. Every contact keeps its Outreach prospect ID and, for task imports, the task ID and sequence step. That is what lets the call complete the right task later.

What Salesfinity writes back

When you log a call on an Outreach prospect, Salesfinity creates a call in Outreach.

Call attribute	Value
Direction	Outbound
Outcome	Completed
Note	Your call notes
Answered at, completed at	The call’s start and end time
To, from	The number reached and the number dialed from
Recording URL	A link to the recording, when the call was recorded
Sequence action	The step the task belonged to, so the sequence advances
Tags	”Salesfinity”
Disposition	The Outreach call disposition mapped from your Salesfinity disposition
Call purpose	The purpose you chose when logging, or your default call purpose
Task	The imported task, marked complete

If the task no longer exists, for example because the sequence was edited after import, the call is still logged without the task link. When the call was recorded, Salesfinity also sends the recording to Outreach’s Kaia so Outreach can transcribe and analyze it. This runs after the call is logged and never holds it up. Only contacts imported from Outreach are logged to Outreach. A call on a CSV or custom-list contact goes to your connected CRMs instead. See how a call gets back to your CRM. Phone numbers found by enrichment or edited in the dialer can be written back to the prospect.

Sequences

From the dialer’s sequence controls you can add a prospect to a sequence, remove them, and move them to another sequence. The contact card also shows the prospect’s current sequence, step and stage.

Permissions Outreach asks for

Scope	Why Salesfinity needs it
`prospects.read`, `prospects.write`	Import prospects, match a contact by email, create a prospect for a referral you capture on a call, and pause or resume their sequence.
`tasks.read`, `tasks.write`, `taskPriorities.read`	Import your due call tasks and complete them when the call is logged.
`calls.read`, `calls.write`	Create a call for every dialed call and read past call activity.
`callDispositions.read`	List call dispositions for the disposition mapping.
`callPurposes.read`, `callPurposes.write`, `callPurposes.all`	List call purposes and attach the chosen purpose to each call.
`sequences.read`, `sequenceSteps.read`, `sequenceStates.write`	List sequences to import from, read a task’s step, and add or remove prospects in sequences.
`stages.read`	Show prospect stages on the contact card.
`accounts.read`, `accounts.write`	Read the prospect’s account and its fields.
`phoneNumbers.read`, `phoneNumbers.write`	Read prospect numbers, drop numbers Outreach flagged invalid, and sync enriched numbers back.
`users.read`, `teams.read`	Attribute calls and tasks to the connected user.
`mailboxes.read`, `mailings.read`, `mailings.write`	Show the prospect’s email history on the contact card.

Settings reference

Default call purpose

The Outreach call purpose added to every logged call unless you pick another while logging. Many Outreach orgs require a purpose on calls.

Disposition mapping

Maps each Salesfinity disposition to an Outreach call disposition. The automatic suggestion fills the table from your org’s disposition names, and you can adjust it.

Contact field mapping

Which Outreach prospect field fills each Salesfinity field.

Custom fields

Extra prospect and account fields to bring onto the contact in the dialer.

Staying connected

Outreach access tokens are short-lived. Salesfinity refreshes them the moment they expire, both when you use the dialer and when Ari or a routine works with Outreach in the background. If Outreach rejects the refresh, usually because the token was revoked, the card reads as disconnected. Reconnect from the same card.

Connect your tools

Keep data in sync

Connect Outreach

Before you start