SourCherry Help Centre
HomeWorkflowsGetting Started w/ Workflows

Cal.com: Workflow Actions & Triggers

Connect Cal.com to SourCherry Workflows to automate scheduling activity without custom webhooks, third-party tools, or manual booking follow-up. Use Cal.com triggers to start workflows when bookings are created, rescheduled, cancelled, or completed, and use Cal.com actions to create, cancel, reschedule, or find bookings directly from a workflow. This helps teams keep CRM records, customer communication, and scheduling operations aligned in real time.


TABLE OF CONTENTS



What is Cal.com Actions & Triggers in Workflows?


Cal.com Actions & Triggers in Workflows connects Cal.com scheduling events with SourCherry’s Workflow Builder. Triggers bring Cal.com booking events into SourCherry, while actions let workflows manage Cal.com bookings from inside an automation.


The integration works in two directions:


Key Benefits of Cal.com Actions & Triggers in Workflows


Cal.com workflow automation helps teams reduce manual scheduling work, respond faster to booking changes, and keep customer communication connected to real booking activity.



Connecting Your Cal.com Account


Connecting from either the workflow step or the Integrations page ensures SourCherry can securely receive Cal.com booking events and call the Cal.com API from workflow actions. Choose the path that best matches your role and setup process.


  1. In SourCherry, open Automation → Workflows and add any Cal.com trigger or action.

→ If Cal.com is not connected, click Connect Now and authenticate using your Cal.com API key, or OAuth where available. Then authorize the workspace and event types SourCherry should access.

→ If Cal.com is already connected, the trigger or action fields load instantly in the workflow step.




  1. Alternate path: Go to Sub-Account Settings → Integrations → Cal.com → Connect.


Cal.com Triggers


Triggers start workflows when specific Cal.com events happen. Use triggers when booking activity in Cal.com should create or update contacts, send messages, branch workflows, assign tasks, or start follow-up sequences.


TriggerWhat it does
Booking CreatedStarts a workflow when a new booking is created in Cal.com and returns the booking payload.
Booking RescheduledStarts a workflow when an existing booking is moved to a new start time and returns previous and updated time details.
Booking CancelledStarts a workflow when a booking is cancelled by the attendee, organizer, or system. Cancellation reason may be available if supplied.
Meeting EndedStarts a workflow at the scheduled end time of the booking. If the booking is rescheduled, the Meeting Ended webhook is re-armed for the updated time.
OOO Created / UpdatedStarts a workflow when an out-of-office entry is created or updated in Cal.com.

Cal.com Actions


Actions let workflows send instructions back to Cal.com. Use actions when SourCherry should create a booking, cancel a booking, reschedule a booking, or look up booking details before another step runs.


ActionPurpose
Create BookingCreates a new booking for a selected Cal.com event type. Required fields include Event Type, Attendee Name, Attendee Email, and Start Time.
Cancel BookingCancels an existing booking by booking ID, with an optional cancellation reason.
Reschedule BookingMoves an existing booking to a new start time. Cal.com handles calendar invite updates and notifications.
Find BookingLooks up a booking by ID, attendee email, or filters and returns matching booking data.


All four Cal.com actions are premium workflow actions. Premium action credits apply when these actions run.


Testing Cal.com Triggers and Actions


Testing confirms that the connection works, the right booking data is available, and downstream workflow steps can map fields correctly. A test should be completed before publishing any workflow that relies on Cal.com booking data.


Test a Cal.com trigger


Step 1: Add the trigger

Step 2: Configure the trigger

Step 3: Test the trigger



Test a Cal.com action


This walkthrough programmatically books a meeting on a host’s calendar from inside a workflow — for instance, after a high-intent form submission.


Step 1: Add the action

Step 2: Configure the action

Step 3: Save and use the output

Click Save action. The new booking’s ID and metadata are exposed as workflow output variables. Chain a Send Email or Send SMS step to confirm the booking to the attendee, or use the booking ID later in a Cancel Booking or Reschedule Booking step if downstream conditions change.



How To Setup Cal.com — Actions & Triggers in Workflows


