Set up a ChartHop connector

Capabilities

The ChartHop connector syncs the following resources:

Resource	Sync	Provision
Groups
Persons

The Persons resource represents ChartHop Persons (HR employees) sourced from /v2/org/{orgId}/person. The Groups resource represents ChartHop groups (departments, teams, locations, and other group-type classifications). Group membership is sourced directly from ChartHop’s calculated groupIds on the person record via /v2/org/{orgId}/person/{personId}?fields=groupIds. This connector intentionally does not emit ChartHop platform login users, roles, or “who can administer the HR system” data. That is IGA data about the HR application itself and is out of scope; if needed, it belongs in a separate connector focused on HR-system administration.

Gather ChartHop credentials

To configure the ChartHop connector, you need administrator permissions in ChartHop.

Navigate to the ChartHop admin console or API settings.

Create API credentials for C1:

Create a new API key or token named C1
Grant the required scopes or permissions
Copy the credentials and save them securely

Configure the ChartHop connector

Cloud-hosted
Self-hosted

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

In C1, navigate to Apps > Connectors and click Add connector.

Search for ChartHop and click Add.

Choose where to add the connector: Create a new app, or Add to an existing app (then select the app).If you’re creating a new app, choose whether to link it to an application discovered from your identity provider: select Yes and pick the IdP application, or No to continue with just the connector.

Set the connector’s Name and, optionally, a Description.

Click the pencil icon next to Owners to choose who can configure and manage this connector.

Click Add. The connector is created and its configuration page opens.

Find the Settings area of the page and click Edit.

Enter the required configuration:

API Token: Your ChartHop API token
Organization ID: Your ChartHop organization ID

Click Save.

The connector’s label changes to Syncing, followed by Connected. You can view the logs to ensure that information is syncing.

Done. Your ChartHop connector is now pulling access data into C1.

Follow these instructions to use the ChartHop connector, hosted and run in your own environment.When running in service mode on Kubernetes, a self-hosted connector maintains an ongoing connection with C1, automatically syncing and uploading data at regular intervals.

Step 1: Set up a new ChartHop connector

In C1, navigate to Apps > Connectors and click Add connector.

Search for Baton and click Add.

Set the connector’s Name and, optionally, a Description.

Click the pencil icon next to Owners to choose who can configure and manage this connector.

Click Add. The connector is created and its configuration page opens.

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.

Step 2: Create Kubernetes configuration files

Create two Kubernetes manifest files for your ChartHop connector deployment:

Secrets configuration

# baton-charthop-secrets.yaml
apiVersion: v1
kind: Secret
metadata:
  name: baton-charthop-secrets
type: Opaque
stringData:
  # C1 credentials
  BATON_CLIENT_ID: <C1 client ID>
  BATON_CLIENT_SECRET: <C1 client secret>

  # ChartHop credentials
  BATON_API_TOKEN: <ChartHop API token>
  BATON_ORG_ID: <ChartHop organization ID>

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

Deployment configuration

# baton-charthop.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
  name: baton-charthop
  labels:
    app: baton-charthop
spec:
  selector:
    matchLabels:
      app: baton-charthop
  template:
    metadata:
      labels:
        app: baton-charthop
        baton: "true"
        baton-app: charthop
    spec:
      containers:
      - name: baton-charthop
        image: public.ecr.aws/conductorone/baton-charthop:latest
        imagePullPolicy: IfNotPresent
        env:
        - name: BATON_HOST_ID
          value: baton-charthop
        envFrom:
        - secretRef:
            name: baton-charthop-secrets

Step 3: Deploy the connector

Create a namespace in which to run C1 connectors (if desired), then apply the secret config and deployment config files.

Check that the connector data uploaded correctly. In C1, click Applications. On the Managed apps tab, locate and click the name of the application you added the ChartHop connector to. ChartHop data should be found on the Entitlements and Accounts tabs.

Done. Your ChartHop connector is now pulling access data into C1.

All versions of this connector are available at dist.conductorone.com.

Welcome

Manage connectors

Deploy connectors

Upload connector data

Configurable connectors

Pre-built connectors

Set up a ChartHop connector

Capabilities

Gather ChartHop credentials

Configure the ChartHop connector

Step 1: Set up a new ChartHop connector

Step 2: Create Kubernetes configuration files

Secrets configuration

Deployment configuration

Step 3: Deploy the connector

​Capabilities

​Gather ChartHop credentials

​Configure the ChartHop connector

​Step 1: Set up a new ChartHop connector

​Step 2: Create Kubernetes configuration files

​Secrets configuration

​Deployment configuration

​Step 3: Deploy the connector

Capabilities

Gather ChartHop credentials

Configure the ChartHop connector

Step 1: Set up a new ChartHop connector

Step 2: Create Kubernetes configuration files

Secrets configuration

Deployment configuration

Step 3: Deploy the connector