Set up a Twilio SendGrid connector

Capabilities
Gather SendGrid credentials
Create a SendGrid API key
Configure the SendGrid connector

Capabilities

Resource	Sync	Provision
Accounts
Scopes
Subusers

The SendGrid connector supports automatic account provisioning and deprovisioning. New accounts are invited by email with optional scopes and admin permissions:

is_admin: Whether the teammate has admin privileges (default: false).
scopes: List of permission scopes for non-admin teammates (default: “user.profile.read”). Scopes are ignored when is_admin is true, as admins have full access.

Gather SendGrid credentials

Configuring the connector requires you to pass in credentials generated in SendGrid. Gather these credentials before you move on.

Create a SendGrid API key

In SendGrid, navigate to Settings > API Keys.

Click Create API Key.

Give your API key a name, such as “ConductorOne integration”.

Select Full Access.

Click Create & View.

The new API key is created. Carefully copy and save the API key.

That’s it! Next, move on to the connector configuration instructions.

Configure the SendGrid connector

To complete this task, you’ll need:

The Connector Administrator or Super Administrator role in ConductorOne
Access to the set of SendGrid credentials generated by following the instructions above

Cloud-hosted
Self-hosted

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

In ConductorOne, navigate to Admin > Connectors and click Add connector.

Search for SendGrid and click Add.

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

Paste your API key into the API key field.

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

Follow these instructions to use the SendGrid connector connector, hosted and run in your own environment.When running in service mode on Kubernetes, a self-hosted connector maintains an ongoing connection with ConductorOne, automatically syncing and uploading data at regular intervals. This data is immediately available in the ConductorOne UI for access reviews and access requests.

Step 1: Set up a new SendGrid connector

In ConductorOne, navigate to Connectors > Add connector.

Search for Baton and click Add.

Choose how to set up the new SendGrid 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 ConductorOne)
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 SendGrid connector deployment:

Secrets configuration

# baton-sendgrid-secrets.yaml
apiVersion: v1
kind: Secret
metadata:
  name: baton-sendgrid-secrets
type: Opaque
stringData:
  # ConductorOne credentials
  BATON_CLIENT_ID: <ConductorOne client ID>
  BATON_CLIENT_SECRET: <ConductorOne client secret>
  
  # SendGrid-specific credentials
  BATON_SENDGRID_API_KEY: <SendGrid API key>
  BATON_SENDGRID_REGION: <SendGrid service region (defaults to global)>

  # Optional: include if you want to skip syncing SendGrid subusers
  BATON_IGNORE_SUBUSERS: <true>

  # Optional: include if you want ConductorOne 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-sendgrid.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
  name: baton-sendgrid
  labels:
    app: baton-sendgrid
spec:
  selector:
    matchLabels:
      app: baton-sendgrid
  template:
    metadata:
      labels:
        app: baton-sendgrid
        baton: true
        baton-app: sendgrid
    spec:
      containers:
      - name: baton-sendgrid
        image: ghcr.io/conductorone/baton-sendgrid:latest
        imagePullPolicy: IfNotPresent
        env:
        - name: BATON_HOST_ID
          value: baton-sendgrid
        envFrom:
        - secretRef:
            name: baton-sendgrid-secrets

Step 3: Deploy the connector

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

Check that the connector data uploaded correctly. In ConductorOne, click Applications. On the Managed apps tab, locate and click the name of the application you added the SendGrid connector to. SendGrid data should be found on the Entitlements and Accounts tabs.

That’s it! Your SendGrid connector is now pulling access data into ConductorOne.

Set up a Tray.ai connector

Set up a Twingate connector

⌘I

Welcome

Build connectors

Configure connectors

Deploy connectors

Upload connector data

Connector library

Set up a Twilio SendGrid connector

Capabilities

Gather SendGrid credentials

Create a SendGrid API key

Configure the SendGrid connector

Step 1: Set up a new SendGrid connector

Step 2: Create Kubernetes configuration files

Secrets configuration

Deployment configuration

Step 3: Deploy the connector

Welcome

Build connectors

Configure connectors

Deploy connectors

Upload connector data

Connector library

​Capabilities

​Gather SendGrid credentials

​Create a SendGrid API key

​Configure the SendGrid connector

​Step 1: Set up a new SendGrid connector

​Step 2: Create Kubernetes configuration files

​Secrets configuration

​Deployment configuration

​Step 3: Deploy the connector

Capabilities

Gather SendGrid credentials

Create a SendGrid API key

Configure the SendGrid connector

Step 1: Set up a new SendGrid connector

Step 2: Create Kubernetes configuration files

Secrets configuration

Deployment configuration

Step 3: Deploy the connector