Outreach integration summary

Stitch’s Outreach integration replicates data using the Outreach REST API. Refer to the Schema section for a list of objects available for replication.

Outreach feature snapshot

A high-level look at Stitch's Outreach (v1) integration, including release status, useful links, and the features supported in Stitch.

STITCH
Release status

Beta

 Supported by

Singer Community
Stitch plan

Standard

 API availability

Available
Singer GitHub repository

singer-io/tap-outreach
REPLICATION SETTINGS
Anchor Scheduling

Supported

 Advanced Scheduling

Supported
Table-level reset

Unsupported

 Configurable Replication Methods

Unsupported
DATA SELECTION
Table selection

Supported

 Column selection

Supported
Select all

Supported
TRANSPARENCY
Extraction Logs

Supported

 Loading Reports

Supported

Connecting Outreach

Step 1: Add Outreach as a Stitch data source

  1. In the Quota Limit field, define the percentage of your standard Outreach API quota Stitch is allowed to use. This is an optional field. Before you define the limit, refer to the Outreach API documentation to learn about your Outreach rate limit.

Step 2: Define the historical replication start date

The Sync Historical Data setting defines the starting date for your Outreach integration. This means that:

  • For tables using Key-based Incremental Replication, data equal to or newer than this date will be replicated to your destination.
  • For tables using Full Table Replication, all data - including records that are older, equal to, or newer than this date - will be replicated to your destination.

Change this setting if you want to replicate data beyond Outreach’s default setting of 1 year. For a detailed look at historical replication jobs, check out the Syncing Historical SaaS Data guide.

Step 3: Create a replication schedule

In the Replication Frequency section, you’ll create the integration’s replication schedule. An integration’s replication schedule determines how often Stitch runs a replication job, and the time that job begins.

Outreach integrations support the following replication scheduling methods:

To keep your row usage low, consider setting the integration to replicate less frequently. See the Understanding and Reducing Your Row Usage guide for tips on reducing your usage.

Step 4: Set objects to replicate

The last step is to select the tables and columns you want to replicate. Learn about the available tables for this integration.

Note: If a replication job is currently in progress, new selections won’t be used until the next job starts.

For Outreach integrations, you can select:

  1. Individual tables and columns

  2. All tables and columns

Click the tabs to view instructions for each selection method.

  1. In the integration’s Tables to Replicate tab, locate a table you want to replicate.

  2. To track a table, click the checkbox next to the table’s name. A blue checkmark means the table is set to replicate.

  3. To track a column, click the checkbox next to the column’s name. A blue checkmark means the column is set to replicate.

  4. Repeat this process for all the tables and columns you want to replicate.
  5. When finished, click the Finalize Your Selections button at the bottom of the screen to save your selections.
  1. Click into the integration from the Stitch Dashboard page.

  2. Click the Tables to Replicate tab.

  3. In the list of tables, click the box next to the Table Names column.

  4. In the menu that displays, click Track all Tables and Fields:

    The Track all Tables and Fields menu in the Tables to Replicate tab

  5. Click the Finalize Your Selections button at the bottom of the page to save your data selections.

Initial and historical replication jobs

After you finish setting up Outreach, its Sync Status may show as Pending on either the Stitch Dashboard or in the Integration Details page.

For a new integration, a Pending status indicates that Stitch is in the process of scheduling the initial replication job for the integration. This may take some time to complete.

Free historical data loads

The first seven days of replication, beginning when data is first replicated, are free. Rows replicated from the new integration during this time won’t count towards your quota. Stitch offers this as a way of testing new integrations, measuring usage, and ensuring historical data volumes don’t quickly consume your quota.

Outreach table reference

accounts

View table schema on GitHub
Replication Method :

Key-based Incremental

 Replication Key :

updatedAt
Primary Key :

id

 API endpoint :

Get accounts

The accounts table contains information about prospective clients in Outreach.

accounts table schema

id
INTEGER

The account ID

Reference:

