Set up Monday.com connector

Capabilities
Gather Monday.com credentials
Configure the Monday.com connector

Capabilities

Resource	Sync	Provision
Account
Board
Team
Workspace

Additional functionality: Supports automatic account provisioning
This connector does not support account deprovisioning. You must deprovision accounts directly in Monday.com.

Gather Monday.com credentials

Configuring the connector requires you to pass in information from Monday.com. Gather these configuration details before you move on. Here’s the information you’ll need:

An API key generated by a user with the Admin role in Monday.com

See the Monday.com docs for information on how to acquire credentials: View the documentation That’s it! Next, move on to the connector configuration instructions.

Configure the Monday.com connector

To complete this task, you’ll need:

The Connector Administrator or Super Administrator role in C1
Access to the set of Monday.com configuration information gathered by following the instructions above

Cloud-hosted
Self-hosted

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

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

Search for Monday.com and click Add.

Choose how to set up the new Monday.com 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 C1)
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 C1 users. Setting multiple owners is allowed.If you choose someone else, C1 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.

Enter the configuration information from the previous section.

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

Follow these instructions to use the Monday.com 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

Contact C1’s support team to download the latest version of the connector.

Step 1: Set up a new Monday.com connector

In C1, navigate to Integrations > Connectors > Add connector.

Search for Baton and click Add.

Choose how to set up the new Monday.com 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 C1)
Add the connector to a managed app (select from the list of existing managed apps)
Create a new managed app

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 Monday.com connector deployment:

Secrets configuration

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

  # Monday.com config
  BATON_MONDAY_API_KEY: <API Key for Monday>

  # Optional: include if you want C1 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-monday.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
  name: baton-monday
  labels:
    app: baton-monday
spec:
  selector:
    matchLabels:
      app: baton-monday
  template:
    metadata:
      labels:
        app: baton-monday
        baton: true
        baton-app: monday
    spec:
      containers:
      - name: baton-monday
        image: ghcr.io/conductorone/baton-monday:latest
        imagePullPolicy: IfNotPresent
        env:
        - name: BATON_HOST_ID
          value: baton-monday
        envFrom:
        - secretRef:
            name: baton-monday-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 monday connector to. monday data should be found on the Entitlements and Accounts tabs.

That’s it! Your Monday.com connector is now pulling access data into C1.

Set up Mode connector

Set up a MongoDB Atlas connector

⌘I

Welcome

Manage connectors

Deploy connectors

Upload connector data

Configurable connectors

Pre-built connectors

Set up Monday.com connector

Capabilities

Gather Monday.com credentials

Configure the Monday.com connector

Resources

Step 1: Set up a new Monday.com connector

Step 2: Create Kubernetes configuration files

Secrets configuration

Deployment configuration

Step 3: Deploy the connector

Welcome

Manage connectors

Deploy connectors

Upload connector data

Configurable connectors

Pre-built connectors

​Capabilities

​Gather Monday.com credentials

​Configure the Monday.com connector

​Resources

​Step 1: Set up a new Monday.com connector

​Step 2: Create Kubernetes configuration files

​Secrets configuration

​Deployment configuration

​Step 3: Deploy the connector

Capabilities

Gather Monday.com credentials

Configure the Monday.com connector

Resources

Step 1: Set up a new Monday.com connector

Step 2: Create Kubernetes configuration files

Secrets configuration

Deployment configuration

Step 3: Deploy the connector