Note: 

  • Use and transfer of information received from Google APIs to any other app will adhere to Google API Services User Data Policy, including the Limited Use requirements.

  • In accordance with the Nintex Privacy Policy, Nintex Services do not retain any information obtained from third party services.

Google Calendar - Get Calendars

Use the Google Calendar - Get Calendars action A tool for building the processes, logic, and direction within workflows. Actions are the steps the workflow performs to complete a process. to return a list of calendars for the account specified when configuring the connection.

For more information about the Google Calendar connector A software component that allows seamless integration with third-party services, business applications, and content stores. Examples include Salesforce, Box, and Microsoft SharePoint. Connectors are used to create connections required for workflow actions and start events., go to Google Calendar.

Before you begin: 

Jump to:

Configure the Google Calendar - Get Calendars action

  1. Add the action to the workflow and open the action configuration panel. For more information, see Add an action to the workflow.

  1. Select a Connection. If you do not have a connection, see Add a connection.
  2. In Calendars, select or insert a variable to store the list of calendars.

Google Calendar - Get Calendars action fields, buttons, and settings

Section

Field

Description

Variable types

(Unlabeled)

Connection Credentials and other settings that enables workflows to communicate with external systems, services, or applications. It's required to pass data between the workflow and the indicated service, which could be a cloud service, business application, or content store.

The Google Calendar connection to use for retrieving the list of calendars for the account used when configuring the connection.

To refresh the available connections, click .

(n/a)

Output

Calendars

The variable to store the retrieved list of calendars. At most, 250 calendars are returned.
The output result is a Calendars collection containing the following data for each calendar:

  • ID: (Text) A unique ID for the calendar.
  • Summary: (Text) The title of the calendar
  • Description: (Text) Description of the calendar.
  • Time zone: (Text) The time zone linked to the calendar in the IANA Time Zone Database format, for example: Europe/Zurich. See the Wikipedia article List of tz database time zones for more info on time zone database names
  • Access role: (Text) The access role that the user has on the calendar. For example:
    • freeBusyReader: The user can read free/busy information
    • owner: The user can read and modify events and access control lists
    • reader: The user has read access to the calendar, but details for private events are hidden
    • writer: The user can read and modify events, and private event details are visible
  • Primary: (Boolean) The value returned is true or false, indicating if the calendar is the user's primary calendar

Object