updatedAt
DATE-TIME

The time the account was last updated.

companyType
STRING

createdAt
DATE-TIME

creatorId
INTEGER

Reference:

custom1
STRING

custom10
STRING

custom11
STRING

custom12
STRING

custom13
STRING

custom14
STRING

custom15
STRING

custom16
STRING

custom17
STRING

custom18
STRING

custom19
STRING

custom2
STRING

custom20
STRING

custom21
STRING

custom22
STRING

custom23
STRING

custom24
STRING

custom25
STRING

custom26
STRING

custom27
STRING

custom28
STRING

custom29
STRING

custom3
STRING

custom30
STRING

custom31
STRING

custom32
STRING

custom33
STRING

custom34
STRING

custom4
STRING

custom5
STRING

custom6
STRING

custom7
STRING

custom8
STRING

custom9
STRING

customId
STRING

description
STRING

domain
STRING

externalSource
STRING

followers
INTEGER

foundedAt
DATE-TIME

industry
STRING

linkedInEmployees
INTEGER

linkedInUrl
STRING

locality
STRING

name
STRING

named
BOOLEAN

naturalName
STRING

numberOfEmployees
INTEGER

ownerId
INTEGER

Reference:

tags
ARRAY

Click to expand tags

value
STRING

accounts (table), tags (attribute)

updaterId
INTEGER

Reference:

websiteUrl
STRING

calls

View table schema on GitHub
Replication Method :

Key-based Incremental

 Replication Key :

updatedAt
Primary Key :

id

 API endpoint :

Get calls

The calls table contains information about inbound and outbound calls in your Outreach call logs.

calls table schema

id
INTEGER

The call ID.

Reference:

updatedAt
DATE-TIME

The time the call was last updated.

answeredAt
DATE-TIME

callDispositionId
INTEGER

Reference:

callPurposeId
INTEGER

Reference:

completedAt
DATE-TIME

createdAt
DATE-TIME

direction
STRING

from
STRING

note
STRING

opportunityId
INTEGER

Reference:

outcome
STRING

prospectId
INTEGER

Reference:

recordingUrl
STRING

returnedAt
DATE-TIME

sequenceAction
STRING

sequenceId
INTEGER

Reference:

sequenceStateId
INTEGER

Reference:

sequenceStepId
INTEGER

Reference:

state
STRING

stateChangedAt
DATE-TIME

tags
ARRAY

Click to expand tags

value
STRING

calls (table), tags (attribute)

taskId
INTEGER

Reference:

to
STRING

userCallType
STRING

userId
INTEGER

Reference:

voicemailRecordingUrl
STRING

call_dispositions

View table schema on GitHub
Replication Method :

Key-based Incremental

 Replication Key :

updatedAt
Primary Key :

id

 API endpoint :

Get call dispositions

The call_dispositions table contains information about call dispositions from your call log in Outreach.

call_purposes

View table schema on GitHub
Replication Method :

Key-based Incremental

 Replication Key :

updatedAt
Primary Key :

id

 API endpoint :

Get call purposes

The call_purposes table contains information about the purpose of calls in your Outreach call logs.

content_categories

View table schema on GitHub
Replication Method :

Key-based Incremental

 Replication Key :

updatedAt
Primary Key :

id

 API endpoint :

Get content categories

The content_categories table contains information about your content categories in Outreach.

content_categories table schema

id
INTEGER

The content category ID.

updatedAt
DATE-TIME

The time the content category was last updated.

allowSequences
STRING

allowSnippets
STRING

allowTemplates
STRING

createdAt
DATE-TIME

creatorId
INTEGER

Reference:

name
STRING

duties

View table schema on GitHub
Replication Method :

Full Table

 Primary Key :

id
API endpoint :

Get duties

The duties table contains Outreach-suggested job roles for users.

duties table schema

id
INTEGER

The duty ID.

dutyType
STRING

symbolicName
STRING

events

View table schema on GitHub
Replication Method :

