List Events: 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	Your Calendly user URI (get via /users/me). Format: https://api.calendly.com/users/XXXX
Start After min_start_time	string	Optional	ISO 8601 date — only events starting after this
Start Before max_start_time	string	Optional	ISO 8601 date — only events starting before this
Status status	options	Optional	Status. Options: Active, Canceled
Count count	string	Optional	Number of events to return (max 100)

Sample request

{
  "user_uri": "https://api.calendly.com/users/ABCDEF123",
  "min_start_time": "e.g. 2025-01-15T00:00:00Z",
  "max_start_time": "e.g. 2025-02-15T00:00:00Z",
  "status": "{{trigger.status}}",
  "count": "20"
}

Returns

{
  "collection": [
    {
      "uri": "https://api.calendly.com/scheduled_events/EVT123",
      "name": "30 Min Meeting",
      "status": "active",
      "end_time": "2025-01-20T10:30:00.000000Z",
      "start_time": "2025-01-20T10:00:00.000000Z"
    }
  ],
  "pagination": {
    "count": 20,
    "next_page_token": null
  }
}

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

FAQ

Questions about List Events.

What does the List Events action do in Calendly?

Lists scheduled events for the authenticated Calendly user with filters for date range and status. Used for daily-roster emails or for syncing into a BI tool.

What inputs does List Events 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 Events support batch operations?

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