Capabilities

Available hosting methods

Choose the hosting method that best suits your needs:

Gather Trello credentials

Each setup method requires you to pass in credentials generated in Trello. Gather these credentials before you move on.

A user with access to the Power-UP Admin Portal in Trello must perform this task.

Create a Trello Power-Up and generate an API key

1. Navigate to the Trello Power-Up Admin Portal and click New.

2. Give the new Power-Up a name, such as “ConductorOne” and select your Trello Workspace.

3. Leave the Iframe connector URL field blank and fill out the rest of the form.

4. Click Create.

5. Navigate to your new Power-Up’s API key tab and click Generate a new API key.

6. Carefully copy and save the API key.

Create an Atlassian API token

1. Log in to Atlassian and click Create API token.

2. Give your API token a name and select an expiration date for the token.

3. Click Create.

4. Carefully copy and save the API token.

Look up Trello organization IDs

Finally, we’ll use the Trello API to look up the IDs of the Trello organizations you want to sync to ConductorOne.

1. Navigate to https://api.trello.com/1/organizations/[organization-name]?key=[API-key]&token=[API-token], passing in the organization’s name and the values of the API key and token you created for [organization-name], [API-key], and [API-token].

   To look up an organization name, navigate to the organization in Trello and copy the name from the URL.

2. Carefully copy and save the ID of the organization.

3. Repeat the steps as needed to look up the IDs of additional organizations.

That’s it! Next, move on to the instructions for your chosen setup method.

Set up a Trello cloud-hosted connector

To complete this task, you’ll need:

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

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

2. Search for Trello and click Add.

   Don’t see the Trello connector? Reach out to support@conductorone.com to add Trello to your Connectors page.

1. Choose how to set up the new Trello 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

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

3. Click Next.

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

5. Paste the API key into the API key field.

6. Paste the API token into the API token field.

7. Paste the comma-separated list of IDs of the organization you want to sync into the Organizations field.

8. Click Save.

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

Set up a Trello self-hosted connector

To complete this task, you’ll need:

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

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.

Why use Kubernetes? Kubernetes provides automated deployment, scaling, and management of your connectors. It ensures high availability and reliable operation of your connector services.

Step 1: Configure the Trello connector

1. In ConductorOne, navigate to Connectors > Add connector.

2. Search for Baton and click Add.

3. Choose how to set up the new Trello 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

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

5. Click Next.

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

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

Secrets configuration

# baton-trello-secrets.yaml
apiVersion: v1
kind: Secret
metadata:
  name: baton-trello-secrets
type: Opaque
stringData:
  # ConductorOne credentials
  BATON_CLIENT_ID: <ConductorOne client ID>
  BATON_CLIENT_SECRET: <ConductorOne client secret>
  
  # Trello credentials
  BATON_API_KEY: <Trello API key>
  BATON_API_TOKEN: <Trello API token>
  BATON_ORGS: <Array of the IDs of Trello organizations to sync>

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

Deployment configuration

# baton-trello.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
  name: baton-trello
  labels:
    app: baton-trello
spec:
  selector:
    matchLabels:
      app: baton-trello
  template:
    metadata:
      labels:
        app: baton-trello
        baton: true
        baton-app: trello
    spec:
      containers:
      - name: baton-trello
        image: ghcr.io/conductorone/baton-trello:latest
        imagePullPolicy: IfNotPresent
        envFrom:
        - secretRef:
            name: baton-trello-secrets

Step 3: Deploy the connector

1. Create a namespace in which to run ConductorOne connectors (if desired):

   kubectl create namespace conductorone
   

2. Apply the secret configuration:

   kubectl -n conductorone apply -f baton-trello-secrets.yaml
   

3. Apply the deployment:

   kubectl -n conductorone apply -f baton-trello.yaml
   

Step 4: Verify the deployment

1. Check that the deployment is running:

   kubectl -n conductorone get pods
   

2. View the connector logs:

   kubectl -n conductorone logs -l app=baton-${baton-trello}
   

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

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