Set up Monday.com connector

Capabilities

Resource	Sync	Provision	Delete
Account
Role
Team
Board
Workspace

Additional functionality: Supports automatic account provisioning
Supports account lifecycle actions (enable and disable user)
Supports resource create for teams, boards, and workspaces
Monday.com does not expose a hard delete for human users. Use the Disable User connector action to deactivate accounts. Board and workspace owner/subscriber entitlements are synced for access reviews but are not provisioned by this connector. Boards sync nested under their workspace when workspace_id is present; otherwise they sync at the top level. Board and workspace delete are not implemented by this connector.

Connector actions

Action	Description
Enable User	Reactivates a previously deactivated user via the `activate_users` GraphQL mutation
Disable User	Deactivates (soft-disables) a user via the `deactivate_users` GraphQL mutation

User states and provisioning

Monday.com users keep the same ID from invitation through deactivation. The connector maps each lifecycle state to a C1 account status and blocks unsupported operations with clear errors. How users appear in C1 after sync:

User state	C1 account status	Included in sync
Pending invite (not yet accepted)	Disabled	Yes
Active member	Enabled	Yes
Deactivated (soft-disabled)	Disabled	Yes

What each state supports:

Operation	Pending invite	Active	Deactivated
Team member grant	Supported	Supported	Not supported — run Enable User first
Team member revoke	Supported	Supported	Supported
Role grant / revoke	Supported	Supported	Supported
Enable User action	Not supported — invitation not accepted yet	Idempotent success if already active	Supported
Disable User action	Not supported — invitation not accepted yet	Supported	Idempotent success if already disabled

Pending invites can still receive team and role entitlements because Monday.com accepts those changes before the user accepts the invitation. Team grants on deactivated users are blocked before the API call; role grants on deactivated users remain supported because Monday.com accepts them.

Provisioned entitlements

Resource	Entitlement	Operation
Role	Assigned	Grant or revoke a user’s account-level base role (Admin, Member, View Only, Guest)
Team	Team Member	Add or remove a user from a team

Resource create

Resource	Operation
Team	Create a team (`create_team`) or delete a team (`delete_team`)
Board	Create a board in a workspace (`create_board`)
Workspace	Create a workspace (`create_workspace`)

Gather Monday.com credentials

To generate credentials, you’ll need a user with the Admin role in Monday.com.

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 from Developers > My Access Tokens in Monday.com

See the Monday.com docs for information on how to acquire credentials: View the documentation Done. 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 Apps > Connectors and click Add connector.

Search for Monday.com 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 configuration information from the previous section.

monday-api-key (required): API Key for Monday

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 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 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. 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.com connector to. Monday.com data should be found on the Entitlements and Accounts tabs.

Done. Your Monday.com connector is now pulling access data into C1.

Welcome

Manage connectors

Deploy connectors

Upload connector data

Configurable connectors

Pre-built connectors

Set up Monday.com connector

Capabilities

Connector actions

User states and provisioning

Provisioned entitlements

Resource create

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

​Connector actions

​User states and provisioning

​Provisioned entitlements

​Resource create

​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

Connector actions

User states and provisioning

Provisioned entitlements

Resource create

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