Cal.com logo
Slack logo

Workflow template

Notify Slack about new Cal.com bookings

Notify a Slack channel when a new Cal.com booking is created. Share the booking title, UID, scheduled start and event time without mapping attendee email fields into the alert.

How it works

From a new Cal.com booking to a Slack alert

1 Trigger · 1 Action
Cal.com1 · Trigger

Booking created

Receive signed BOOKING_CREATED webhooks for the connected Cal.com account. Event coverage depends on the account’s plan, role and booking ownership.

Slack2 · Action

Notify Slack about new Cal.com bookings

Post the booking title, UID, start time and event time to the chosen Slack channel. Markdown and link/media previews are disabled.

The result

A short booking announcement in Slack

The prepared alert helps your team notice a booking. It does not include attendee email fields or all of the booking-form answers.

Example Slack message

New Cal.com booking: FICTIONAL FastHook booking Booking UID: FICTIONAL_BOOKING Starts: 2026-11-10T10:00:00Z Event time: 2026-11-02T00:00:00.000Z

Fictional booking data. Starts is the scheduled meeting time, while Event time comes from the webhook envelope.

Before activation

Set up your workflow

  1. Connect Cal.com

    Use OAuth or a dedicated API key. Confirm that the booking link is covered by the connected account’s webhook and that the account’s plan and role allow the event.

  2. Select the Slack channel

    Connect Slack and choose a channel where FastHook can post. Review its membership because the booking title, UID and timing will be shared there.

  3. Create a fictional booking

    Activate and wait for the signed booking webhook connection. Make a fictional booking through a covered link and verify the resulting message and workflow run.

Details and limitations
  • New bookings rather than calendar synchronization. This template listens for booking-created events. Later reschedules and cancellations do not edit the Slack announcement or send a notification through this workflow.

  • Team links can require a different hook. The managed webhook is account-level. Team-owned booking links may require a team or event-type subscription. FastHook manages only subscriptions it owns and removes them when no active consumer needs them.

  • Plain text with possible repeats. The mapped message contains only title, UID, start time and event time; attendee email fields are not copied. Manual reruns can send it again. Link and media previews are disabled.

Questions about this template

Which booking details are posted to Slack?

The prepared message contains the booking title, UID, scheduled start and event time. It does not map attendee email fields or additional booking-form answers.

Does the alert include the meeting document or a booking link?

No. This template’s message contains the four prepared booking fields only. Creating a document or adding another link requires extending the workflow.

Will reschedules or cancellations update the message?

No. The trigger handles BOOKING_CREATED, and the Slack step posts a new announcement. It does not maintain earlier messages as bookings change.

Why might a team-owned booking not trigger the workflow?

The native webhook is account-level. A team-owned booking link may need a separate team or event-type hook, and event coverage depends on the Cal.com plan and role.

Explore connected apps