# CommandBar Destination

## About this integration

CommandBar gives your users a searchable index of your app’s features and content, and as customizable in-app components like onboarding nudges. This helps you better understand user intent and deliver step-change usability improvements for your users. By connecting Customer.io to CommandBar, you can trigger nudges and customize CommandBar functionality based on user events and user attributes. The integration also lets you deploy CommandBar to your users.

[Mode How we forward source data to the destination: through Customer.io's servers or directly from our JavaScript client.](/cdp/destinations/getting-started/#connection-mode)

[Web sources Indicates whether or not this integration supports our the JavaScript client.](/cdp/sources/getting-started/#types-of-sources)

[API sources Indicates whether or not this integration supports our server libraries (Go, NodeJS, Python), API, Mobile SDK, and other data sources.](/cdp/sources/getting-started/#types-of-sources)

[Supported calls The API methods this integration supports.](/cdp/sources/source-spec/source-events/)

[Integration name The name of this integration if you want to enable or disable it in the `integrations` object.](/cdp/sources/source-spec/common-fields/#the-integrations-object)

Web

[identify](/api/cdp/#operation/identify) and [track](/api/cdp/#operation/track)

commandbar

## Getting started[](#getting-started)

1.  Go to **[Data & Integrations > Integrations](https://fly.customer.io/workspaces/last/journeys/integrations/all/directory)** and select the **CommandBar** entry in the *Directory* tab.
    
2.  (Optional) Select the data sources that you want to connect to your outbound integration. You can always connect data sources later. We’ll only show you data sources that work with your integration.
    
3.  Configure your integration.
    
    1.  **Org Id**: The ID of your CommandBar organization.
        
    2.  **Deploy**: If enabled, CommandBar will be deployed to your site automatically and you can remove the snippet from your source code.
        
4.  Click **Enable Destination**.
    

## Actions[](#actions)

When you’re done setting things up, you can go to the *Actions* tab to see how we map incoming data to your integration.

You may need to add actions for this integration

While we often have default triggers for actions, we don't always add those actions as defaults. You may need to add actions to make sure that you're sending all the data that you want to send to your integration. See our [actions](/integrations/data-out/actions/) page for help setting up actions.

Action

Default Trigger

Description

Identify User

`type = “identify”`

Set attributes for the user in CommandBar. If "Deploy automatically" is enabled, then also boot CommandBar for the user, which makes CommandBar available to the user.

Track Event

`type = “track”`

Submit an event's properties as CommandBar metaData.