Key-based Incremental

 Replication Key :

eventAt
Primary Key :

id

 API endpoint :

Get events

The events table contains information about application events in your Outreach account.

mailboxes

View table schema on GitHub
Replication Method :

Key-based Incremental

 Replication Key :

updatedAt
Primary Key :

id

 API endpoint :

Get mailboxes

The mailboxes table contains information about your Outreach email mailbox.

mailboxes table schema

id
INTEGER

The mailbox ID.

Reference:

updatedAt
DATE-TIME

The time the mailbox was last updated.

authId
INTEGER

createdAt
DATE-TIME

creatorId
INTEGER

Reference:

editable
BOOLEAN

email
STRING

emailProvider
STRING

emailSignature
STRING

ewsEndpoint
STRING

ewsSslVerifyMode
INTEGER

exchangeVersion
STRING

imapHost
STRING

imapPort
INTEGER

imapSsl
BOOLEAN

maxEmailsPerDay
INTEGER

maxMailingsPerDay
INTEGER

maxMailingsPerWeek
INTEGER

optOutMessage
STRING

optOutSignature
STRING

prospectEmailExclusions
STRING

providerId
INTEGER

providerType
STRING

sendDisabled
BOOLEAN

sendErroredAt
DATE-TIME

sendMaxRetries
INTEGER

sendMethod
STRING

sendPeriod
INTEGER

sendRequiresSync
BOOLEAN

sendSuccessAt
DATE-TIME

sendThreshold
INTEGER

sendgridWebhookUrl
STRING

smtpHost
STRING

smtpPort
INTEGER

smtpSsl
BOOLEAN

smtpUsername
STRING

syncActiveFrequency
INTEGER

syncDisabled
BOOLEAN

syncErroredAt
DATE-TIME

syncFinishedAt
DATE-TIME

syncMethod
STRING

syncOutreachFolder
BOOLEAN

syncPassiveFrequency
INTEGER

syncSuccessAt
DATE-TIME

updaterId
INTEGER

Reference:

userId
INTEGER

Reference:

username
STRING

validateSend
BOOLEAN

validateSync
BOOLEAN

mailings

View table schema on GitHub
Replication Method :

Key-based Incremental

 Replication Key :

updatedAt
Primary Key :

id

 API endpoint :

Get mailings

The mailings table is a representation of a platform-related email.

mailings table schema

id
INTEGER

The mailing ID.

updatedAt
DATE-TIME

The time the mailing was last updated.

bodyHtml
STRING

bodyText
STRING

bouncedAt
DATE-TIME

calendarId
INTEGER

clickCount
INTEGER

clickedAt
DATE-TIME

createdAt
DATE-TIME

deliveredAt
DATE-TIME

errorBacktrace
STRING

errorReason
STRING

followUpTaskScheduledAt
DATE-TIME

followUpTaskType
STRING

mailboxAddress
STRING

mailboxId
INTEGER

Reference:

mailingType
STRING

markedAsSpamAt
DATE-TIME

messageId
STRING

notifyThreadCondition
STRING

notifyThreadScheduledAt
DATE-TIME

notifyThreadStatus
STRING

openCount
INTEGER

openedAt
DATE-TIME

opportunityId
INTEGER

Reference:

overrideSafetySettings
BOOLEAN

prospectId
INTEGER

Reference:

references
STRING

repliedAt
DATE-TIME

retryAt
DATE-TIME

retryCount
INTEGER

retryInterval
INTEGER

scheduledAt
DATE-TIME

sequenceId
INTEGER

Reference:

sequenceStateId
INTEGER

Reference:

sequenceStepId
INTEGER

Reference:

state
STRING

stateChangedAt
DATE-TIME

subject
STRING

taskId
INTEGER

Reference:

templateId
INTEGER

trackLinks
BOOLEAN

trackOpens
BOOLEAN

unsubscribedAt
DATE-TIME

opportunities

View table schema on GitHub
Replication Method :

