Short answer: Drop the "Cal.com → Create Booking" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Event Type ID eventTypeId | string | Required | The event type ID from Cal.com (numeric). Find it in Cal.com → Event Types. |
Start Time start | datetime | Required | ISO 8601 datetime |
Attendee Name attendeeName | string | Required | Attendee Name |
Attendee Email attendeeEmail | string | Required | Attendee Email |
Timezone attendeeTimeZone | string | Optional | Timezone. Example: America/New_York |
Notes notes | string | Optional | Notes |
{"eventTypeId": "{{trigger.eventTypeId}}","start": "{{trigger.start}}","attendeeName": "{{trigger.attendeeName}}","attendeeEmail": "{{trigger.attendeeEmail}}","attendeeTimeZone": "e.g. America/New_York"}
{"data": {"uid": "abc-123","title": "30 Min Meeting","status": "accepted","startTime": "2026-04-15T14:00:00Z"},"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.
Triggered by anything in the catalog. Free tier available. No credit card.