Set up an Expensify connector

C1 provides identity governance for Expensify. Integrate your Expensify instance with C1 for unified visibility and governance over user access.

Capabilities

Resource	Sync	Provision
Accounts
Policies

Gather Expensify credentials

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

A user with access to the Expensify Integration Server must perform this task.

1. Log into Expensify and navigate to Integrations or click www.expensify.com/tools/integrations.

2. On the Integration Server Access page, copy and save your partnerUserID and partnerUserSecret.

Done. Next, move on to the connector configuration instructions.

Configure the Expensify connector

To complete this task, you’ll need:

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

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 Expensify 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. Paste the partnerUserID into the User ID field.

9. Paste the partnerUserSecret into the User secret field.

10. Click Save.

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

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

Self-hosted

Follow these instructions to use the Expensify 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 Expensify 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 Expensify connector deployment:

Secrets configuration

# baton-expensify-secrets.yaml
apiVersion: v1
kind: Secret
metadata:
  name: baton-expensify-secrets
type: Opaque
stringData:
  # C1 credentials
  BATON_CLIENT_ID: <C1 client ID>
  BATON_CLIENT_SECRET: <C1 client secret>
  
  # Expensify credentials
  BATON_PARTNER_USER_ID: <Expensify partner user ID>
  BATON_PARTNER_USER_SECRET: <Expensify partner user secret>

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

Deployment configuration

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

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