Key-based Incremental

 Replication Key :

updatedAt
Primary Key :

id

 API endpoint :

Get pportunities

The opportunities table contains information about your pending deals and sales in Outreach.

opportunities table schema

id
INTEGER

The opportunity ID.

Reference:

updatedAt
DATE-TIME

The time the opportunity was last updated.

accountId
INTEGER

Reference:

amount
INTEGER

closeDate
DATE-TIME

createdAt
DATE-TIME

creatorId
INTEGER

Reference:

custom1
STRING

custom10
STRING

custom100
STRING

custom11
STRING

custom12
STRING

custom13
STRING

custom14
STRING

custom15
STRING

custom16
STRING

custom17
STRING

custom18
STRING

custom19
STRING

custom2
STRING

custom20
STRING

custom21
STRING

custom22
STRING

custom23
STRING

custom24
STRING

custom25
STRING

custom26
STRING

custom27
STRING

custom28
STRING

custom29
STRING

custom3
STRING

custom30
STRING

custom31
STRING

custom32
STRING

custom33
STRING

custom34
STRING

custom35
STRING

custom36
STRING

custom37
STRING

custom38
STRING

custom39
STRING

custom4
STRING

custom40
STRING

custom41
STRING

custom42
STRING

custom43
STRING

custom44
STRING

custom45
STRING

custom46
STRING

custom47
STRING

custom48
STRING

custom49
STRING

custom5
STRING

custom50
STRING

custom51
STRING

custom52
STRING

custom53
STRING

custom54
STRING

custom55
STRING

custom56
STRING

custom57
STRING

custom58
STRING

custom59
STRING

custom6
STRING

custom60
STRING

custom61
STRING

custom62
STRING

custom63
STRING

custom64
STRING

custom65
STRING

custom66
STRING

custom67
STRING

custom68
STRING

custom69
STRING

custom7
STRING

custom70
STRING

custom71
STRING

custom72
STRING

custom73
STRING

custom74
STRING

custom75
STRING

custom76
STRING

custom77
STRING

custom78
STRING

custom79
STRING

custom8
STRING

custom80
STRING

custom81
STRING

custom82
STRING

custom83
STRING

custom84
STRING

custom85
STRING

custom86
STRING

custom87
STRING

custom88
STRING

custom89
STRING

custom9
STRING

custom90
STRING

custom91
STRING

custom92
STRING

custom93
STRING

custom94
STRING

custom95
STRING

custom96
STRING

custom97
STRING

custom98
STRING

custom99
STRING

description
STRING

externalCreatedAt
DATE-TIME

name
STRING

nextStep
STRING

opportunityStageId
INTEGER

Reference:

opportunityType
STRING

ownerId
INTEGER

Reference:

probability
INTEGER

prospectingRepId
STRING

tags
ARRAY

Click to expand tags

value
STRING

opportunities (table), tags (attribute)

touchedAt
DATE-TIME

personas

View table schema on GitHub
Replication Method :

Key-based Incremental

 Replication Key :

updatedAt
Primary Key :

id

 API endpoint :

Get personas

The personas table contains information about descriptions and types of people in Outreach.

personas table schema

id
INTEGER

The persona ID.

Reference:

updatedAt
DATE-TIME

The time the persona was last updated.

createdAt
DATE-TIME

description
STRING

name
STRING

prospects

View table schema on GitHub
Replication Method :

Key-based Incremental

 Replication Key :

updatedAt
Primary Key :

id

 API endpoint :

Prospect

The prospects table contains information about your prospects.

prospects table schema

id
INTEGER

The prospect ID.

Reference:

updatedAt
DATE-TIME

The time the prospect was last updated.

accountId
INTEGER

Reference:

addedAt
DATE-TIME

addressCity
STRING

addressCountry
STRING

addressState
STRING

addressStreet
STRING

addressStreet2
STRING

addressZip
STRING

angelListUrl
STRING

availableAt
DATE-TIME

