Cal.com
Schedule and manage Cal.com bookings, event types, slots and webhooks.
OCNORA ships 15 typed Cal.com operations and 1 trigger. Each node has a schema-driven form, input and output tables beside its settings, and is pre-flighted by Workflow Health before your first real run. Endpoints not covered by a typed node are called at https://api.cal.com through the HTTP node with the same credential.
Before you connect Cal.com
- Authentication
- API key
- Credential
- the Cal.com API key (cal_live_… / cal_test_…)the Cal.com API key (cal_live_… / cal_test_…), or {"api_key": "…"}
- Connection test
- Available: the stored credential can be checked against the provider when you add it. This is not a record that a test was run or passed.
- Prerequisites
- Publishing needs MANTLE_APP_PUBLIC_BASE_URL set to a URL Cal.com can reach. Cal.com's cloud accepts https only and refuses private or loopback addresses; a self-hosted instance also accepts http.
Prerequisites are taken from the connection notes in this provider’s node contracts; each node’s reference page says which apply to it.
What you can do with Cal.com
Operations, grouped by what they do to your data, plus 1 trigger that start a run.
Create and send 1
Read and search 8
Update 1
Delete and cancel 2
Other operations 3
A sample Cal.com workflow
- 1Booking Eventtrigger.cal_bookingStart a run when Cal.com raises a booking event — created, rescheduled, cancelled, confirmed, or a meeting starting or ending.
- 2Get Bookingcal.get_bookingFetch one booking by its uid, or every occurrence when the uid names a recurring booking.
- 3Cancel Bookingcal.cancel_bookingCancel a booking, or one seat of a seated booking, with an optional reason shown to the attendee.
An outline built from this provider’s node contracts, not a recorded run. Each step’s output fields are available to the next in the field picker.
Every node below has a reference page: what it does, the connection it needs, its config fields with types, constraints and examples, and the shapes it emits.
Operations 15
- Cancel BookingCancel a booking, or one seat of a seated booking, with an optional reason shown to the attendee.cal.cancel_booking
- Confirm BookingAccept a booking that is waiting for confirmation on an event type that requires it.cal.confirm_booking
- Create BookingBook a slot on an event type for an attendee, returning the booking Cal.com created.cal.create_booking
- Decline BookingReject a booking that is waiting for confirmation, with an optional reason for the requester.cal.decline_booking
- Delete WebhookRetire one webhook by id. Webhooks that trigger.cal_booking created are removed on unpublish already; this is for the rest.cal.delete_webhook
- Get BookingFetch one booking by its uid, or every occurrence when the uid names a recurring booking.cal.get_booking
- Get Event TypeFetch one event type in full by its numeric id.cal.get_event_type
- Get My ProfileFetch the Cal.com profile the API key belongs to — useful for resolving the username and default schedule a later node needs.cal.get_me
- List BookingsList one cursor page of bookings, optionally narrowed to a single status, attendee, event type, team or time window.cal.list_bookings
- List Event TypesList the bookable event types, optionally narrowed to one username, slug or organisation.cal.list_event_types
- List SchedulesList the availability schedules on the account the key belongs to.cal.list_schedules
- List Available SlotsList the free slots an event type offers between two dates, grouped by date the way Cal.com returns them.cal.list_slots
- List WebhooksList the account's webhooks with their signing secrets removed, so a workflow can audit what is subscribed without handling credentials.cal.list_webhooks
- Mark No-ShowRecord that the host or named attendees did not turn up for a booking.cal.mark_absent
- Reschedule BookingMove a booking to a new start time; Cal.com cancels the old booking and returns the new one, which has its own uid.cal.reschedule_booking
Cal.com questions
- How does OCNORA authenticate with Cal.com?
- With a stored API key credential, shaped the Cal.com API key (cal_live_… / cal_test_…) or the Cal.com API key (cal_live_… / cal_test_…), or {"api_key": "…"}. A connection test can check it when you add it.
- What can I automate with Cal.com?
- 15 typed operations and 1 trigger, each with a reference page listing its config fields and the shapes it emits.
- What if the Cal.com operation I need is not listed?
- Call https://api.cal.com from the HTTP node with the same credential, or describe the step to the AI builder, which asks our team for a typed node when one is missing.
- Are there templates that use Cal.com?
- Not yet. Start from a blank workflow, or describe the workflow to Build with AI.
- How are Cal.com calls controlled?
- Every call and every run step is audited, runs count against the execution budget, and Workflow Health pre-flights the workflow when you save it.
More in Business apps
See your first Cal.com workflow run.
Book a technical demo. We add the connection, pick a template or describe the workflow to Build with AI, and Workflow Health checks it before it runs.