Set up Whimsical connector

Capabilities

Resource	Sync	Provision
Users
Roles

The Whimsical connector syncs users and roles via the SCIM 2.0 API. This connector supports the following provisioning operations:

User account provisioning: Create new users via SCIM POST
User account deletion: Remove users from the workspace via SCIM DELETE
Role provisioning: Assign and revoke Editor or Viewer roles via SCIM PATCH (grant/revoke)

Requirements

A Whimsical Enterprise plan with SAML SSO enabled
A SCIM OAuth token from workspace settings

Gather Whimsical credentials

Obtain a SCIM OAuth token

Click on the workspace name in the top left corner.

Navigate to Workspace settings.

Ensure SAML SSO is enabled and correctly configured.

Enable SCIM provisioning.

Click Reveal to retrieve the OAuth token.

Copy the token immediately.

See the Whimsical SCIM documentation for detailed instructions. Done. Next, move on to the connector configuration instructions.

Configure the Whimsical connector

To complete this task, you’ll need:

The Connector Administrator or Super Administrator role in C1
Your Whimsical SCIM OAuth token generated above

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 Whimsical 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.

Paste the SCIM OAuth Token.

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 Whimsical connector is now pulling access data into C1.

Follow these instructions to use the Whimsical 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. This data is immediately available in the C1 UI for access reviews and access requests.

Resources

GitHub repository: Access the source code, report issues, or contribute to the project.

Step 1: Set up a new Whimsical 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.

Find the Settings area of the page and 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

Secrets configuration

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

  # Whimsical config
  BATON_WHIMSICAL_TOKEN: <Whimsical Token>

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

Deployment configuration

# baton-whimsical.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
  name: baton-whimsical
  labels:
    app: baton-whimsical
spec:
  selector:
    matchLabels:
      app: baton-whimsical
  template:
    metadata:
      labels:
        app: baton-whimsical
        baton: "true"
        baton-app: whimsical
    spec:
      containers:
        - name: baton-whimsical
          image: public.ecr.aws/conductorone/baton-whimsical:latest
          imagePullPolicy: IfNotPresent
          env:
            - name: BATON_HOST_ID
              value: baton-whimsical
          envFrom:
            - secretRef:
                name: baton-whimsical-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 Apps. On the Managed apps tab, locate and click the name of the application you added the whimsical connector to. whimsical data should be found on the Entitlements and Accounts tabs.

Done. Your Whimsical 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 Whimsical connector

Capabilities

Requirements

Gather Whimsical credentials

Obtain a SCIM OAuth token

Configure the Whimsical connector

Resources

Step 1: Set up a new Whimsical connector

Step 2: Create Kubernetes configuration files

Secrets configuration

Deployment configuration

Step 3: Deploy the connector

​Capabilities

​Requirements

​Gather Whimsical credentials

​Obtain a SCIM OAuth token

​Configure the Whimsical connector

​Resources

​Step 1: Set up a new Whimsical connector

​Step 2: Create Kubernetes configuration files

​Secrets configuration

​Deployment configuration

​Step 3: Deploy the connector

Capabilities

Requirements

Gather Whimsical credentials

Obtain a SCIM OAuth token

Configure the Whimsical connector

Resources

Step 1: Set up a new Whimsical connector

Step 2: Create Kubernetes configuration files

Secrets configuration

Deployment configuration

Step 3: Deploy the connector