Cal.com
Cal.com scheduling platform integration. Manages bookings (create, get, list, cancel, reschedule), event types (list, create, update), schedules (list, create), and availability slots (get available). Supports API Key authentication with optional custom base URL for self-hosted instances. All nodes accept either a Client ID from Connect or direct credentials.
| Namespace | Robomotion.CalCom |
| Version | 1.1.0 |
| Category | Calendar, Automation & Workflow |
| Nodes | 14 |
Nodes
| Node | Description |
|---|---|
| Connect | Opens a connection to Cal.com and returns a Client ID. |
| Disconnect | Closes a Cal.com connection. |
| Create Booking | Creates a booking in Cal.com. |
| Get Booking | Gets a booking in Cal.com. |
| List Bookings | Lists bookings in Cal.com. |
| Cancel Booking | Cancels a booking in Cal.com. |
| Reschedule Booking | Reschedule Booking — see the properties below. |
| List Event Types | Lists event types in Cal.com. |
| Create Event Type | Creates an event type in Cal.com. |
| Update Event Type | Updates an event type in Cal.com. |
| Get Available Slots | Gets available slots in Cal.com. |
| List Schedules | Lists schedules in Cal.com. |
| Create Schedule | Creates a schedule in Cal.com. |
| Toolkit | Exposes this package's operations to an AI Agent as a single tool. |
Connecting
This package has a Connect node. Run it once at the start of your flow; it returns a Client ID that the other nodes take as input. Pair it with Disconnect so the connection is released when the flow ends.
Credentials belong in a Vault rather than typed into the node.
AI Agent tools
13 of these nodes are exposed as tools an AI Agent can call directly:
Connect, Disconnect, Create Booking, Get Booking, List Bookings, Cancel Booking, Reschedule Booking, List Event Types, Create Event Type, Update Event Type, Get Available Slots, List Schedules, Create Schedule.
Generated from the package spec that the Flow Designer itself loads, so the node list and every property below match the version above exactly.
It does not yet include worked examples or service-specific guidance — those are written by hand, and a plausible-sounding guess in a reference page is worse than an honest gap. If you build something useful with this package, the community is the place to share it.