Outreach Collect Slice

Overview

Outreach is a sales engagement software/platform that provides lead generators, sales representatives, and sales managers an account-based sales communication solution in order for them to secure prospects and identify and increase sales opportunities.

This datasource slice collects data from Outreach and writes it to S3 and Redshift.

Steps to add this slice to your installation

The steps to launch your slice are:

  1. Generate Outreach keys
  2. Specify the slice config
  3. Add the Outreach slice

1. Generate Outreach keys

Setup requirements

Before getting started please make sure to have the following information:

  • Access to an active Outreach account

Prerequisites

Please refer to the documentation at https://api.outreach.io/api/v2/docs#api-reference to understand and obtain the tokens/urls needed for the slice to pull data from Outreach. You will need to obtain the clientId, clientSecret, and refreshToken.

2. Specify the slice config

To get a template for the Outreach slice configuration save the output of the describe --input-parameters command as follows:

datacoral collect describe --slice-type outreach \
--input-parameters > outreach_parameters_file.json

Necessary input parameters:

  • clientId - The Consumer Key from the connected app definition.
  • clientSecret - The Consumer Secret from the connected app definition.
  • refreshToken - The refresh token the client application already received.

Optional input parameters:

for datasource:

for loadunit:

  • schedule - cron format. You can define a different schedule for the loadunit from the global schedule set above.

  • skipErrors - boolean parameter, if set to true all errors will be silently skipped

    Example templates:

{
"clientId": "consumer_key",
"clientSecret": "consumer_key",
"refreshToken": "refresh_token"
}

3. Add the Slice

datacoral collect add --slice-type outreach --slice-name <slice-name> --parameters-file <params-file>
  • slice-name Name of your slice. A schema with your slice-name is automatically created in your warehouse
  • params-file File path to your input parameters file. Ex. outreach_parameters_file.json

Supported load units

  • accounts
  • calls
  • mailings
  • personas
  • phone_numbers
  • prospects
  • sequence_states
  • sequence_steps
  • sequences
  • stages
  • tasks
  • user_duties
  • users

Slice output

Output of this slice is stored in S3 and Redshift.

AWS S3 Data stored in AWS S3 is partitioned by date and time in the following bucket s3//:customer_installation.datacoral/<sliceName>

AWS Redshift: Schema - schema name will be same as a slice-name. Tables produced by the slice are:

- schema.accounts
- schema.calls
- schema.mailings
- schema.personas
- schema.phone_numbers
- schema.prospects
- schema.sequence_states
- schema.sequence_steps
- schema.sequences
- schema.stages
- schema.tasks
- schema.user_duties
- schema.users

Questions? Interested?

If you have questions or feedback, feel free to reach out at hello@datacoral.co or Request a demo