ConductorOne provides identity governance and just-in-time provisioning for Outreach. Integrate your Outreach instance with ConductorOne to run user access reviews (UARs) and enable just-in-time access requests.
In Outreach, navigate to Admin Home > Installed apps.
2
Click Create new app.
3
Click Create app.
4
Give the new app a name, such as “ConductorOne”, then click Create.
5
The new app’s details view opens. Click Feature selection.
6
Select Outreach API (OAuth) and click Add feature.
7
Carefully copy and save the OAuth Application ID and Application Secret.
8
Enter a callback URL for your app.
9
Select the relevant scopes for the app:To sync access data (READ):
User: Read
Teams: Read
Profiles: Read
To sync access data and provision accounts and entitlements (READ/WRITE):
User: All
Teams: All
Profiles: All
Reauthorize the connector if you change which permissions are granted to the OAuth app.If, for example, you previously set up the Outreach connector with READ permissions, then updated the Outreach OAuth app to grant READ/WRITE permissions, you must re-authorize the OAuth app for the changes to take effect.
10
Save the app. If desired, create a release.
That’s it! Next, move on to the connector configuration instructions.
The Connector Administrator or Super Administrator role in ConductorOne
Access to the set of Outreach credentials generated by following the instructions above
Cloud-hosted
Self-hosted
Follow these instructions to use a built-in, no-code connector hosted by ConductorOne.
1
In ConductorOne, navigate to Admin > Connectors and click Add connector.
2
Search for Outreach and click Add.
3
Choose how to set up the new Outreach connector:
Add the connector to a currently unmanaged app (select from the list of apps that were discovered in your identity, SSO, or federation provider that aren’t yet managed with ConductorOne)
Add the connector to a managed app (select from the list of existing managed apps)
Create a new managed app
4
Set the owner for this connector. You can manage the connector yourself, or choose someone else from the list of ConductorOne users. Setting multiple owners is allowed.If you choose someone else, ConductorOne will notify the new connector owner by email that their help is needed to complete the setup process.
5
Click Next.
6
Find the Settings area of the page and click Edit.
7
Paste the the OAuth application ID and application secret into the Client ID and Client secret fields.
8
Click Login with OAuth.
9
Log into Outreach and authorize ConductorOne.After authorizing, you’ll be redirected back to the ConductorOne integrations page, where an “Authorized as” message is now printed.
Remember: Reauthorize the connector if you change the permissions that are granted to the Outreach OAuth app.
10
Click Save.
11
The connector’s label changes to Syncing, followed by Connected. You can view the logs to ensure that information is syncing.
That’s it! Your Outreach connector is now pulling access data into ConductorOne.
Follow these instructions to use the Outreach connector, hosted and run in your own environment.When running in service mode on Kubernetes, a self-hosted connector maintains an ongoing connection with ConductorOne, automatically syncing and uploading data at regular intervals. This data is immediately available in the ConductorOne UI for access reviews and access requests.
In ConductorOne, navigate to Connectors > Add connector.
2
Search for Baton and click Add.
3
Choose how to set up the new Outreach connector:
Add the connector to a currently unmanaged app (select from the list of apps that were discovered in your identity, SSO, or federation provider that aren’t yet managed with ConductorOne)
Add the connector to a managed app (select from the list of existing managed apps)
Create a new managed app
4
Set the owner for this connector. You can manage the connector yourself, or choose someone else from the list of ConductorOne users. Setting multiple owners is allowed.If you choose someone else, ConductorOne will notify the new connector owner by email that their help is needed to complete the setup process.
5
Click Next.
6
In the Settings area of the page, click Edit.
7
Click Rotate to generate a new Client ID and Secret.Carefully copy and save these credentials. We’ll use them in Step 2.
Create a namespace in which to run ConductorOne connectors (if desired), then apply the secret config and deployment config files.
2
Check that the connector data uploaded correctly. In ConductorOne, click Applications. On the Managed apps tab, locate and click the name of the application you added the Outreach connector to. Outreach data should be found on the Entitlements and Accounts tabs.
That’s it! Your Outreach connector is now pulling access data into ConductorOne.