callOptedOut
BOOLEAN

callsOptStatus
STRING

callsOptedAt
DATE-TIME

campaignName
STRING

clickCount
INTEGER

contactHistogram
ARRAY

Click to expand contactHistogram

value
ARRAY

Click to expand value

value
INTEGER

prospects (table), value (attribute)
prospects (table), contactHistogram (attribute)

createdAt
DATE-TIME

creatorId
INTEGER

Reference:

custom1
STRING

custom10
STRING

custom11
STRING

custom12
STRING

custom13
STRING

custom14
STRING

custom15
STRING

custom16
STRING

custom17
STRING

custom18
STRING

custom19
STRING

custom2
STRING

custom20
STRING

custom21
STRING

custom22
STRING

custom23
STRING

custom24
STRING

custom25
STRING

custom26
STRING

custom27
STRING

custom28
STRING

custom29
STRING

custom3
STRING

custom30
STRING

custom31
STRING

custom32
STRING

custom33
STRING

custom34
STRING

custom35
STRING

custom36
STRING

custom37
STRING

custom38
STRING

custom39
STRING

custom4
STRING

custom40
STRING

custom41
STRING

custom42
STRING

custom43
STRING

custom44
STRING

custom45
STRING

custom46
STRING

custom47
STRING

custom48
STRING

custom49
STRING

custom5
STRING

custom50
STRING

custom51
STRING

custom52
STRING

custom53
STRING

custom54
STRING

custom55
STRING

custom6
STRING

custom7
STRING

custom8
STRING

custom9
STRING

dateOfBirth
DATE-TIME

defaultPluginMappingId
INTEGER

degree
STRING

emailOptedOut
BOOLEAN

emails
ARRAY

Click to expand emails

value
STRING

prospects (table), emails (attribute)

emailsOptStatus
STRING

emailsOptedAt
DATE-TIME

engagedAt
DATE-TIME

engagedScore
NUMBER

eventName
STRING

externalId
STRING

externalOwner
STRING

externalSource
STRING

facebookUrl
STRING

firstName
STRING

gender
STRING

githubUrl
STRING

githubUsername
STRING

googlePlusUrl
STRING

graduationDate
DATE-TIME

homePhones
STRING

jobStartDate
DATE-TIME

lastName
STRING

linkedInConnections
INTEGER

linkedInId
STRING

linkedInSlug
STRING

linkedInUrl
STRING

middleName
STRING

mobilePhones
ARRAY

Click to expand mobilePhones

value
STRING

prospects (table), mobilePhones (attribute)

name
STRING

nickname
STRING

occupation
STRING

openCount
INTEGER

optedOut
BOOLEAN

optedOutAt
DATE-TIME

otherPhones
ARRAY

Click to expand otherPhones

value
STRING

prospects (table), otherPhones (attribute)

ownerId
INTEGER

Reference:

personaId
INTEGER

Reference:

personalNote1
STRING

personalNote2
STRING

preferredContact
STRING

quoraUrl
STRING

region
STRING

replyCount
INTEGER

school
STRING

score
INTEGER

smsOptStatus
STRING

smsOptedAt
DATE-TIME

smsOptedOut
BOOLEAN

source
STRING

specialties
STRING

stackOverflowId
STRING

stackOverflowUrl
STRING

stageId
INTEGER

Reference:

tags
ARRAY

Click to expand tags

value
STRING

prospects (table), tags (attribute)

timeZone
STRING

timeZoneIana
STRING

timeZoneInferred
STRING

title
STRING

touchedAt
DATE-TIME

twitterUrl
STRING

twitterUsername
STRING

updaterId
INTEGER

Reference:

voipPhones
ARRAY

Click to expand voipPhones

value
STRING

prospects (table), voipPhones (attribute)

websiteUrl1
STRING

websiteUrl2
STRING

websiteUrl3
STRING

workPhones
ARRAY

Click to expand workPhones

value
STRING

prospects (table), workPhones (attribute)

