ActionCalendlyUpdated September 2026

How do I get my Calendly user URI?

Short answer: You can get current user in Calendly by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Calendly Get Current User action to a workflow, map its 0 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

Get Current User in Calendly — start free All 5 Calendly actions

Get Current User in Calendly — start free

Sample request

{}

Returns

{
  "resource": {
    "uri": "https://api.calendly.com/users/ABCDEF123",
    "name": "John Doe",
    "email": "john@example.com",
    "timezone": "America/New_York"
  }
}

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

Triggered by

Apps that pair well as the trigger for Get Current User.

Any of these apps can fire this action as part of a workflow.

Google Sheets → Calendly

2 Google Sheets triggers

HubSpot → Calendly

18 HubSpot triggers

FAQ

Questions about Get Current User.

What does the Get Current User action do in Calendly?

Returns the authenticated user's info, including the user URI required for most other Calendly API calls. Standard connection-check action.

What inputs does Get Current User require?

Get Current User 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 Calendly returns an error?

The run history shows the failed step with its input and the error message Calendly returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.

Does Get Current User support batch operations?

Run Get Current User inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within Calendly's rate limits.

More actions