Skip to content
Per-pair page

Connect Cal.com to Slack in two minutes.

Real-time triggers from Cal.com, ready-made actions in Slack. Filter, transform, and route without writing a line of code.

Trigger app
Cal.com as the trigger

Workflows fire when something happens in Cal.com.

Action app
Slack as the action

Workflows do something in Slack, instantly.

See all 45 actions →
Both directions

Pick the way that fits your stack.

Pair pages are mirrored. Each direction gets its own dedicated page.

Cal.comSlack

When something happens in Cal.com, do it in Slack.

3 Cal.com triggers wired to 45 Slack actions. Most-used pairing: Booking CancelledRaw API Request.

SlackCal.com

Or fire it the other way around.

13 Slack triggers wired to 7 Cal.com actions downstream.

See SlackCal.com
Popular pairings

Common Cal.com → Slack workflows.

Pick a pairing to set it up in two minutes. Each one is a fully editable recipe.

Showing 9 of 135 combinations
When booking cancelled in Cal.com, raw api request in Slack.

Fires when a booking is cancelled — by the booker, by the host, or via API. Payload includes the booking, the cancellation reason if provided, and the attendees. The hook for "free up calendar slot, notify waitlist, refund deposit" cascading workflows.

When booking cancelled in Cal.com, add reaction in Slack.

Fires when a booking is cancelled — by the booker, by the host, or via API. Payload includes the booking, the cancellation reason if provided, and the attendees. The hook for "free up calendar slot, notify waitlist, refund deposit" cascading workflows.

When booking cancelled in Cal.com, archive channel in Slack.

Fires when a booking is cancelled — by the booker, by the host, or via API. Payload includes the booking, the cancellation reason if provided, and the attendees. The hook for "free up calendar slot, notify waitlist, refund deposit" cascading workflows.

When booking cancelled in Cal.com, cancel scheduled message in Slack.

Fires when a booking is cancelled — by the booker, by the host, or via API. Payload includes the booking, the cancellation reason if provided, and the attendees. The hook for "free up calendar slot, notify waitlist, refund deposit" cascading workflows.

When booking created in Cal.com, raw api request in Slack.

Fires the moment someone books a meeting via Cal.com. Payload includes booker, host, event type, time, custom-question answers. The base hook for "new booking → push to CRM, send pre-meeting brief, create the Notion record" workflows.

When booking created in Cal.com, add reaction in Slack.

Fires the moment someone books a meeting via Cal.com. Payload includes booker, host, event type, time, custom-question answers. The base hook for "new booking → push to CRM, send pre-meeting brief, create the Notion record" workflows.

When booking created in Cal.com, archive channel in Slack.

Fires the moment someone books a meeting via Cal.com. Payload includes booker, host, event type, time, custom-question answers. The base hook for "new booking → push to CRM, send pre-meeting brief, create the Notion record" workflows.

When booking created in Cal.com, cancel scheduled message in Slack.

Fires the moment someone books a meeting via Cal.com. Payload includes booker, host, event type, time, custom-question answers. The base hook for "new booking → push to CRM, send pre-meeting brief, create the Notion record" workflows.

When booking rescheduled in Cal.com, raw api request in Slack.

Fires when a booking moves to a different time. Payload includes both old and new times. Useful for cascading updates — adjust downstream reminders, update calendar holds, sync the new time to client CRM record.

How it works

Connect Cal.com and Slack in five steps.

No code, no glue, no half-day setup. Each step is one click.

  1. 1
    Connect
    Authorize Cal.com and Slack

    Open Tiny Command, authorize Cal.com and Slack once each. Both connections are available to every workflow on your account.

  2. 2
    Trigger
    Pick a Cal.com trigger

    Drop the Cal.com → Booking Cancelled trigger onto the canvas. Tiny Command auto-registers the webhook.

    POST /v1/webhooks/cal-com.trigger-booking-cancelled
  3. 3
    Transform
    Add a filter or AI step

    Optionally add a Filter node ("subject contains URGENT") or an AI step ("classify intent") between trigger and action.

  4. 4
    Action
    Add the Slack action

    Drop the Slack → Raw API Request action below it. Map fields from the Cal.com payload into the Slack inputs.

    slack.api-request
  5. 5
    Publish
    Publish and forget

    Hit Publish. Tiny Command runs it in production from second one. Watch the run-log fill up.

FAQ

Questions about Cal.com + Slack.

How long does it take to connect Cal.com and Slack on Tiny Command?
Under two minutes. Authorize Cal.com and Slack once each, drop the Cal.com trigger and Slack action onto a workflow canvas, map a couple of fields, and publish. No code, no glue.
Is the Cal.com ↔ Slack integration real-time?
Yes. Both Cal.com and Slack expose webhooks, so events from one fire workflows in the other within seconds rather than on a polling interval.
Can I filter or transform data between Cal.com and Slack?
Yes. Add a Filter node to only pass through matching events, a Switch node to branch by value, or an AI / Code node to transform payloads before they hit Slack.
What Cal.com events can trigger a Slack workflow?
Any of the 3 Cal.com triggers, including "Booking Cancelled". Each fires in real time when the matching event happens in Cal.com.
Do I need a paid plan to use Cal.com with Slack?
No. There's a free tier that covers most Cal.com+Slack use cases without a credit card. Paid plans unlock higher run volumes and team features when you outgrow it.
What if I want Slack → Cal.com instead?
Build it the same way, in reverse. There's a dedicated /integrations/slack/with/cal-com page with the reverse-direction triggers and actions.
Related

Other apps that pair well with Cal.com.


Wire Cal.com to Slack in 2 minutes.

Free tier available. No credit card. No onboarding call.