A clean setup helps ensure booking events enter the workflow correctly and action steps send accurate scheduling instructions back to Cal.com. Start with a simple workflow, confirm the Cal.com connection is active, then add the trigger, action, and follow-up steps needed for your scheduling process.


  1. Go to Automation → Workflows and create a new workflow or open an existing workflow.

  2. Click Add Trigger, go to the Apps tab, search for Cal.com, and select the trigger that matches your goal, such as Booking Created, Booking Rescheduled, Booking Cancelled, or Meeting Ended.



  3. Click the + icon to add the next workflow step, then choose the SourCherry or Cal.com action you want to run after the trigger fires. Use SourCherry actions for CRM updates, messages, tags, tasks, and internal notifications. Use Cal.com actions when the workflow needs to create, find, cancel, or reschedule a Cal.com booking.

  4. To create a booking from the workflow, select Cal.com → Create Booking, then complete the required fields: Event Type, Attendee Name, Attendee Email, and Start Time. Add Attendee Timezone in IANA format, such as America/New_York or Europe/London, when the booking should respect the attendee’s timezone.



  5. Add any remaining follow-up steps, such as sending confirmation messages, adding contact tags, creating internal tasks, branching with If/Else conditions, or logging booking details in the CRM.
  6. Click Save, run a final workflow test, confirm all mapped values populate correctly, then publish the workflow.

Use Cases & Patterns


These workflow patterns help teams turn booking activity into consistent customer communication and internal follow-up. Start with the closest use case, then customize filters, branches, and messages for your process.


Use Case 1: New Booking → CRM Contact + Welcome Sequence


Goal: Turn every new booking into a fully-onboarded contact with the right context attached.


Workflow Setup:


Example: A prospect books a 30-minute discovery call. The workflow creates a contact, tags them as ‘discovery’, sends a personalized prep email, and ensures a reminder fires the day before the call.


Use Case 2: No-Show Recovery


Goal: Auto-recover no-shows without requiring a CSM to track them down.


Workflow Setup:


Example: Whenever a meeting ends, the workflow checks the booking state. If the attendee was a no-show, they get a softening message with a one-click rebook link — instead of falling through the cracks.


Use Case 3: Cancellation Retention


Goal: Treat a cancellation as the start of a save flow, not a dead end.


Workflow Setup:


Example: A prospect cancels their demo because of a calendar conflict. The workflow sends a friendly reschedule message with two pre-filled time options — and tags the contact for CSM follow-up if there’s no rebook within a week.


Use Case 4: Programmatic Scheduling from a Form


Goal: Eliminate the email-back-with-a-booking-link round-trip for high-intent leads.


Workflow Setup:


Example: A lead requests a same-day call via a high-intent form. The workflow books the meeting on the assigned AE’s calendar at the requested slot and confirms it instantly — no manual scheduling, no missed lead.


Use Case 5: Recording Distribution


Goal: Get Cal Video recordings to the right place automatically.


Workflow Setup:


Example: Right after a recording finishes processing, the attendee receives a thank-you email with the recording link and an AI-generated recap — and the CRM activity log captures the same context for the rep.


Best Practices


Following a few setup standards helps reduce mapping errors, timezone issues, and failed booking updates. These practices are especially useful when workflows create or change bookings automatically.



Frequently Asked Questions


Q: Are Cal.com actions premium workflow actions?
Yes. Create Booking, Cancel Booking, Reschedule Booking, and Find Booking are premium workflow actions and consume premium action credits when they run.


Q: What data is available from a Cal.com trigger?
The booking payload can include details such as booking URL, title, start time, end time, notes, event type, attendees, and organizer.


Q: What does Webhook Status mean?
Webhook Status shows whether the underlying Cal.com webhook is active. If the status becomes inactive, reconnect the Cal.com integration.


Q: What timezone format should I use in Create Booking?
Use an IANA timezone format, such as America/New_York or Europe/London. If the field is left blank, Cal.com falls back to the sub-account timezone.


Q: What Start Time format should I use?
Use a standard date-time value. The suggested format is 12-21-2026 08:30 AM, and ISO-8601 values such as 2026-12-21T08:30:00 are also accepted.


Q: Does Cancel Booking notify the attendee?
Yes. Cal.com sends its standard cancellation email, including the cancellation reason if one is supplied.


Q: Will Reschedule Booking send updated calendar invites?
Yes. Cal.com cancels the original calendar event and sends an updated invite for the new time.


Q: Will Booking Created fire again when a booking is rescheduled?
No. Booking Rescheduled is its own trigger. Booking Created does not fire again when an existing booking is rescheduled.


Q: Does the integration work with self-hosted Cal.com?
Self-hosted Cal.com supports the same webhook surface, but some self-hosted setups may have issues with Meeting Started or Meeting Ended behavior. Test with a real booking before relying on it in production.


Q: Can I use workflow variables in Cal.com action fields?
Yes. Inline workflow variables can be used in fields such as Attendee Name, Attendee Email, Start Time, and other fields exposed by the action.