Skip to main content
Returns a URL to open in a browser. Google 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 that both calendar permissions were granted, 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=GOOGLE.
Calls POST /v1/integrations/calendar/google/authorize-url

​
Options

​
string
required
Customer-facing name for the connection, unique within the project. 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 Google account’s own. A fixed offset such as -08:00 is rejected: it does not observe DST.
​
string
The Google account to preselect on the consent screen. A hint only: it is ignored if the user is signed into another account, and nothing is authorized by it.

​
Example

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