Outreach is a sales engagement platform that allows sales and business development representatives to automate sales, manage their prospects and leads, and derive insights into data.
Outreach uses OAuth 2.0 to identify Hevo and authorize the request for accessing account data.
Prerequisites
-
An active Outreach account.
-
You are assigned the Team Administrator, Team Collaborator, or Pipeline Administrator role in Hevo to create the Pipeline.
Configuring Outreach as a Source
Perform the following steps to configure Outreach as the Source in your Pipeline:
-
Click PIPELINES in the Navigation Bar.
-
Click + CREATE PIPELINE in the Pipelines List View.
-
On the Select Source Type page, select Outreach.
-
On the Configure your Outreach account page, do one of the following:
-
Select a previously configured account and click CONTINUE.
-
Click + ADD OUTREACH ACCOUNT and log in to your Outreach account:
-
-
On the Configure your Outreach Source page, specify the following:
-
Pipeline Name: A unique name for the Pipeline, not exceeding 255 characters.
-
Authorized User Account: The Outreach account that you configured. This field is non-editable.
-
-
Click CONTINUE.
-
Proceed to configuring the data ingestion and setting up the Destination.
Data Replication
| For Teams Created | Default Ingestion Frequency | Minimum Ingestion Frequency | Maximum Ingestion Frequency | Custom Frequency Range (in Hrs) |
|---|---|---|---|---|
| Before Release 2.21 | 1 Hr | 1 Hr | 24 Hrs | 1-24 |
| After Release 2.21 | 6 Hrs | 30 Mins | 24 Hrs | 1-24 |
Note: The custom frequency must be set in hours as an integer value. For example, 1, 2, or 3, but not 1.5 or 1.75.
-
Historical Data: In the first run of the Pipeline, Hevo ingests all the existing data for the selected objects from your Outreach account and loads it to the Destination.
-
Incremental Data: Once the historical load is complete, data is ingested as per the ingestion frequency in Full Load or Incremental mode, as mentioned in the table below.
Schema and Primary Keys
Hevo uses the following schema to upload the records in the Destination database:
Data Model
The following is the list of tables (objects) that are created at the Destination when you run the Pipeline:
| Object | Mode | Description |
| Account | Incremental | Contains the details of the companies added in your Outreach account and their categorization in an account-based sales strategy. |
| Audit | Full Load | Contains the details of the Events that happen in your Outreach account. For example, login, logout, exporting a CSV, and adding or removing users. |
| Call Disposition | Incremental | Contains the details of the outcomes of calls made to prospective customers. |
| Call Purpose | Incremental | Contains the details of the purpose of calls made to the prospective customers. |
| Call | Incremental | Contains the details of inbound and outbound calls made to the prospective customers. |
| Compliance Request | Full Load | Contains the details of the privacy compliances laws that define the amount of personal information that can be retained in Outreach. |
| Content Category | Incremental | Contains the details of the various categories created in your Outreach account to increase discoverability of the content for your product or service. |
| Content Category Membership | Incremental | Contains the details of the category of the product or service content. |
| Content Category Ownership | Incremental | Contains the details of the relationship between the content category and the team that created it. |
| Duty | Full Load | Contains the details of the job that is to be performed by a user in their organization. |
| Email Address | Full Load | Contains the details of the email address of the prospective customer. |
| Event | Full Load | Contains the details of any actions that are done by users in their Outreach account. For example, creating mailbox, adding mail alias, and creating a template. |
| Favorites | Incremental | Contains the details of the records marked as favorite in your Outreach account. For example, prospects, accounts, and template. |
| Mail Alias | Incremental | Contains the details of the alternative email used in the Outreach mailbox. |
| Mailbox | Incremental | Contains the details of the email service provider integrated in your Outreach account. |
| Mailing | Incremental | Contains the details of the email sent to prospective customers. |
| Opportunity | Incremental | Contains the details of a sale or a pending deal with a prospective customer. |
| Opportunity Prospect Role | Incremental | Contains the details of the role of a prospect and their relationship with an opportunity. |
| Opportunity Stage | Incremental | Contains the details of the stage that an opportunity is in. |
| Persona | Incremental | Contains the details of the prospective customers. |
| Phone Number | Full Load | Contains the details of the prospect’s phone number. |
| Profile | Full Load | Contains the details of permissions that define what you can do within your Outreach account. |
| Prospect | Incremental | Contains the details of the users or organizations interested in your product or service. |
| Recipient | Full Load | Contains the details of any communication received in your Outreach account. |
| Role | Full Load | Contains the details of your organization’s hierarchical structure. |
| Ruleset | Incremental | Contains the details of the various settings configured for sequences in your Outreach account. |
| Sequence State | Incremental | Contains the details of the prospects for whom sequences are built. |
| Sequence Step | Incremental | Contains the details of a step in sequences automated for prospect engagement. |
| Sequence Template | Full Load | Contains the details of templates being used, and the steps of the sequence they are being used in. |
| Sequence | Incremental | Contains the details of a set of emails sent sequentially to prospects, to increase engagement. |
| Snippet | Incremental | Contains the details of an email content that can be reused in the future. |
| Stage | Incremental | Contains the details of a status in the sales process. |
| Task Priority | Incremental | Contains the details of the categorization of tasks. |
| Task | Incremental | Contains the details of the various actions that can be taken for engaging prospective customers. For example, emailing or calling a prospect. |
| Team | Incremental | Contains the details of the different group of users in your Outreach account. |
| Template | Incremental | Contains the details of a pre-defined email layout that can be reused in the future. |
| User | Incremental | Contains the details of the persons who can access your Outreach account. |
Additional Information
Read the detailed Hevo documentation for the following related topics:
Source Considerations
-
Pagination: An API response for each Outreach object fetches one page with up to 1000 records.
-
Rate Limit: Outreach imposes a limit of 10000 API calls per hour. If the limit is exceeded, Hevo defers the ingestion till the limits reset. Read Rate Limiting to know more about rate limits in Outreach, and configure a suitable ingestion frequency for your Pipeline.
Limitations
-
Hevo currently does not support deletes. Therefore, any data deleted in the Source may continue to exist in the Destination.
-
Hevo does not provide you with the option to select the historical sync duration for loading historical data. All the historical data in your Outreach account is loaded.
-
Hevo does not load an Event into the Destination table if its size exceeds 128 MB, which may lead to discrepancies between your Source and Destination data. To avoid such a scenario, ensure that each row in your Source objects contains less than 100 MB of data.
Revision History
Refer to the following table for the list of key updates made to this page:
| Date | Release | Description of Change |
|---|---|---|
| Jan-07-2025 | NA | Updated the Limitations section to add information on Event size. |
| Mar-05-2024 | 2.21 | Updated the ingestion frequency table in the Data Replication section. |
| Nov-23-2022 | 2.02 | New document. |