sequences

View table schema on GitHub
Replication Method :

Key-based Incremental

 Replication Key :

updatedAt
Primary Key :

id

 API endpoint :

Get sequences

The sequences table contains info about sequences.

sequences table schema

id
INTEGER

The sequence ID.

Reference:

updatedAt
DATE-TIME

The time the sequence was last updated.

automationPercentage
NUMBER

bounceCount
INTEGER

clickCount
INTEGER

createdAt
DATE-TIME

creatorId
INTEGER

Reference:

deliverCount
INTEGER

description
STRING

durationInDays
INTEGER

enabled
BOOLEAN

enabledAt
DATE-TIME

failureCount
INTEGER

finishOnReply
BOOLEAN

lastUsedAt
DATE-TIME

locked
BOOLEAN

lockedAt
DATE-TIME

maxActivations
INTEGER

name
STRING

negativeReplyCount
INTEGER

neutralReplyCount
INTEGER

numContactedProspects
INTEGER

numRepliedProspects
INTEGER

openCount
INTEGER

optOutCount
INTEGER

ownerId
INTEGER

Reference:

positiveReplyCount
INTEGER

primaryReplyAction
STRING

primaryReplyPauseDuration
INTEGER

replyCount
INTEGER

scheduleCount
INTEGER

scheduleIntervalType
STRING

secondaryReplyAction
STRING

secondaryReplyPauseDuration
INTEGER

sequenceStepCount
INTEGER

sequenceType
STRING

shareType
STRING

tags
STRING

throttleCapacity
INTEGER

throttleMaxAddsPerDay
INTEGER

throttlePaused
BOOLEAN

throttlePausedAt
DATE-TIME

transactional
BOOLEAN

updaterId
INTEGER

Reference:

sequence_states

View table schema on GitHub
Replication Method :

Key-based Incremental

 Replication Key :

updatedAt
Primary Key :

id

 API endpoint :

Get sequence steps

The sequence_states table contains info about currently sequenced prospects.

sequence_states table schema

id
INTEGER

The sequence state ID.

Reference:

updatedAt
DATE-TIME

The time the sequence state was last updated.

accountId
INTEGER

Reference:

activeAt
DATE-TIME

bounceCount
INTEGER

callCompletedAt
DATE-TIME

clickCount
INTEGER

createdAt
DATE-TIME

creatorId
INTEGER

Reference:

deliverCount
INTEGER

errorReason
STRING

failureCount
INTEGER

naturalReplyCount
INTEGER

negativeReplyCount
INTEGER

openCount
INTEGER

optOutCount
INTEGER

pauseReason
STRING

positiveReplyCount
INTEGER

prospectId
INTEGER

Reference:

repliedAt
DATE-TIME

replyCount
INTEGER

scheduleCount
INTEGER

sequenceId
INTEGER

Reference:

state
STRING

stateChangedAt
DATE-TIME

sequence_steps

View table schema on GitHub
Replication Method :

Key-based Incremental

 Replication Key :

updatedAt
Primary Key :

id

 API endpoint :

Get sequence steps

The sequence_steps table contains info about individual steps within automated sequences.

sequence_steps table schema

id
INTEGER

The sequence step ID.

Reference:

updatedAt
DATE-TIME

The time the sequence step was last updated.

bounceCount
INTEGER

clickCount
INTEGER

createdAt
DATE-TIME

creatorId
INTEGER

Reference:

date
DATE

deliverCount
INTEGER

displayName
STRING

failureCount
INTEGER

interval
INTEGER

negativeReplyCount
INTEGER

neutralReplyCount
INTEGER

openCount
INTEGER

optOutCount
INTEGER

order
INTEGER

positiveReplyCount
INTEGER

replyCount
INTEGER

scheduleCount
INTEGER

sequenceId
INTEGER

Reference:

stepType
STRING

taskAutoskipDelay
INTEGER

taskNote
STRING

updaterId
INTEGER

Reference: