Outreach (Edge)

Last updated on Nov 13, 2026

Hevo uses the Outreach API to replicate the prospects, accounts, opportunities, sequences, mailings, calls, tasks, events, users, and other data of your Outreach organization to the Destination of your choice. Hevo connects to Outreach using OAuth 2.0. To ingest data, you must authorize Hevo to read the data of your Outreach organization.

Supported Features

Feature Name	Supported
Capture deletes	Yes, except for the objects listed in Handling of Deletes
History mode	No
Custom data (user-configured tables & fields)	Yes, for the custom fields of the Account, Opportunity, Prospect, and Users objects
Data blocking (skip objects and fields)	Yes
Resync (objects and Pipelines)	Yes
API configurable	Yes

Getting Started

Setup

Data Sync

Prerequisites

An active Outreach account exists from which data is to be ingested.
You can log in to Outreach as a user with the Admin profile, which can read the data of all the objects. Outreach returns only the data that the profile of the user who authorizes Hevo can access. Read Source Considerations.

Scopes Required by Hevo

When you authorize Hevo, Outreach asks you to grant the following read-only scopes. Hevo uses each scope to read the objects listed against it:

Scope	Objects
accounts.read	Account and its child object
callDispositions.read	Call Disposition
callPurposes.read	Call Purpose
calls.read	Call and its child object
complianceRequests.read	Compliance Request
contentCategories.read	Content Category
contentCategoryMemberships.read	Content Category Membership
contentCategoryOwnerships.read	Content Category Ownership
duties.read	Duty
emailAddresses.read	Email Address
events.read	Event
favorites.read	Favorite
mailAliases.read	Mail Alias
mailboxes.read	Mailbox
mailings.read	Mailing and its child objects
opportunities.read	Opportunity and its child object
opportunityProspectRoles.read	Opportunity Prospect Role
opportunityStages.read	Opportunity Stage
personas.read	Persona
phoneNumbers.read	Phone Number
profiles.read	Profile
prospects.read	Prospect and its child objects
recipients.read	Recipient
roles.read	Role
rulesets.read	Ruleset
sequenceStates.read	Sequence State and its child objects
sequenceSteps.read	Sequence Step
sequenceTemplates.read	Sequence Template
sequences.read	Sequence and its child object
snippets.read	Snippet and its child object
stages.read	Stage
taskPriorities.read	Task Priority
tasks.read	Task
teams.read	Team
templates.read	Template and its child objects
users.read	Users and its child objects

Configure Outreach as a Source in your Pipeline

Perform the following steps to configure your Outreach Source:

Click Pipelines in the Navigation Bar.
Click + Create Pipeline in the Pipelines List View.
On the Select Source Type page, select Outreach.
On the Select Destination Type page, select the type of Destination you want to use.
On the Select Pipeline Type page, click Edge, and then click Continue.
In the Configure Source screen, specify the following:
- Source Name: A unique name for your Source, not exceeding 255 characters. For example, Outreach Source.
- In the Connect to Outreach section, click Authorize With Outreach, log in to your Outreach account if prompted, and allow Hevo to read your data with the requested scopes. Hevo displays the email address of your Outreach user as Account Added.
Click Test & Continue to test the connection to your Outreach Source. Once the test is successful, you can proceed to set up your Destination.

If the user who authorized Hevo is deactivated in Outreach or revokes the access granted to Hevo, Hevo cannot read your Outreach data, and the jobs of the Pipeline fail. To resume data replication, modify the Source configuration in the Pipeline and authorize Hevo again. Once the updated configuration is saved, Hevo re-authenticates the Source, and data ingestion resumes from the last saved position.

Data Replication

Hevo replicates data for all the objects selected on the Configure Objects page during Pipeline creation. By default, all supported objects and their available fields are selected. However, you can modify this selection while creating or editing the Pipeline. To ingest a child object, you must also select its parent object. For example, to ingest the Prospect Tag object, you must also select the Prospect object. The Data Model lists the child objects of each parent object.

