Skip to main content

Our integrations philosophy

We were good sharers as kids. At least when the sharing was done in a really well-defined way — NOT when the sharing involved arbitrarily handing over the fire truck that we were currently playing with TIMMY!

Anyways, that trait has blossomed into the plethora of integrations which you see below. We have a lot of these today because CommandBar is an intentionally-focused product with lots of non-features (features we don’t intend to build because they would distract from our core mission of helping end users use software).

Where we don’t build, we integrate with the best tools out there that our customers are currently using.

There’s two ways to think about our integrations:

  • The list of companies we integrate with: this makes it easy to say “I use Vendor X —> does CommandBar integrate with Vendor X —> if so, how does that integration work”
  • The types of integrations we support: the product stack is confusing. Vendors do lots of different things. This cut makes it possible for you to see the types of functionality that CommandBar integrates with. For some vendors, there’s a 1:1 map. For others, we integrate with them in multiple ways.

All the companies we integrate with

Here’s a list of every company we have some sort of integration with. You can click each to learn more about how each works.




Data lake


Knowledge base


Community platform


The types of integrations we support

Here are the different functionalities we support via integrations.

  • Knowledge base: CommandBar uses content in various ways. To train Copilot, to make articles available in HelpHub, or to nudge users toward useful content.
  • Data (outgoing): CommandBar generates a lot of events as a result of users interacting with our experiences. We have our own dashboards, but most of our customers analyze product data somewhere else to. Our outgoing data integrations support this. Destinations include analytics tools (like Amplitude, Mixpanel, and Heap), CDPs (like Segment and Rudderstack), and customer tools (like Salesforce and HubSpot).
  • Data (incoming): One of the key ways CommandBar aims to help users is through targeting nudges so that users see only proactive help they care about. A lot of the data to target users comes from CommandBar itself, but more is always better. So we’ve built many integrations that import data to make targeting better. That might involve bringing in raw data or structured data (for example, importing a segment of users from an analytics tool where you do that kind of thing). Typically, integrations where we have an outgoing data integration have a correspond incoming integration.
  • Data (search): The data integrations above relate to data about users. We also have integrations to allow users to access their data (that you store for them) from CommandBar. The two places this happens are in Spotlight and in Copilot (🤫 it’s coming soon). We access user data through search companies: Algolia, Elastic.
Knowledge baseData (outgoing)Data (incoming)CS handoffData (search)
Help Scoutx
Vanilla Forumsx
  • Random: We sometimes build integrations just for fun that don’t fit into these categories. For example, we have a Slack integration that pings you when exciting things happen in CommandBar (like when a user fills out a survey).
  • Analytics tools: CommandBar generates a lot of events as a result of users interacting with our experiences. We have our own dashboards, but most of our customers analyze product data somewhere else to. So we integrate with those tools, for two reasons. (1) To allow CommandBar data to flow into those tools so it can live alongisde the rest of your product data. (2) To bring data from those tools into CommandBar to use for targeting.
  • CDPs: We integrate with major CDPs (Rudderstack, Segment) to connect to all the tools connected to your CDP. It’s kind of like a meta integration. Once you sync CommandBar with a CDP, it becomes way easier to both pull CommandBar data into other tools, and also send data to CommandBar.
  • CRMs: Sales systems contain a lot of value data used for targeting users (for example, what features a user/team is paying for). It’s also a good destination for some types of CommandBar data. For example, maybe you want a customer’s most recent NPS score (are you tracking that?) to live alongside your customer contacts so it can inform your renewal workflow.
  • CS/Support: we try to help users as much as we can, but sometimes there’s no substitute for a bonafide human. CommandBar is not a tool for support agents, but we do integrate with the best in that business (Intercom, Zendesk, Freshworks, HubSpot, and others) to seamlessly hand off to them when the going gets tough. The most obvious place this happens is in Copilot when the user has had enough of us.