Skip to main content
Returns a URL to open in a browser. Calendly has no credential a request body can carry, so connecting one is two steps: ask for this URL, let the customer consent, and Roark finishes the rest server-side (it exchanges the code, verifies the credential, reads the account’s own timezone when none was given, and stores the connection). Nothing is created until the customer consents, and a link that is not used expires. Read the result with GET /v1/integrations/calendar?provider=CALENDLY.
Calls POST /v1/integrations/calendar/calendly/authorize-url

Options

string
Reconnect an existing connection instead of creating one: the consent screen replaces that connection’s credential in place, so every tool bound to it keeps working. Use this when a connection reports INVALID_CREDENTIALS. The connection’s existing name and timezone are kept, so label is ignored when this is set.
string
Customer-facing name for the connection, unique within the project. Required unless calendarConnectionId is set, and decided now because the consent screen has nowhere to carry it.
string
The named IANA timezone to offer slots in, for example America/Los_Angeles. Omit to adopt the Calendly account’s own. A fixed offset such as -08:00 is rejected: it does not observe DST.

Example

Every command also takes the global options and sets one of the exit codes.