How to Build a Meeting Booked Alert in Slack

How do you get a Slack alert every time a prospect books a meeting?

Trigger a workflow when a meeting is booked, filter out internal and rescheduled meetings, and post a short message with the prospect, company, source, and owner to one Slack channel. In HubSpot, a meeting-based workflow with the Slack action does this. Outside HubSpot, your scheduler's webhook plus Make or Zapier works.

This tutorial is for one specific reader: a founder or sales lead at a small B2B team who wants to see booked meetings as they happen, without opening the CRM. Maybe you have two reps and a marketer. Maybe it is just you and an SDR.

A meeting-booked alert sounds like a small thing. In practice it changes how a team behaves. Reps prep sooner. Marketing sees which campaigns produce real conversations. And the founder stops asking "how many demos this week?" because the answer scrolls past every day.

What should count as a booked meeting?

Decide this before you build anything. A booked meeting should be a first or qualifying conversation with an external prospect, booked through a scheduling link or logged by a rep. It should exclude internal syncs, customer check-ins, and reschedules, or your channel fills with noise that people learn to mute.

Write the definition in one sentence and share it with the team. Mine usually reads: "A new meeting with a contact who is not a customer, booked on a sales scheduling page or logged by a rep as a discovery call." That sentence becomes your filter logic.

If you are unsure, start narrow. It is easier to add meeting types to the alert later than to win back attention after the channel becomes spam. A quiet, accurate channel is worth more than a busy one nobody reads.

Which channel should the alert go to?

Use one dedicated channel, something like #meetings-booked, and post nothing else there. Do not drop meeting alerts into a general sales channel where they compete with chatter. A dedicated channel lets people mute everything else and still see bookings, and it gives you a clean daily record.

Some teams also want the meeting owner to get a direct message. That is a good addition, not a replacement. The channel is for visibility. The direct message is for action. I would build the channel alert first, then add direct messages once the format is settled.

Keep the channel public inside your Slack workspace. Marketing, sales, and leadership should all see it. Part of the value is shared context: everyone knows what is happening in the pipeline without a meeting about it.

How do you build the alert inside HubSpot?

Create a meeting-based workflow and add the Slack action. HubSpot's own documentation lists a meeting workflow example, "create a deal record anytime a demo meeting is booked," and lists Slack under connected app actions, which send "a Slack notification to your integrated Slack workspace." Your Slack integration must be connected first.

Here is the flow in plain steps. First, connect the HubSpot and Slack integration if you have not already. Second, create a new workflow based on meetings. Third, set the enrollment trigger to fire when a meeting is booked, using the meeting trigger options your account shows, and add filters for your definition, such as meeting type or the scheduling page used.

Fourth, add the Slack notification action and choose your #meetings-booked channel. Fifth, write the message using the meeting and contact details available in the workflow. Workflows require specific HubSpot subscriptions, so check HubSpot's documentation for what your plan includes before you start. Then turn the workflow on and book a test meeting.

How do you build it if your scheduler is not HubSpot?

Use your scheduling tool's webhook or native integration as the trigger, and send it through Make or Zapier to Slack. Most scheduling tools can notify another app when a meeting is booked. Check your tool's documentation for the exact event name, since each vendor labels it differently.

The automation has four steps. Catch the booking event. Look up the contact in your CRM by email to get the owner and source. Apply your filters, such as skipping internal domains and existing customers. Then post the message to Slack.

The CRM lookup is the step people skip, and it is the one that makes the alert useful. Without it, you only know a name and a time. With it, you know the company, who owns it, and where the lead came from. If you already route form leads to Slack, the same lookup pattern applies, as I covered in how to route Webflow form leads to Slack channels by lead type.

What should the Slack message say?

Keep it to five lines: who booked, from which company, when the meeting is, who owns it, and where the lead came from. Add one link to the CRM record. Anything longer turns a glanceable alert into something people skim past. The goal is context in three seconds.

A format I like looks like this in practice. First line: the contact's name and title, plus the company. Second line: the meeting date and time. Third line: the owner. Fourth line: the original source, such as "organic, pricing page" or "outbound, sequence B." Fifth line: the record link.

Resist adding scores, notes, and every form field. If a rep needs more, they click through. The alert's job is to announce the meeting and point to the record, not to replace the CRM.

How do you filter out noise?

Filter on three things: internal email domains, existing customers, and reschedules. Internal meetings are the most common noise. Customer meetings belong in a different channel, if anywhere. Reschedules can look like new bookings in some tools, so check whether your trigger fires on updates as well as creation.

Test each filter on purpose. Book a meeting from a teammate's address and confirm no alert appears. Book one from a test contact marked as a customer. Reschedule a test meeting and watch what happens. Ten minutes of deliberate testing saves weeks of a noisy channel.

Also decide what happens with no-shows and cancellations. Some teams post a short follow-up line when a meeting is canceled. I prefer to keep the channel focused on bookings and track cancellations in reporting instead.

How do you know the alert is reliable?

Compare the Slack channel against your CRM once a week for the first month. Count booked meetings in the CRM and count alerts in Slack. If the numbers differ, find the missing meetings and check why the workflow skipped them. A silent miss is worse than no alert, because people trust the channel.

The usual causes are a scheduling page not covered by the trigger, a contact without an email match, or a filter that is too strict. Fix each one as you find it. After a month of matching counts, a monthly check is enough.

Once you trust the alert, it becomes a data source too. The same events can feed a dashboard of meetings by source. I walked through that in how to build a meetings booked by source dashboard in HubSpot.

What should you do next?

Write your one-sentence definition of a booked meeting, create a #meetings-booked channel, and build the workflow with the five-line message. Then book three test meetings: one valid, one internal, and one rescheduled. If only the valid one posts, your alert is ready for the team.

After a week, ask your reps if the alert changed how they prepare. If it did, consider adding a direct message to the meeting owner with a short prep checklist. If you also want to measure how quickly inbound leads reach that first meeting, see how to measure time to first meeting for inbound leads.

If you want help wiring meeting alerts, routing, and reporting into one system that your team trusts, reach out. I build websites and the automations behind them for lead generation, and small alerts like this are often where a revenue team starts to feel the difference. Let's chat.