List Event Types: Cal.com action

Sample request

{}

Returns

{
  "data": [
    {
      "id": 456,
      "slug": "30min",
      "title": "30 Minute Meeting",
      "length": 30
    }
  ],
  "status": "success"
}

Use these fields in downstream nodes for routing, logging, or error handling.

FAQ

Questions about List Event Types.

What does the List Event Types action do in Cal.com?

Returns the user's or team's event types with duration, configured availability, payment requirements. Useful for resolving event-type IDs at workflow-build time and for inventorying scheduling-link configuration.

What inputs does List Event Types require?

List Event Types has no required inputs. Sensible defaults are applied if you leave fields blank.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if Cal.com returns an error?

The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does List Event Types support batch operations?

Yes. Run List Event Types inside a Loop node to process arrays. Tiny Command handles Cal.com's rate limits automatically so you don't have to throttle manually.

More actions