List Schedules: Cal.com action

Sample request

{}

Returns

{
  "data": [
    {
      "id": 1,
      "name": "Working Hours",
      "timeZone": "America/New_York",
      "isDefault": true
    }
  ],
  "status": "success"
}

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

FAQ

Questions about List Schedules.

What does the List Schedules action do in Cal.com?

Returns the user's configured working-hours schedules. Useful for syncing availability across tools or for "what days/hours am I bookable?" introspection workflows.

What inputs does List Schedules require?

List Schedules 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 Schedules support batch operations?

Yes. Run List Schedules 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