1. Get Slots - Return slots for one day.

1. Get Slots For One Date - Get slots for the indicated date. The action will return slots of the indicated date if the date is corresponding to the completed day field from the Weekly Pattern Executer.

2. Get Slots For Range - Get slots for the indicated range of dates.

json
[
    {"_p_Start Slot":1637132400000,"_p_Stop Slot":1637135100000},
    {"_p_Start Slot":1637136000000,"_p_Stop Slot":1637138700000},
    {"_p_Start Slot":1637139600000,"_p_Stop Slot":1637142300000},
    {"_p_Start Slot":1637146800000,"_p_Stop Slot":1637149500000},
    {"_p_Start Slot":1637150400000,"_p_Stop Slot":1637153100000},
    {"_p_Start Slot":1637157600000,"_p_Stop Slot":1637160300000},
    {"_p_Start Slot":1637161200000,"_p_Stop Slot":1637163900000},
    {"_p_Start Slot":1637164800000,"_p_Stop Slot":1637167500000},
    {"_p_Start Slot":1637168400000,"_p_Stop Slot":1637171100000}
]

1. Authorize - Do a redirect to the Google Access grant page.

1. Slot - This data call is used to specify Slot Type fields for plugin elements.
Returns:

Title	Description	Type
Start Slot	Indicates the beginning of the slot.	date
Stop Slot	Indicates the end of the slot.	date

2. Get Google Calendar Events - This data call is used to get list of Google Calendar events.



Fields:

Title	Description	Type
Calendar Id	The calendar ID from Google Calendar. Use the “Get Google Calendar List” call to get all available calendars.	text
Api Key	The API Key from Google. Use here the “API Key” state from the “Google Access” element.	text
Date	Date for events in "yyyy-mm-dd" format. e.g. 2023-05-29	text
Hash	The random text.	text
Authorization	The call authorization. Use the “Bearer ” + “access token” state from the “Google Access” element.	text

Returns:
Please consult this Google documentation.

3. Get Google Calendar List - Get the list of available calendars from Google Calendar.



Fields:

Title	Description	Type
Authorization	The call authorization. Use the “Bearer ” + “access token” state from the “Google Access” element.	text

Returns:
Please consult this Google documentation.

1. Create Google Calendar Event - Create a Google Calendar event.



Fields:

Title	Description	Type
Calendar Id	The calendar ID from Google Calendar. Use the “Get Google Calendar List” call to get all available calendars.	text
Authorization	The call authorization. Use the “Bearer ” + “access token” state from the “Google Access” element.	text
Start Time	The start time for the event into the "yyyy-mm-ddThh:mm:ssZ" format. e.g. 2023-05-29T09:00:00Z.	text
End Time	The end time for the event into the "yyyy-mm-ddThh:mm:ssZ" format. e.g. 2023-05-29T11:00:00Z.	text
Title	The title of the event.	text
Description	The description of the event.	text

Returns:
Please consult this Google documentation.

2. Create Webhook - Create a Google Calendar webhook.
❗
For this action need to create a backend workflow.
⌛
Created webhook is available for 7 days. After this time need to create another webhook.



Fields:

Title	Description	Type
Calendar Id	The calendar ID from Google Calendar. Use the “Get Google Calendar List” call to get all available calendars.	text
Authorization	The call authorization. Use the “Bearer ” + “access token” state from the “Google Access” element.	text
URL	The address where notifications are delivered for this channel.	text
Channel ID	A UUID or similar unique string that identifies this channel. This value is used for deleting an existing webhook.	text

Returns:
Please consult this Google documentation.

3. Delete Webhook - Delete an existing webhook.
Fields:

Title	Description	Type
Authorization	The call authorization. Use the “Bearer ” + “access token” state from the “Google Access” element.	text
Resource ID	An opaque ID that identifies the resource being watched on this channel. Stable across different API versions. Search this value in the results of the “Create Webhook” action.	text
Channel ID	A UUID or similar unique string that identifies this channel. Search this value in the results of the “Create Webhook” action.	text

Returns:
This call returns nothing.

1. The One Day Pattern Generator element is placed on the page with the following completed fields.

2. Also, on the page, is placed Text element with the One Day Pattern Generator pattern state.

3. To have access to the List of Slots states, on the page, used the Get today slots button.

4. In the workflow, when this button is clicked then is called the Get Slots element action. After this action, the List of Slots states will be available from the One Day Pattern Generator element.

5. The List of Slots states are listed, so these are used in two Repeating Group elements.

1. On the page, it is placed the Weekly Pattern Executer and 7 One Day Pattern Generator elements with the following completed fields.

2. To have access to element states, on the page, are used Get Time Slots for date and Get Time Slots for date range buttons.

3. In the workflow, when the Get Time Slots for date button is clicked then is called the Get Slots For One Date element action. After this action, just the List of slots state will be available from the Weekly Pattern Executer element.

4. The List of slots state is a list, so this is used in the Repeating group element.

5. In the workflow, when the Get Time Slots for date range button is clicked then is called the Get Slots For Range element action. After this action, just the List of slots for a range state will be available from the Weekly Pattern Executer element.

7. The List of slots for a range state from the Weekly Pattern Executer element is used in the Repeating Group element because it is a list.

1. On the page, it is placed Interval Generator element with the following completed fields.

2. Also, on the page, is placed Text element with Interval Generator interval state.

1. On the page, it is placed an Google Access element.

2. On the page, it is placed an element for click listener.

3. In the workflow, when Auth with Google is clicked is called the Authorize action.

4. In the workflow, when Google Access Access token is ready workflow is added. This workflow set list of available calendars in a custom state.

1. On the page, a Dropdown element is used to list all available calendar IDs.

2. On the page, it is placed an element for click listener.

3. In the workflow, when Add listener for calendar is clicked is called the Create Webhook action.

4. In the backend, it is created a “google_hook” workflow.





⚠️
The backend workflow needs to be initialized first. Please read steps 4 - 12 from this documentation to learn how to initialize a backend workflow.