Get Event: 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
Event URI eventUri	string	Required	Event URI

Sample request

{
  "eventUri": "{{trigger.eventUri}}"
}

Returns

{
  "resource": {
    "uri": "https://api.calendly.com/scheduled_events/abc123",
    "name": "30 Minute Meeting",
    "status": "active",
    "end_time": "2026-04-15T14:30:00Z",
    "start_time": "2026-04-15T14:00:00Z"
  }
}

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

FAQ

Questions about Get Event.

What does the Get Event action do in Calendly?

Returns details of a scheduled Calendly event with start/end time, event type, and location. Used to enrich a trigger payload before posting downstream.

What inputs does Get Event require?

Required: Event 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 Get Event support batch operations?

Yes. Run Get Event 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