In the first run of the Pipeline, Hevo ingests all the data available for the selected objects in your Outreach organization. In the subsequent runs, as per the sync frequency, Hevo ingests data as follows:

Ingestion	Objects
All the records, in each run	Compliance Request, Custom Field, Duty, Phone Number, Profile, Recipient, Role, Sequence Template, and Team
New and updated records, based on the time each record was last updated in Outreach	All the other parent objects, such as Account, Call, Event, Mailing, Opportunity, Prospect, Sequence, Sequence State, Task, Template, and Users

Hevo ingests the child objects of a parent object along with it. When Hevo ingests a new or updated parent record, it replaces the child records of that parent in the Destination.

Outreach limits API requests per user, to 10,000 requests per hour. Read Rate Limiting. If Outreach returns a rate limit error, Hevo waits and retries the request. If a run stops because of a rate limit, Hevo resumes from the last saved position in the next run. To understand how Hevo handles such scenarios, read Handling Rate Limit Exceptions.

Pipelines with this Source support only the Merge load mode.

Schema and Primary Keys

Hevo uses the following schema to upload the records in the Destination. For a detailed view of the objects, fields, and relationships, click the ERD.

Click to view ERD

Data Model

The following is the list of tables (objects) that are created at the Destination when you run the Pipeline:

Object	Description
Account	Contains the companies that your prospects belong to, with their name, domain, industry, owner, and custom fields. It includes a child object, Account Tag, which contains the tags of each account.
Call	Contains the calls logged in Outreach, with their direction, duration, outcome, disposition, purpose, and the prospect and opportunity of each call. It includes a child object, Call Tag, which contains the tags of each call.
Call Disposition	Contains the call dispositions defined in your Outreach organization, with their name and outcome.
Call Purpose	Contains the call purposes defined in your Outreach organization.
Compliance Request	Contains the compliance requests, such as requests to delete the data of a prospect, with their state and requester.
Content Category	Contains the content categories that group your templates, snippets, and sequences.
Content Category Membership	Contains the content that belongs to each content category.
Content Category Ownership	Contains the users and teams that own each content category.
Custom Field	Contains the custom fields defined in your Outreach organization, with the object and the label of each field.
Data Connection	Contains the links between Outreach records and the records of your connected CRM.
Duty	Contains the duties (job functions) that users can be assigned in Outreach.
Event	Contains the events that Outreach logs, such as emails opened and prospects updated, with the related prospect, mailing, call, and account.
Favorite	Contains the records that users have marked as favorites.
Mail Alias	Contains the email aliases of each mailbox.
Mailbox	Contains the mailboxes that users connect to Outreach to send email, with their email address and sync settings.
Mailing	Contains the emails sent or scheduled from Outreach, with their subject, state, delivery and engagement times, and the prospect, sequence, and mailbox of each email. It includes the following child objects: - Mailing Recipient - Mailing Reference
Opportunity	Contains the opportunities in Outreach, with their amount, stage, close date, owner, account, and custom fields. It includes a child object, Opportunity Tag, which contains the tags of each opportunity.
Opportunity Prospect Role	Contains the roles that prospects hold in opportunities.
Opportunity Stage	Contains the opportunity stages defined in your Outreach organization.
Persona	Contains the personas that you assign to prospects.
Phone Number	Contains the phone numbers of your prospects, with their type and status.
Profile	Contains the governance profiles that set what Outreach users can access.
Prospect	Contains the people that you engage in Outreach, with their contact details, stage, owner, account, engagement counts, and custom fields. It includes the following child objects: - Email Address - Prospect Email - Prospect Favorite - Prospect Home Phone - Prospect Mobile Phone - Prospect Other Phone - Prospect Tag - Prospect VoIP Phone - Prospect Work Phone
Recipient	Contains the recipients of emails sent from Outreach.
Role	Contains the roles in the hierarchy of your Outreach organization.
Ruleset	Contains the rulesets that control how sequences behave.
Sequence	Contains the sequences of your Outreach organization, with their type, state, owner, ruleset, and engagement counts. It includes a child object, Sequence Tag, which contains the tags of each sequence.
Sequence State	Contains the state of each prospect in a sequence, with the current step and the mailbox that sends the emails. It includes the following child objects: - Active Step Mailing - Active Step Task
Sequence Step	Contains the steps of each sequence, with their type, order, and interval.
Sequence Template	Contains the templates used by the steps of each sequence.
Snippet	Contains the reusable text snippets of your Outreach organization. It includes a child object, Snippet Tag, which contains the tags of each snippet.
Stage	Contains the prospect stages defined in your Outreach organization.
Task	Contains the tasks assigned to users, with their type, state, due date, priority, and the prospect, account, opportunity, and sequence of each task.
Task Priority	Contains the task priorities defined in your Outreach organization.
Team	Contains the teams of your Outreach organization.
Template	Contains the email templates of your Outreach organization, with their subject, owner, and engagement counts. It includes the following child objects: - Template BCC Recipient - Template CC Recipient - Template Tag - Template To Recipient
Users	Contains the users of your Outreach organization, with their email address, role, profile, and team. It includes the following child objects: - User Duty - User Email Recipients - User Team

