Short answer: You can cancel booking in Cal.com by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Cal.com Cancel Booking action to a workflow, map its 2 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Booking UID bookingUid | string | Required | Booking UID. Example: abc-123-def-456 |
Reason cancellationReason | string | Optional | Reason |
{"bookingUid": "e.g. abc-123-def-456","cancellationReason": "{{trigger.cancellationReason}}"}
{"data": {"uid": "abc-123","status": "cancelled"},"status": "success"}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.