List Event Types: Calendly action

Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

Field	Type	Required	Description
User URI user_uri	string	Required	User URI. e.g. "https://api.calendly.com/users/ABCDEF123"
Active Only active	options	Optional	Active Only. Options: Active, All

Sample request

{
  "user_uri": "https://api.calendly.com/users/ABCDEF123",
  "active": "{{trigger.active}}"
}

Returns

{
  "collection": [
    {
      "uri": "https://api.calendly.com/event_types/ET123",
      "name": "30 Min Meeting",
      "slug": "30-min",
      "active": true,
      "duration": 30
    }
  ]
}

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 Calendly?

Lists available event types (meeting templates) for the user, with their booking URLs and durations. Used to populate a meeting-type picker.

What inputs does List Event Types require?

Required: User URI. Every input accepts a static value or a variable from any upstream node in your workflow.

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 Calendly 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 Calendly's rate limits automatically so you don't have to throttle manually.

More actions