Set up an Outreach connector

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.

Capabilities

Resource	Sync	Provision
Accounts	✅	✅
Profiles	✅	✅
Teams	✅	✅

The Outreach connector supports automatic account provisioning and deprovisioning.

Gather Outreach credentials

Configuring the connector requires you to pass in credentials generated in Outreach. Gather these credentials before you move on.

A user who is an admin in Outreach must perform this task.

Create an OAuth application

In Outreach, navigate to Admin Home > Installed apps.
Click Create new app.
Click Create app.
Give the new app a name, such as “ConductorOne”, then click Create.
The new app’s details view opens. Click Feature selection.
Select Outreach API (OAuth) and click Add feature.
Carefully copy and save the OAuth Application ID and Application Secret.
Enter a callback URL for your app.
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
Save the app. If desired, create a release.

That’s it! Next, move on to the connector configuration instructions.

Configure the Outreach connector

To complete this task, you’ll need:
The Connector Administrator or Super Administrator role in ConductorOne
Access to the set of Outreach credentials generated by following the instructions above

Follow these instructions to use a built-in, no-code connector hosted by ConductorOne.

In ConductorOne, navigate to Admin > Connectors and click Add connector.
Search for Outreach and click Add.
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
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.
Click Next.
Find the Settings area of the page and click Edit.
Paste the the OAuth application ID and application secret into the Client ID and Client secret fields.
Click Login with OAuth.
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.
Click Save.
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.

Step 1: Set up a new Outreach connector

In ConductorOne, navigate to Connectors > Add connector.
Search for Baton and click Add.
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
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.
Click Next.
In the Settings area of the page, click Edit.
Click Rotate to generate a new Client ID and Secret.
Carefully copy and save these credentials. We’ll use them in Step 2.

Step 2: Create Kubernetes configuration files

Create two Kubernetes manifest files for your Outreach connector deployment:

Secrets configuration

# baton-outreach-secrets.yaml
apiVersion: v1
kind: Secret
metadata:
  name: baton-outreach-secrets
type: Opaque
stringData:
  # ConductorOne credentials
  BATON_CLIENT_ID: <ConductorOne client ID>
  BATON_CLIENT_SECRET: <ConductorOne client secret>
  
  # Outreach credentials
  BATON_OUTREACH_CLIENT_ID: <Outreach app ID>
  BATON_OUTREACH_CLIENT_ID: <Outreach app secret>

  # Optional: include if you want ConductorOne to provision access using this connector
  BATON_PROVISIONING: true

See the connector’s README or run --help to see all available configuration flags and environment variables.

Deployment configuration

# baton-outreach.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
  name: baton-outreach
  labels:
    app: baton-outreach
spec:
  selector:
    matchLabels:
      app: baton-outreach
  template:
    metadata:
      labels:
        app: baton-outreach
        baton: true
        baton-app: outreach
    spec:
      containers:
      - name: baton-outreach
        image: ghcr.io/conductorone/baton-outreach:latest
        imagePullPolicy: IfNotPresent
        envFrom:
        - secretRef:
            name: baton-outreach-secrets

Step 3: Deploy the connector

Create a namespace in which to run ConductorOne connectors (if desired), then apply the secret config and deployment config files.
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.