Skip to main content
Connect Calendly, Cal.com or Brevo so a meeting booked through any of them moves the lead who booked it to Meeting Scheduled.
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.
All three are meeting trackers, not CRMs: none of them ever receives a lead. Each only reports a booking back, so the app can log it and move the lead along.

​
Before you begin

  • An account with whichever one of the three you already book through. You only need one; nothing here needs all three connected at once.
  • For Cal.com or Brevo, permission in that account to generate an API key. Calendly instead asks you to sign in and approve access, with no key involved.
  • For Brevo, one manual step in Brevo’s own dashboard partway through, covered below.

​
Steps

1

Open the connector list

Go to and choose Add integration. Calendly, Cal.com and Brevo are the first three entries in the list, above the CRM connectors. Pick whichever one you use.
2

Connect Calendly

Choosing Calendly opens no dialog. Your browser leaves the app for Calendly, where you sign in and approve access. Approving it brings you back to (the settings tab, even though you started on the sidebar) with a toast confirming the connection, and a webhook subscription is requested on your Calendly account in the same round trip.That toast confirms the sign-in, not the webhook. Only a failed sign-in produces an error toast: a webhook subscription Calendly refused still lands you on a success toast, and only shows up afterwards as a warning chip on the card.
3

Connect Cal.com

Choosing Cal.com opens a dialog with a six-step panel for finding your API key in Cal.com’s own settings, and a field to paste it into underneath.The panel (1) walks through Cal.com’s own account settings; the field to paste the result into (2) sits underneath it. Only a key starting with cal_ is accepted; anything else is refused in the dialog, before it is sent anywhere.Paste a real one and choose Connect. The key is checked against your Cal.com account and stored, and a webhook subscription is created on Cal.com in the same request. If that works, the dialog reads Integration Complete!. If it does not, the dialog reads Connected with Limited Functionality, carrying Cal.com’s own reason where one came back. The account is connected either way; what is missing is the webhook, and without it no booking ever reaches the app.
4

Connect Brevo

Choosing Brevo opens a similar dialog, but Brevo has no API for creating a meeting webhook, so this connection takes one extra step that you do yourself.The panel (1) walks through Brevo’s own account settings; the field (2) is underneath it. Only a key starting with xkeysib- is accepted.Paste it and choose Next. The key is checked against your Brevo account, and the dialog moves to a second step showing a webhook URL to copy. Open Brevo yourself, add an outbound webhook under Meetings → Settings → Webhooks with that URL, set its event category to Meetings, and turn on the Meeting booked event. Turn on nothing else: a Brevo webhook that arrives with participants on it is read as a booking, whatever event sent it.Back in the dialog, choose Done, then, once the button changes, Yes, I created it!. The first click only asks you to confirm; the second is what marks the connection ready. Until it is, the card carries a Finish setup chip.

​
What happens next

The connector’s card on shows a Connected chip, with the account’s own email under its name. Where the service returned no email, the card shows the date you connected it instead.
From here on the app listens for a webhook from whichever of the three you connected. Only a new booking does anything. Calendly’s subscription also covers cancellations and no-shows, and Cal.com’s covers cancellations and reschedules: those arrive and change nothing, so a lead a booking moved to Meeting Scheduled stays there even if the meeting is later called off. When a booking does arrive, the app looks for a lead already in this workspace, in this order: the exact address that booked it, then that address’s domain, then those same two tries again for each of the other people on the booking. The domain step is narrower than it sounds. It is skipped altogether for public mail domains (gmail.com, outlook.com, yahoo.com and a long list of others), so a booking from a personal address only ever matches on the exact address. Where it does apply, it considers only leads that are not Closed and already have at least one message on record, and takes the most recently active of those. A lead matched that way keeps the booking address: it is added to that lead’s own list of emails. On a match, the app records the meeting as an event on that lead, moves the lead to Meeting Scheduled unless it is already there or Converted, pauses automated outreach to it, and raises a notification saying the lead booked a meeting. If nothing on the booking matches a lead, nothing is recorded in this workspace at all: no lead is created, no meeting appears, no stage moves. A connected card’s title is built from the connector’s type rather than the brand. Calendly and Brevo both come out right, but a connected Cal.com card reads “Cal Com”, with a space. Connection health is only ever surfaced for these three. When a webhook is missing or failed, the card carries a warning chip, worded differently for each. Calendly’s reads “Require attention”; its tooltip repeats Calendly’s own error where there is one, and otherwise says that tracking campaign meetings needs a Calendly Standard subscription. Cal.com’s reads “Limited functionality”, with Cal.com’s reason in the tooltip where one came back. Brevo’s is the only one you can click: Finish setup reopens the Brevo dialog on the webhook step described above. No CRM connector carries a warning chip of any kind, so these three are the only health signal this screen gives you.

​
Troubleshooting

The key had the right prefix (cal_ or xkeysib-), so it was sent on to be checked against your account there, and the service refused it. Copy a fresh key straight from Cal.com’s or Brevo’s own settings page rather than retyping it, and confirm it has not been revoked since you copied it.
What it means depends on the connector. Calendly’s “Require attention” is the tooltip’s fallback when Calendly sent no error of its own, and it points at the usual cause: the account is not on Calendly’s Standard plan. Cal.com’s “Limited functionality” means the automatic webhook subscription failed; hover the chip for Cal.com’s own reason, where it gave one. Brevo’s Finish setup means the manual webhook step in Brevo’s dashboard has not been confirmed yet. Click it to reopen the dialog where you left off.
A booking only moves a lead that is already in this workspace and that one of the booking’s own addresses reaches. The exact address is tried first. The fallback on its domain is skipped for personal mail domains, and otherwise only reaches leads that are not Closed and have at least one message on record, so a booking from a colleague at a company you have never written to matches nothing. When nothing matches, no lead is created and nothing is logged where you could see it.

Meetings overview

The product’s own meeting links, for booking without ever leaving the app.

Lead stages and the funnel view

The six fixed stages, and what else moves a lead between them.

Calendar connections

A different connection: your own calendar, used to check conflicts and place bookings from a meeting link.