Every connector you can add, the three shapes a connection takes, and what a card tells you once it is connected.
Apps & CRM is where you connect the outside services this workspace pushes leads to, reads meeting bookings from, and posts alerts into. The sidebar entry and open the same screen, and on both the card heading reads Integrations.
Where
Integrations→Integrations→Apps & CRM
Your role needs
Read access to Apps & CRM read-integrations. Admin, Member and Viewer have it by default.
To create or change
create-integrations to add one, update-integrations to change one, on top of the permission above.
If you cannot find this in your sidebar, your workspace may have a custom menu configuration. Contact support and we will check it for you.
Add integration opens the whole catalog in one menu, in this order: Calendly, Cal.com and Brevo, which read meeting bookings back into your campaigns; HubSpot, Salesforce, Odoo and Kommo, which create a record in your CRM; HeyReach, which appends the lead to a LinkedIn-outreach list; Slack, which posts lead alerts into a channel; and Webhook, which sends the lead to any endpoint you name (an automation tool such as Zapier or Make, or your own API). The grid below the button is not limited to that list, though: it shows every connector this workspace has, so a Google Calendar connected from a meeting link appears here as a card too.Connecting takes one of three shapes, and which one you get decides where you finish. Most connectors open a dialog on top of the page: you paste an API key (Brevo, Cal.com, HubSpot, HeyReach), a set of instance credentials (Odoo) or a URL (Slack, Webhook), and the dialog reports success or failure in place without the page ever navigating. Calendly is the exception with no dialog at all: picking it sends your browser straight to Calendly to sign in. Salesforce and Kommo do both: a dialog first, then the same full-page redirect. Salesforce asks whether the org is Production or Sandbox before it sends you; Kommo offers Use your own private integration (optional), where you supply a Kommo integration ID and secret key of your own instead of using the shared app. Where no shared Kommo app is configured for your deployment, that section is titled Connect with your own private integration and is the only way through.Every one of those redirects comes back to (the settings tab, even if you started from the sidebar) with a toast saying whether the connection worked.A connected card carries the connector’s name, its logo, the account’s email or the date it was connected, and a Connected pill (1). Kommo is the only connector that can carry a second pill, Private app, which appears when the connection was authorized with your own Kommo credentials rather than the shared app. A warning chip is wired for exactly three connectors, and all three are the meeting trackers: Calendly gets one when its webhook is missing or errored, and its tooltip shows Calendly’s own error message where there is one, otherwise that tracking campaign meetings needs a Calendly Standard subscription; Cal.com gets one when its webhook did not subscribe; and Brevo’s is the only chip you can click: Finish setup reopens the Brevo dialog at its webhook step. No CRM connector has a warning chip of any kind, so a CRM that has stopped accepting leads looks exactly like a healthy one here.Below that, seven connectors (HubSpot, HeyReach, Salesforce, Odoo, Kommo, Slack and Webhook) carry an Auto-push analyzed leads block (2). It starts as one switch, off. Turn it on and five stage chips appear: Untouched, Contacted, Opportunity, Meeting Scheduled and Converted. Ticking chips limits the automatic push to leads in those stages; leaving all five unticked pushes at any stage. Nothing is stored until you press the Save button that appears as soon as you change something. Slack and Webhook sit in that list because they receive the same lead, but they only notify. They never claim it, so they can fire alongside a real CRM and again on a later stage change. The other five create a record, and only one of them ever owns a given lead: once one has pushed it, the rest skip it.The trash icon on a card needs delete-integrations. The pencil needs update-integrations and only ever appears on a webhook card, because a webhook is the only connector whose configuration you wrote yourself; every other type has to be deleted and reconnected to change. update-integrations also governs the auto-push block: a role without it gets the card with no block at all, rather than a disabled one. Deleting is refused outright while a campaign still points at the connector: the tie an agent makes when it takes its meeting link from a connected Calendly account. That refusal never reaches the screen: the confirmation dialog stays open with no message, so if deleting appears to do nothing, check whether an agent is still using it.With nothing connected, the grid is replaced by an icon, the heading No integrations yet, one line of explanation and a second Add integration button. The one in the card header stays where it is.
