ht
Documentation
WelcomeConcepts

Get Started

OverviewCreate a sourceCreate a modelCreate a destinationCreate a sync

Destinations

AcousticActiveCampaignAirtableAmplitudeAsanaAuth0Bing AdsBrazeChurnzeroClientSuccessCloseCustom DestinationCustomer.ioFacebook Conversions APIFacebook Custom AudiencesFacebook Offline Conversions APIFacebook Product CatalogFreshdeskFrontGainsightGainsight PXGoogle AdsGoogle Campaign ManagerGoogle SheetsHeapHubspotIntercomIterableJiraKlaviyoMailchimpMarketoMixpanelMoengageMongoDBmParticleNetsuiteNotionOneSignalOrbitOutreachPartnerstackPendoPipedrivePostgreSQLQualtricsReply.ioRoktRudderstackS3SailthruSalesforceSalesforce Marketing CloudSalesforce Marketing Cloud File DropSalesloftSegmentSendGridSFTPSlackSnapchatStripeTheTradeDesk PostbackTiktokTotangoUserflowVeroWebhookZendesk
Documentation/Destinations/Outreach
ht
Documentation

Outreach

Table of Contents
Overview
Outreach, the leading Enterprise ready Sales Engagement Platform, accelerates revenue growth by optimizing every interaction throughout the customer lifecycle.

Overview

This integration allows you to sync to Outreach objects.

Setup

After selecting Outreach from our Destinations catalog, you will be prompted to initiate an OAuth flow. You will then be redirected back to Hightouch.

Syncing rows to Outreach

Hightouch supports syncing to the following Outreach objects:
  • Accounts
  • Prospects

Sync Modes

There are two different possible modes for how to alter Outreach objects:
  • Upsert — pushes new objects to Outreach and updates fields that change in your warehouse.
  • Update — updates particular fields on existing objects in Outreach. It does not add new objects.

Record Matching

Records can be matched from your source to your Outreach workspace by the given fields in the dropdown.Note: The record should be matched using a unique identifier, otherwise the intended records may not be updated properly.

Field Mapping

You can sync columns from your source to Outreach's object properties, including custom fields.Note: You will still need to refer to the custom field number, despite having a different custom display name.