Skip to main content

CRM integrations overview

CommandBar integrates with many popular CRMs, including Salesforce and HubSpot.

What is the purpose of these integrations?

We integrate with CRMs for two primary reasons

  1. Analyze CommandBar-generated data alongside other customer data. For example, you might want to include a user’s recent Copilot queries in their customer record, so your customer teams can view them.
  2. Leverage user data for targeting. CRMs contain rich information about a user’s account — the organization they are a part of, the channel through which they created an account, etc. All of this information can be used to construct audiences and targeting conditions to deliver personalized experiences to users.

What can I do if I use a CRM you don’t integrate with?

Answer 1: Use a CDP

We integrate with popular CDPs like Segment and Rudderstack. Often, you can use those as a proxy between CommandBar and your CRM.

Answer 2: Use our SDK and API

Fear not. Our integrations are a relatively thin layer on top of some pretty basic general-purpose SDK and API methods that you can use to create your own integration with any third-party CRM.

Sending data from CommandBar

To do this, you can utilize an event subscriber. Simply create an event subscriber and within the body of that subscriber send the event payload to the CRM or analytics tool of your choice.

// The function that handles CommandBar events
const myHandler = (eventName, eventData) => {
sendToCRM({ name: eventName, ...eventData });
};

// Subscribe to CommandBar events
const unsubPromise = window.CommandBar.addEventSubscriber(myHandler);

// Later, call the function returned by the promise
// to unsubscribe your handler from CommandBar events.
unsubPromise.then((unsub) => unsub());

Sending data to CommandBar

To send data to CommandBar, you can use the strategies described in our User Properties doc.

  1. Provide audience and other user properties via the boot SDK method
  2. Use the https://api.commandbar.com/api/{your_org_id}/bulk-identify/ API URL — be sure not to forget the trailing slash!