This article covers the technical details of how integration works between Koncert and Outreach.
OAuth Connection scopes
Koncert integrates with Outreach using OAuth 2.0, allowing secure interaction between the platforms. Each connection uses an Access Token that allows Koncert to communicate with the Outreach API.
Each user must individually authorize and connect their Outreach account to Koncert.
Scopes
Koncert requires the following scopes to function effectively.
| Object/Scope | Description |
| accounts | Access your accounts' information |
| calls | Access your calls' information |
| callDispositions | Access your call dispositions' information |
| callPurposes | Access your call purposes' information |
| emailAddresses | Access your email addresses' information |
| mailings | Access your mailings' information |
| phoneNumbers | Access your phone numbers' information |
| profiles | Access your profiles' information |
| prospects | Access your prospects' information |
| roles | Access your roles' information |
| sequences | Access your sequences' information |
| sequenceStates | Access your sequence states' information |
| sequenceSteps | Access your sequence steps' information |
| stages | Access your stages' information |
| tasks | Access your tasks' information |
| teams | Access your teams' information |
| users | Access your users' information |
Koncert manages access token validity by utilizing refresh tokens. When an access token expires, Koncert uses the refresh token to validate and generate a new access token, ensuring uninterrupted access to the Outreach API.
For more details and documentation on the Outreach API: https://developers.outreach.io/api/
How does the Integration Work?
Koncert utilizes a real-time access model to ensure data from Outreach is always up-to-date. This model is employed to load the call tasks and log calls, allowing the system to retrieve and interact with Outreach data in real-time, ensuring seamless synchronization.
The diagram below illustrates how Koncert leverages this real-time model to load tasks and log calls.
Data Permissions, Objects & Retention
Permissions Model
Koncert uses the standard Outreach data models and inherits access roles from Outreach. Custom fields will be retrieved based on permissions defined in Outreach; Koncert users will only be able to see fields that they are able to see on Outreach itself.
List of Outreach Objects
Koncert interacts with the following objects in Outreach.
- Prospect
- Account
- Task
- Sequence
- SequenceSteps
- SequenceStates
- Calls
- Mailings
- CallDispostion
- CallPurpose
- EmailAddresses
Koncert also supports custom objects that are linked with Contact/Lead at this time.
Data Retention
Koncert stores minimal data needed for dialing purposes such as Account Name, Contact Name, Title, and Phone Number. There can be additional fields mapped and stored from Outreach. After we dial, we store the call details of those records for a period of 180 days, and will be purged. Also, the user has the ability to delete a specific prospect information from the Koncert platform.
Rate Limiting & Throttling
Koncert uses the API limit available for that user in Outreach. If the API limit is exceeded, the Koncert system alerts the user with a message and stops syncing.
Please refer to this link for more information about getting started with Koncert.
https://kb.koncert.com/hc/en-us/articles/25237134491543-Getting-Started-with-Outreach
Please contact Koncert Support for any questions at support@koncert.com or 603-952-2505.
NOTE: The information provided here is for informational purposes only and should not be considered as a legal advice. Please consult your legal counsel regarding compliance with relevant laws.