Additional Information

Read the detailed Hevo documentation for the following related topics:

Handling of Deletes

Hevo marks a record as deleted by setting the value of the metadata column __hevo__marked_deleted to True. Hevo captures deletes as follows:

For the objects whose records Hevo ingests in full in each run, Hevo compares the records fetched from Outreach with those in the Destination table. Records that are no longer returned by Outreach are marked as deleted in the Destination. If Outreach returns no records for an object in a run, Hevo does not mark any records of the object as deleted.
For the Account, Call, Mailing, Opportunity, Prospect, Sequence, Sequence State, and Task objects, Hevo reads all the records of the object once a day, along with the incremental data, because Outreach does not report deleted records in its API. Records that are no longer returned by Outreach are marked as deleted in the Destination. As a result, a record deleted in Outreach can remain unmarked in the Destination for up to a day.

Hevo reads all the records of these objects once a day by default. Contact Hevo Support to change this interval for your Pipeline, to a value from 1 to 90 days.
For the other objects that Hevo ingests incrementally, such as Event, Snippet, Template, and Users, and the lookup objects such as Persona and Stage, Hevo does not capture records that are deleted in Outreach. These records remain in the Destination. For the Snippet, Template, and Users objects, Hevo reads all the records once a day to rebuild their child objects, and marks the child records that are no longer returned by Outreach as deleted.
For child objects, when Hevo ingests a new or updated parent record, it loads the current child records of that parent. The child records removed from the parent record in Outreach are marked as deleted in the Destination when Hevo reads all the records of the parent object, for example, when you resync the object.

Source Considerations

Hevo ingests the custom fields of the Account, Opportunity, Prospect, and Users objects that are labeled in your Outreach organization or that contain data. Hevo adds a column for each such custom field. The Custom Field object lists the custom fields and their labels.
If the profile of the user who authorized Hevo cannot access an object in Outreach, Hevo shows a permission warning and marks the object and its child objects as Inaccessible. The other objects continue to be ingested. To ingest the object, give the user access to it in Outreach, or authorize Hevo with a user who has the Admin profile, and then resync the object.
If Outreach returns a field that is not part of the schema of an object, Hevo adds a text column for the field, with its name in snake case. For example, the field imapSSl is loaded into the column imap_ssl. Hevo adds up to 100 such columns to a table.
Hevo creates a table in the Destination for each selected object, even if the object has no data in Outreach.

Revision History

Refer to the following table for the list of key updates made to this page:

Date	Release	Description of Change
Nov-12-2026	2.54	New document.