Set up a n8n connector

Capabilities

The n8n connector syncs the following resources:

Resource	Sync	Provision
Users
Global Roles
Projects

Known limitations:

n8n does not support disabling or suspending users — only inviting or deleting them. C1 cannot suspend n8n users.
Project membership provisioning is blocked by n8n (returns 403) when SSO-based provisioning is enabled on the instance. C1 will report the error if this occurs.
Revoking the global:member role is a no-op — it is the base instance role. To remove a user entirely, use the delete user action.
There is no SCIM support in n8n.

Gather n8n credentials

To configure the n8n connector, you need Owner or Admin permissions in your n8n instance so that the API key has access to user and project management endpoints.

In the left sidebar, select API.

Click Create an API key, give it a descriptive name (for example, ConductorOne), and click Save.

Copy the generated API key. You will not be able to view it again after leaving this page.

Note the base URL of your n8n instance (for example, https://n8n.mycompany.com). This is the value you will use for the Instance URL field.

Configure the n8n connector

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 n8n and click Add.

Choose how to set up the new n8n connector:

Add the connector to a currently unmanaged app
Add the connector to a managed app
Create a new managed app

Set the owner for this connector.

Click Next.

Find the Settings area of the page and click Edit.

Enter the required configuration:

API Key (BATON_N8N_API_KEY): The n8n API key you created above.
Instance URL (BATON_N8N_INSTANCE_URL): The base URL of your n8n instance (for example, https://n8n.mycompany.com).

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

Follow these instructions to use the n8n 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 n8n connector

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

Search for Baton and click Add.

Choose how to set up the new n8n connector:

Add the connector to a currently unmanaged app
Add the connector to a managed app
Create a new managed app

Set the owner for this connector.

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.

Step 2: Create Kubernetes configuration files

Create two Kubernetes manifest files for your n8n connector deployment:

Secrets configuration

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

  # n8n credentials
  BATON_N8N_API_KEY: <n8n API key>
  BATON_N8N_INSTANCE_URL: <n8n instance URL, e.g. https://n8n.mycompany.com>

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

Deployment configuration

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

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

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

Set up a MongoDB Atlas connector

Set up an nCino connector

⌘I

Welcome

Manage connectors

Deploy connectors

Upload connector data

Configurable connectors

Pre-built connectors

Set up a n8n connector

Capabilities

Gather n8n credentials

Configure the n8n connector

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

Documentation Index

​Capabilities

​Gather n8n credentials

​Configure the n8n connector

​Step 1: Set up a new n8n connector

​Step 2: Create Kubernetes configuration files

​Secrets configuration

​Deployment configuration

​Step 3: Deploy the connector

Capabilities

Gather n8n credentials

Configure the n8n connector

Step 1: Set up a new n8n connector

Step 2: Create Kubernetes configuration files

Secrets configuration

Deployment configuration

Step 3: Deploy the connector