Overview
OAuth Connection
How the Integration Works
Data Permissions, Objects & Retention
OAuth Connection
Nooks uses OAuth to connect a Nooks account with an associated Outreach account. For each connection, the Nooks service receives an API key that is used to make calls to the Outreach API.
Each rep must connect their Nooks account to Outreach individually.
Scopes
Nooks uses the following scopes.
users.all
calls.all
accounts.all
webhooks.all
teams.all
prospects.all
mailboxes.all
phoneNumbers.all
callDispositions.all
events.all
tasks.all
mailings.all
sequences.all
sequenceTemplates.all
sequenceSteps.all
sequenceStates.all
Occasionally, API keys will expire and Nooks may prompt the user to re-connect.
For more details and documentation on the Outreach API: https://developers.outreach.io/api/
How the Integration Works
Just-in-time Access
In order to ensure data is up-to-date from Outreach, Nooks adopts a “just-in-time” access model to Outreach data.
The below diagram shows how Nooks uses this access model to load tasks and log calls.
Data Objects & Retention
List of Outreach APIs / Objects
Nooks interacts with the following standard objects in Outreach. All data objects pulled from Nooks are designated with the “Restricted classification” and inherits access based on the according internal security model within Outreach.
Data Element | Description |
.prospect | Prospect details |
.account | Account details |
.sequence | Sequence names and ids |
.disposition | Dispositions |
.call | Call objects |
.task | Task ids |
Call Logging
When logging a call, the following properties are written back to Outreach:
Data Element | Type |
prospect_id | number |
disposition_id | number |
notes | text |
task_id | number |
duration | number |
time | date |
to | number |
Data Retention
Nooks generally uses a Just-In-Time model for interactions with Outreach. As a result, no data from Outreach is stored on Nooks servers with one exceptions.
Nooks maintains a list of Outreach Users to support User Mapping settings.
These are not Contacts or Accounts, only Users of the integrated team.
Three fields are stored: UserId, Email and Name.