Set up a Ramp connector

C1 provides identity governance and just-in-time provisioning for Ramp. Integrate your Ramp instance with C1 to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access.

This is an updated and improved version of the Ramp connector! If you’re setting up Ramp with C1 for the first time, you’re in the right place.

Capabilities

Resource	Sync	Provision
Accounts
Roles
Vendors
Vendor agreements

Vendor owner is single-assignee. Each Ramp vendor can have only one owner at a time. Granting the vendor owner entitlement to a new user overwrites the previous owner in Ramp — the prior owner is silently removed. Revoking the entitlement clears the owner only when the principal being revoked is the current owner.

Synced Ramp vendors are emitted as C1 vendor resources with Ramp vendor identity metadata. Vendor owner access is represented as the owner entitlement on each vendor. Vendor agreements are available as an opt-in resource type and use the same Ramp vendors:read scope as vendors.

The Ramp connector supports automatic account provisioning.

Connector actions

Connector actions are custom capabilities that extend C1 automations with app-specific operations. You can use connector actions in the Perform connector action automation step.

Action name	Additional fields	Description
disable_user	user_id (string, required)	Deactivate a Ramp user. The user will no longer be able to log in, spend on cards, or receive notifications.
enable_user	user_id (string, required)	Reactivate a Ramp user. The user can log in to Ramp again, spend on their previously issued cards, and resume receiving notifications.

Gather Ramp credentials

To configure the Ramp connector, you need the Administrator role in Ramp.

The Ramp connector supports two authentication methods. Choose the one that fits your setup:

Option 1: Use an access token

1. In Ramp, navigate to Settings > Developers > API tokens.

2. Click Create a token, give it a name (for example, ConductorOne), and select the following scopes:

   • users:read — sync users and roles
   • vendors:read — sync vendors and vendor agreements

   If you enable provisioning, also select:

   • users:write — provision and deprovision users
   • vendors:write — grant and revoke vendor ownership

   If you enable audit-log event polling, also select:

   • audit_logs:read — read Ramp audit-log events for incremental sync

   The users:write and vendors:write scopes are used only when C1 provisions and deprovisions access. If you do not want C1 to perform these tasks, do not grant these scopes.

3. Click Create and copy the token. Save it somewhere secure — you won’t be able to view it again.

For more information, see the Ramp API token documentation.

Option 2: Use OAuth 2.0 client credentials

1. In Ramp, navigate to Settings > Developers > OAuth apps.

2. Click Create OAuth app and configure the following:

   1. Enter a name: ConductorOne

   2. Set the grant type to Client Credentials

   3. Select the following scopes:

      • users:read — sync users and roles
      • vendors:read — sync vendors and vendor agreements

      If you enable provisioning, also select:

      • users:write — provision and deprovision users
      • vendors:write — grant and revoke vendor ownership

      If you enable audit-log event polling, also select:

      • audit_logs:read — read Ramp audit-log events for incremental sync

   The users:write and vendors:write scopes are used only when C1 provisions and deprovisions access. If you do not want C1 to perform these tasks, do not grant these scopes.

   4. Click Create
3. Copy and save the Client ID and Client Secret. Save them somewhere secure — the secret won’t be shown again.

For more information, see the Ramp authorization documentation.

Configure the Ramp connector

To complete this task, you’ll need:

• The Connector Administrator or Super Administrator role in C1
• The Administrator role in Ramp

Cloud-hosted

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

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

2. Search for Ramp and click Add.

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

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

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

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

7. Find the Settings area of the page and click Edit.

8. Select your authentication method and enter the credentials you gathered earlier:

   • Access Token: paste your Ramp API access token into the Ramp Access Token field.
   • OAuth 2.0 Client Credentials: paste your Ramp OAuth client ID and client secret into the Ramp OAuth Client ID and Ramp OAuth Client Secret fields.
9. Click Save.

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

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

Self-hosted

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

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

2. Search for Baton and click Add.

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

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

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

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

7. In the Settings area of the page, click Edit.

8. 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 Ramp connector deployment.

The Ramp connector supports two authentication methods — pick one when populating the secret:

• Access Token — a long-lived Ramp API access token.
• OAuth 2.0 Client Credentials — a Ramp OAuth client ID and secret (the connector exchanges them for a short-lived access token automatically, via https://api.ramp.com/developer/v1/token).

See the Ramp authorization docs for how to create an OAuth app with the Client Credentials grant type and the following scopes:

• Required for read-only sync: users:read, vendors:read.
• Required only if BATON_PROVISIONING=true: users:write, vendors:write.
• Required only if BATON_AUDIT_LOG_EVENTS=true: Ramp audit-log API availability, such as Ramp Plus, and the audit_logs:read scope.

The connector points at https://api.ramp.com by default. Set BATON_RAMP_BASE_URL (or the Ramp API Base URL field) to https://demo-api.ramp.com (or another Ramp environment) to override.

Optional resources and events

The connector ships with an opt-in vendor_agreement resource type. When enabled in C1 resource-type settings, the connector syncs Ramp vendor agreements as their own resources, including term, renewal status, total contract value, and contract owners. Vendor agreements use the existing vendors:read scope; Ramp does not require a separate vendor-agreement scope.

Ramp vendors are always decorated with cross-system identity and pre-aggregated trailing-window spend when those fields are returned by Ramp.

Set BATON_AUDIT_LOG_EVENTS=true to expose Ramp’s audit-log API as an event feed so vendor and agreement changes can flow into C1 incrementally between full syncs. This setting is independent from vendor-agreement resource enablement and requires Ramp audit-log API availability, such as Ramp Plus, plus the audit_logs:read scope. When the flag is unset (the default), the audit-log API is not called.

Secrets configuration

Option A — Access Token:

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

  # Ramp credentials
  BATON_TOKEN: <Ramp API access token>

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

  # Optional: include if you want audit-log incremental sync events.
  # Requires Ramp audit-log API availability, such as Ramp Plus.
  BATON_AUDIT_LOG_EVENTS: "true"

Option B — OAuth 2.0 Client Credentials:

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

  # Ramp OAuth credentials
  BATON_RAMP_CLIENT_ID: <Ramp OAuth client ID>
  BATON_RAMP_CLIENT_SECRET: <Ramp OAuth client secret>

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

  # Optional: include if you want audit-log incremental sync events.
  # Requires Ramp audit-log API availability, such as Ramp Plus.
  # When set, the OAuth client must also have the `audit_logs:read` scope.
  BATON_AUDIT_LOG_EVENTS: "true"

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

Deployment configuration

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

Step 3: Deploy the connector

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

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

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