Wiresk

Wiresk

Google Calendar – Methods

Estimated reading time: 19 min

What your automation will do…

Google Calendar Google Calendar - Methods

Configuration Table:

Input Options (Field Mapping):

  • Input: Allows dynamic inputs, e.g., from a Trigger or from Step responses. Input tab>uncheck “Show recommended” to see all fields).
  • Default Value: Select value from a defined list or specify a fixed attribute.
  • Manual input: Set a custom value by using the Lightning Bold feature (⚡ icon).

(*) required field

Name* Find Calendar
Connection*Select your Google connection or create one.

MATCHING CRITERIA

Search Key*:

You can:

  • Select a Calendar from the default value.
  • Map the calendar ID with the Input field
  • Enter a summary search (the calendar’s display name, like “Team Schedule”) with the ⚡ icon.

if not Found Consider as*:

Success – When the record is not found during execution, the system does not treat this as an error. Instead, it considers the operation successful and continues with the workflow.

Failed – Wiresk treats this as an error or failure. The workflow stops or takes a predefined failure action.

Sample response 
{
  "kind": "calendar#calendarListEntry",
  "etag": "\"1743861872630895\"",
  "id": "family18177438921175916299@group.calendar.google.com",
  "summary": "Family",
  "timeZone": "UTC",
  "colorId": "15",
  "backgroundColor": "#9fc6e7",
  "foregroundColor": "#000000",
  "selected": true,
  "accessRole": "owner",
  "defaultReminders": [
    {
      "method": "popup",
      "minutes": 30
    },
    {
      "method": "email",
      "minutes": 10
    }
  ],
  "conferenceProperties": {
    "allowedConferenceSolutionTypes": [
      "hangoutsMeet"
    ]
  }
}

Configuration Table:

Input Options (Field Mapping):

  • Input: Allows dynamic inputs, e.g., from a Trigger or from Step responses. Input tab>uncheck “Show recommended” to see all fields).
  • Default Value: Select value from a defined list or specify a fixed attribute.
  • Manual input: Set a custom value by using the Lightning Bold feature (⚡ icon).

(*) required field

Name* Create Calendar
Connection*Select your Google connection or create one.
MAP FIELDS + Add Field ↓
Additional fields to configure the Method.

Time Zone:

The time zone of the calendar. (Formatted as an IANA Time Zone Database name, e.g. “Europe/Zurich”.) Optional.

Description:

Description of the calendar.

Location:

Geographic location of the calendar as free-form text.

Summary*:

Title of the new calendar.

Sample response 
{
  "kind": "calendar#calendarListEntry",
  "etag": "\"1743861872630895\"",
  "id": "family18177438921175916299@group.calendar.google.com",
  "summary": "Family",
  "timeZone": "UTC",
  "colorId": "15",
  "backgroundColor": "#9fc6e7",
  "foregroundColor": "#000000",
  "selected": true,
  "accessRole": "owner",
  "defaultReminders": [
    {
      "method": "popup",
      "minutes": 30
    },
    {
      "method": "email",
      "minutes": 10
    }
  ],
  "conferenceProperties": {
    "allowedConferenceSolutionTypes": [
      "hangoutsMeet"
    ]
  }
}

Configuration Table:

Input Options (Field Mapping):

  • Input: Allows dynamic inputs, e.g., from a Trigger or from Step responses. Input tab>uncheck “Show recommended” to see all fields).
  • Default Value: Select value from a defined list or specify a fixed attribute.
  • Manual input: Set a custom value by using the Lightning Bold feature (⚡ icon).

(*) required field

Name* Update Calendar
Connection*Select your Google connection or create one.

MATCHING CRITERIA

Calendar ID*:

Choose the Calendar to update.

Or Map the calendar ID.

MAP FIELDS + Add Field ↓
Additional fields to configure the Method.

Summary:

New title of the calendar.

Time Zone:

The time zone of the calendar. (Formatted as an IANA Time Zone Database name, e.g. “Europe/Zurich”.) Optional.

Description:

Description of the calendar.

Location:

Geographic location of the calendar as free-form text.

Sample response 
{
  "kind": "calendar#calendar",
  "etag": "\"M1nOXquMkR8DmzdnQNhEIMY-mBI\"",
  "id": "100c2fc7868d7d42cb9da8dcff79d0b39b80defdd7d19656c4ccba3e6c62bea7@group.calendar.google.com",
  "summary": "update summary",
  "description": "update description",
  "location": "update location",
  "timeZone": "Europe/Zurich",
  "conferenceProperties": {
    "allowedConferenceSolutionTypes": [
      "hangoutsMeet"
    ]
  }
}

Configuration Table:

Input Options (Field Mapping):

  • Input: Allows dynamic inputs, e.g., from a Trigger or from Step responses. Input tab>uncheck “Show recommended” to see all fields).
  • Default Value: Select value from a defined list or specify a fixed attribute.
  • Manual input: Set a custom value by using the Lightning Bold feature (⚡ icon).

(*) required field

Name* Delete Calendar
Connection*Select your Google connection or create one.

MATCHING CRITERIA

Calendar ID*:

Choose the Calendar to delete.

Or Map the calendar ID.

Sample response 
{
  "delete": "the calendar has been deleted succesfully"
}
Google Calendar Google Calendar - Methods

Configuration Table:

Input Options (Field Mapping):

  • Input: Allows dynamic inputs, e.g., from a Trigger or from Step responses. Input tab>uncheck “Show recommended” to see all fields).
  • Default Value: Select value from a defined list or specify a fixed attribute.
  • Manual input: Set a custom value by using the Lightning Bold feature (⚡ icon).

(*) required field

Name* Find Event
Connection*Select your Google connection or create one.

MATCHING CRITERIA

Calendar ID*:

Choose the Calendar that contain the event.

Or Map the calendar ID.

Search Key*:

You can:

  • Select an event from the default value.
  • Map the event ID with the Input field or Provide the event ID.
  • Enter name of the event (must be an exact match) with the ⚡ icon.

if not Found Consider as*:

Success – When the record is not found during execution, the system does not treat this as an error. Instead, it considers the operation successful and continues with the workflow.

Failed – Wiresk treats this as an error or failure. The workflow stops or takes a predefined failure action.

Sample response 
{
  "kind": "calendar#event",
  "etag": "\"3506159663194750\"",
  "id": "2ho74gc2pk1rrhvsq42mi4ibih",
  "status": "confirmed",
  "htmlLink": "https://www.google.com/calendar/event?eid=MmhvNzRnYzJwazFycmh2c3E0Mm1pNGliaWggMTAwYzJmYzc4NjhkN2Q0MmNiOWRhOGRjZmY3OWQwYjM5YjgwZGVmZGQ3ZDE5NjU2YzRjY2JhM2U2YzYyYmVhN0Bn",
  "created": "2025-07-21T06:37:11.000Z",
  "updated": "2025-07-21T06:37:11.597Z",
  "summary": "test1",
  "creator": {
    "email": "user@gmail.com"
  },
  "organizer": {
    "email": "100c2fc7868d7d42cb9da8dcff79d0b39b80defdd7d19656c4ccba3e6c62bea7@group.calendar.google.com",
    "displayName": "method wiresk",
    "self": true
  },
  "start": {
    "date": "2025-07-22"
  },
  "end": {
    "date": "2025-07-23"
  },
  "transparency": "transparent",
  "iCalUID": "2ho74gc2pk1rrhvsq42mi4ibih@google.com",
  "sequence": 0,
  "reminders": {
    "useDefault": false
  },
  "eventType": "default"
}

Configuration Table:

Input Options (Field Mapping):

  • Input: Allows dynamic inputs, e.g., from a Trigger or from Step responses. Input tab>uncheck “Show recommended” to see all fields).
  • Default Value: Select value from a defined list or specify a fixed attribute.
  • Manual input: Set a custom value by using the Lightning Bold feature (⚡ icon).

(*) required field

Name* Create Event
Connection*Select your Google connection or create one.

MATCHING CRITERIA

Calendar ID*:

Choose the Calendar in which you want to create the event.

Or Map the calendar ID.

When Event Overlap*:

Consider action when event is overlapping with others.

  • Ignore event creation
  • Allow overlap event creation
  • Consider failed when event overlap
MAP FIELDS + Add Field ↓
Additional fields to configure the Method.

Anyone can add self

True – False – Whether anyone can invite themselves to the event (deprecated).

Attendees omitted

True – False

  • If True, the event is created as a solo event.
  • No invitations are sent to other people.
  • The event appears only in the creator’s calendar (the calendar selected in the “Calendar” field).

Color Id

The color of the event. This is an ID referring to an entry in the event section of the colors definition (see the colors endpoint).

  • Color ID is a string number from 1 to 11, each corresponding to a different preset Google Calendar color.
  • It overrides the calendar’s default event color, making it easier to visually distinguish events.
  • If omitted, the event uses the calendar’s default color.

Color list:

  • 1-Lavender-Default
  • 2-Sage
  • 3-Grape
  • 4-Flamingo
  • 5-Banana
  • 6-Tangerine
  • 7-Peacock
  • 8-Graphite
  • 9-Blueberry
  • 10-Basil
  • 11-Tomato

Conference Data

The conference-related information, such as details of a Google Meet conference:

By setting “Create request” Conference solution key → set to hangoutsMeet and Request ID → a unique string (e.g., event-123), this alone will generate a Google Meet link automatically and attach it to your event. All other fields can be omitted.

  • When enabled and properly configured, a link appears in the calendar invite under “Join with Google Meet.”
  • Attendees will see the link in their invitation and can join the meeting directly.

Note: In “Create Request“, if you choose Add On as the conference solution key type, you may need to manually configure the rest of these fields depending on the third-party provider’s API. Google expects the add-on provider to fill them, but if you’re constructing manually via Wiresk, you might have to simulate that structure.

+ Add Field ↓
Fields to configure the conference data

Conference ID

The unique ID provided by the third-party system.

Conference solution

+ Add Field ↓
Fields to configure the conference solution

Icon uri

A logo or icon URL

Key

Usually used for internal linking, e.g., Zoom’s solution ID.

Name

Display name of the provider (e.g., Zoom)

Create request

+ Add Field ↓
Fields to configure the Create request

Conference solution key

Choose :

Hangouts Meet (Google Meet): the default built-in video conferencing solution in Google Calendar.

Use this if:

  • Your Google account supports Meet.
  • You want Wiresk to auto-generate a Google Meet link.

Add On (for3P conference providers): This is used for third-party conferencing providers (like Zoom, Cisco WebEx, etc.) that have been integrated via Google Workspace Add-ons.

Use this only if:

  • Your Google Workspace admin has installed a third-party conferencing add-on (via G Suite Marketplace).
  • You are generating events with custom conferencing solutions provided by that add-on.

Request ID

A unique ID for the request. You can enter any string (e.g., event-12345).

Status

  • Pending
  • Success
  • Failure

Entry points

These define how attendees join the meeting:

+Element +Map ↓
(Add a repeating group of fields or Map it from an array. See Field Mapping).

Element 1: Represents the first entry point.

Access code:

If required for joining.

Entry point type:

  • Video
  • Phone
  • SIP
  • More

Label:

Description like “Zoom Meeting”.

Meeting code:

If required for joining.

Passcode:

If required for joining.

Password:

If required for joining.

PIN:

If required for joining.

URI:

Join URL (e.g., https://zoom.us/j/123456789)

Notes

Any join instructions.

Signature

Verification hash (typically auto-generated by the provider).

Description

Additional text or agenda for the event. Appears in the event details panel.

Guests Can invite others

True – False – If true, guests can add others.

Guests can modify

True – False – Allows guests to change the event (time, location, etc.).

Guests can see other guests

True – False – Controls whether invitees can see the full guest list.

ID

Custom ID for the event. Optional. If you provide one, it must be unique across all events in the calendar.

Location

Physical or virtual location of the event. Accepts a free-text address or meeting room name.

Organizer

Used to define the event organizer (host). Normally, this is auto-filled based on the authenticated user. But you can specify it:

+ Add Field ↓
Fields to configure the Organizer

Display name

Shown in the event.

Email

Address of the organizer (must match connected account or be authorized).

ID

Google Calendar user ID.

Self

True – False – indicates if this organizer is the current user.

Original start time

It marks the initial scheduled start time of a specific instance of a recurring event.

It is used only when modifying or canceling an individual occurrence in a recurring series.

For normal (non-recurring) events, this field is ignored.

You don’t use it when:

  • Creating a new single event.
  • Creating a full recurring series with RRULE.
+ Add Field ↓
Fields for configuration
  • Date
  • Date time
  • Time zone

Private Copy

True – False – If true, the event is a private copy for the user (others won’t see it).

Recurrence (RRULE, EXRULE, RDATE and EXDATE)

Supports these rule types:

  • RRULE: Repeating logic
  • EXRULE: Exclusion rule
  • RDATE: Include extra specific dates
  • EXDATE: Exclude specific dates

Can be entered as plain text or array.

Repeat TypeRRULE ExampleMeaning
Every day, 5 timesRRULE:FREQ=DAILY;COUNT=5Daily for 5 occurrences
Every week on MondayRRULE:FREQ=WEEKLY;BYDAY=MOWeekly, on Mondays
Monthly on 1stRRULE:FREQ=MONTHLY;BYMONTHDAY=1Every 1st of the month
Until specific dateRRULE:FREQ=WEEKLY;UNTIL=20250831T000000ZRepeat weekly until August 31, 2025
Every weekdayRRULE:FREQ=WEEKLY;BYDAY=MO,TU,WE,TH,FRRepeat Monday to Friday

You can also add:

  • EXDATE: to exclude specific dates
    Example: EXDATE:20250801T100000Z
  • RDATE: to include specific extra dates
    Example: RDATE:20250805T100000Z,20250812T100000Z

Reminders

+ Add Field ↓
Fields to configure the Reminders

Overrides

Each override defines a custom reminder:

+Element +Map ↓
(Add a repeating group of fields or Map it from an array. See Field Mapping).

Element 1: Represents the first override

Method

email, popup

Minutes

how many minutes before the event

Example: popup 10 → shows 10 min before

Use default

True – False – If true, uses calendar’s default reminders.

Sequence

Version number of the event (used for syncing).

Source

A link to a source webpage or external system where the event was created.

+ Add Field ↓
Fields for configuration

Title

Source title

URL

A link associated with the event (used in source field).

Status

Choose the status of the event:

confirmed, tentative, or cancelled.

Transparency

  • opaque: blocks calendar time (default).
  • transparent: does not block time (free slot).

Visibility

default, public, or private. Controls how visible it is to others.

Attachments

Let you attach Google Drive files.

Google requires the file to be shared with attendees or publicly visible.

+Element +Map ↓
(Add a repeating group of fields or Map it from an array. See Field Mapping).

Element 1: Represents the first attachment.

File ID

From Drive.

File URL

Link to the file.

Icon link

Optional, for visual.

Mime type

Type of the file:

File TypeMIME Type
PDFapplication/pdf
Word Documentapplication/vnd.openxmlformats-officedocument.wordprocessingml.document
Excel Sheetapplication/vnd.openxmlformats-officedocument.spreadsheetml.sheet
Image (JPEG)image/jpeg
Image (PNG)image/png
Google Docapplication/vnd.google-apps.document
Google Sheetapplication/vnd.google-apps.spreadsheet
Google Slidesapplication/vnd.google-apps.presentation
Text Filetext/plain

Title

Display name in event.

Attendees

+Element +Map ↓
(Add a repeating group of fields or Map it from an array. See Field Mapping).

Element 1: Represents the first attendee.

Additional guest

Extra Guest count.

Comment

Internal comment.

Display name

Friendly name.

Email*

who you’re inviting.

Optional

True -False – not required to attend.

Organizer

True -False – If this guest is the organizer.

Resource

true → if the attendee is a calendar resource, such as a meeting room, projector, or shared equipment.

Google Calendar treats resources as non-human attendees with limited availability that can be reserved.

Examples:

  • room-a@yourdomain.com
  • projector-1@yourdomain.com

If you mark the attendee with resource: true, Google will check if the resource is available and block out its time accordingly.

Response status

needsAction, accepted, declined, tentative.

Self

True – False – Whether the attendee is the current user.

Summary*

The title of the event. This is what appears in the calendar block.

All Day Event*:

Yes – No

Start*:

Date & Time*:

Define when the event starts

End*:

Date & Time*:

Define when the event end

Sample response 
{
  "kind": "calendar#event",
  "etag": "\"3506159663194750\"",
  "id": "2ho74gc2pk1rrhvsq42mi4ibih",
  "status": "confirmed",
  "htmlLink": "https://www.google.com/calendar/event?eid=MmhvNzRnYzJwazFycmh2c3E0Mm1pNGliaWggMTAwYzJmYzc4NjhkN2Q0MmNiOWRhOGRjZmY3OWQwYjM5YjgwZGVmZGQ3ZDE5NjU2YzRjY2JhM2U2YzYyYmVhN0Bn",
  "created": "2025-07-21T06:37:11.000Z",
  "updated": "2025-07-21T06:37:11.597Z",
  "summary": "test1",
  "creator": {
    "email": "user@gmail.com"
  },
  "organizer": {
    "email": "100c2fc7868d7d42cb9da8dcff79d0b39b80defdd7d19656c4ccba3e6c62bea7@group.calendar.google.com",
    "displayName": "wiresk",
    "self": true
  },
  "start": {
    "date": "2025-07-22"
  },
  "end": {
    "date": "2025-07-23"
  },
  "transparency": "transparent",
  "iCalUID": "2ho74gc2pk1rrhvsq42mi4ibih@google.com",
  "sequence": 0,
  "reminders": {
    "useDefault": false
  },
  "eventType": "default"
}

Configuration Table:

Input Options (Field Mapping):

  • Input: Allows dynamic inputs, e.g., from a Trigger or from Step responses. Input tab>uncheck “Show recommended” to see all fields).
  • Default Value: Select value from a defined list or specify a fixed attribute.
  • Manual input: Set a custom value by using the Lightning Bold feature (⚡ icon).

(*) required field

Name* Update Event
Connection*Select your Google connection or create one.

MATCHING CRITERIA

Calendar ID*:

Choose the Calendar that contain the event.

Or Map the calendar ID.

Event ID*:

Choose the event to update.

Or Map the event ID.

When Event Overlap*:

Consider action when event is overlapping with others.

  • Ignore event creation
  • Allow overlap event creation
  • Consider failed when event overlap
MAP FIELDS + Add Field ↓
Additional fields to configure the Method.

Anyone can add self

True – False – Whether anyone can invite themselves to the event (deprecated).

Attachments

Let you attach Google Drive files.

Google requires the file to be shared with attendees or publicly visible.

+Element +Map ↓
(Add a repeating group of fields or Map it from an array. See Field Mapping).

Element 1: Represents the first attachment.

File ID

From Drive.

File URL

Link to the file.

Icon link

Optional, for visual.

Mime type

Type of the file:

File TypeMIME Type
PDFapplication/pdf
Word Documentapplication/vnd.openxmlformats-officedocument.wordprocessingml.document
Excel Sheetapplication/vnd.openxmlformats-officedocument.spreadsheetml.sheet
Image (JPEG)image/jpeg
Image (PNG)image/png
Google Docapplication/vnd.google-apps.document
Google Sheetapplication/vnd.google-apps.spreadsheet
Google Slidesapplication/vnd.google-apps.presentation
Text Filetext/plain

Title

Display name in event.

Attendees

+Element +Map ↓
(Add a repeating group of fields or Map it from an array. See Field Mapping).

Element 1: Represents the first attendee.

Additional guest

Extra Guest count.

Comment

Internal comment.

Display name

Friendly name.

Email*

who you’re inviting.

Optional

True -False – not required to attend.

Organizer

True -False – If this guest is the organizer.

Resource

true → if the attendee is a calendar resource, such as a meeting room, projector, or shared equipment.

Google Calendar treats resources as non-human attendees with limited availability that can be reserved.

Examples:

  • room-a@yourdomain.com
  • projector-1@yourdomain.com

If you mark the attendee with resource: true, Google will check if the resource is available and block out its time accordingly.

Response status

needsAction, accepted, declined, tentative.

Self

True – False – Whether the attendee is the current user.

Attendees omitted

True – False

  • If True, the event is created as a solo event.
  • No invitations are sent to other people.
  • The event appears only in the creator’s calendar (the calendar selected in the “Calendar” field).

Color Id

The color of the event. This is an ID referring to an entry in the event section of the colors definition (see the colors endpoint).

  • Color ID is a string number from 1 to 11, each corresponding to a different preset Google Calendar color.
  • It overrides the calendar’s default event color, making it easier to visually distinguish events.
  • If omitted, the event uses the calendar’s default color.

Color list:

  • 1-Lavender-Default
  • 2-Sage
  • 3-Grape
  • 4-Flamingo
  • 5-Banana
  • 6-Tangerine
  • 7-Peacock
  • 8-Graphite
  • 9-Blueberry
  • 10-Basil
  • 11-Tomato

Conference Data

The conference-related information, such as details of a Google Meet conference:

By setting “Create request” Conference solution key → set to hangoutsMeet and Request ID → a unique string (e.g., event-123), this alone will generate a Google Meet link automatically and attach it to your event. All other fields can be omitted.

  • When enabled and properly configured, a link appears in the calendar invite under “Join with Google Meet.”
  • Attendees will see the link in their invitation and can join the meeting directly.

Note: In “Create Request“, if you choose Add On as the conference solution key type, you may need to manually configure the rest of these fields depending on the third-party provider’s API. Google expects the add-on provider to fill them, but if you’re constructing manually via Wiresk, you might have to simulate that structure.

+ Add Field ↓
Fields to configure the conference data

Conference ID

The unique ID provided by the third-party system.

Conference solution

+ Add Field ↓
Fields to configure the conference solution

Icon uri

A logo or icon URL

Key

Usually used for internal linking, e.g., Zoom’s solution ID.

Name

Display name of the provider (e.g., Zoom)

Create request

+ Add Field ↓
Fields to configure the Create request

Conference solution key

Choose :

Hangouts Meet (Google Meet): the default built-in video conferencing solution in Google Calendar.

Use this if:

  • Your Google account supports Meet.
  • You want Wiresk to auto-generate a Google Meet link.

Add On (for3P conference providers): This is used for third-party conferencing providers (like Zoom, Cisco WebEx, etc.) that have been integrated via Google Workspace Add-ons.

Use this only if:

  • Your Google Workspace admin has installed a third-party conferencing add-on (via G Suite Marketplace).
  • You are generating events with custom conferencing solutions provided by that add-on.

Request ID

A unique ID for the request. You can enter any string (e.g., event-12345).

Status

  • Pending
  • Success
  • Failure

Entry points

These define how attendees join the meeting:

+Element +Map ↓
(Add a repeating group of fields or Map it from an array. See Field Mapping).

Element 1: Represents the first entry point.

Access code:

If required for joining.

Entry point type:

  • Video
  • Phone
  • SIP
  • More

Label:

Description like “Zoom Meeting”.

Meeting code:

If required for joining.

Passcode:

If required for joining.

Password:

If required for joining.

PIN:

If required for joining.

URI:

Join URL (e.g., https://zoom.us/j/123456789)

Notes

Any join instructions.

Signature

Verification hash (typically auto-generated by the provider).

Description

Additional text or agenda for the event. Appears in the event details panel.

Start

Date & Time*:

Define when the event starts

End

Date & Time*:

Define when the event end

Guests Can invite others

True – False – If true, guests can add others.

Guests can modify

True – False – Allows guests to change the event (time, location, etc.).

Guests can see other guests

True – False – Controls whether invitees can see the full guest list.

ID

Custom ID for the event. Optional. If you provide one, it must be unique across all events in the calendar.

Location

Physical or virtual location of the event. Accepts a free-text address or meeting room name.

Organizer

Used to define the event organizer (host). Normally, this is auto-filled based on the authenticated user. But you can specify it:

+ Add Field ↓
Fields to configure the Organizer

Display name

Shown in the event.

Email

Address of the organizer (must match connected account or be authorized).

ID

Google Calendar user ID.

Self

True – False – indicates if this organizer is the current user.

Original start time

It marks the initial scheduled start time of a specific instance of a recurring event.

It is used only when modifying or canceling an individual occurrence in a recurring series.

For normal (non-recurring) events, this field is ignored.

You don’t use it when:

  • Creating a new single event.
  • Creating a full recurring series with RRULE.
+ Add Field ↓
Fields for configuration
  • Date
  • Date time
  • Time zone

Private Copy

True – False – If true, the event is a private copy for the user (others won’t see it).

Recurrence (RRULE, EXRULE, RDATE and EXDATE)

Supports these rule types:

  • RRULE: Repeating logic
  • EXRULE: Exclusion rule
  • RDATE: Include extra specific dates
  • EXDATE: Exclude specific dates

Can be entered as plain text or array.

Repeat TypeRRULE ExampleMeaning
Every day, 5 timesRRULE:FREQ=DAILY;COUNT=5Daily for 5 occurrences
Every week on MondayRRULE:FREQ=WEEKLY;BYDAY=MOWeekly, on Mondays
Monthly on 1stRRULE:FREQ=MONTHLY;BYMONTHDAY=1Every 1st of the month
Until specific dateRRULE:FREQ=WEEKLY;UNTIL=20250831T000000ZRepeat weekly until August 31, 2025
Every weekdayRRULE:FREQ=WEEKLY;BYDAY=MO,TU,WE,TH,FRRepeat Monday to Friday

You can also add:

  • EXDATE: to exclude specific dates
    Example: EXDATE:20250801T100000Z
  • RDATE: to include specific extra dates
    Example: RDATE:20250805T100000Z,20250812T100000Z

Reminders

+ Add Field ↓
Fields to configure the Reminders

Overrides

Each override defines a custom reminder:

+Element +Map ↓
(Add a repeating group of fields or Map it from an array. See Field Mapping).

Element 1: Represents the first override

Method

email, popup

Minutes

how many minutes before the event

Example: popup 10 → shows 10 min before

Use default

True – False – If true, uses calendar’s default reminders.

Sequence

Version number of the event (used for syncing).

Source

A link to a source webpage or external system where the event was created.

+ Add Field ↓
Fields for configuration

Title

Source title

URL

A link associated with the event (used in source field).

Status

Choose the status of the event:

confirmed, tentative, or cancelled.

Summary

The title of the event. This is what appears in the calendar block.

Transparency

  • opaque: blocks calendar time (default).
  • transparent: does not block time (free slot).

Visibility

default, public, or private. Controls how visible it is to others.

All Day Event*:

Yes – No

Sample response 
{
  "kind": "calendar#event",
  "etag": "\"3507877248336990\"",
  "id": "2ho74gc2pk1rrhvsq42mi4ibih",
  "status": "confirmed",
  "htmlLink": "https://www.google.com/calendar/event?eid=MmhvNzRnYzJwazFycmh2c3E0Mm1pNGliaWggMTAwYzJmYzc4NjhkN2Q0MmNiOWRhOGRjZmY3OWQwYjM5YjgwZGVmZGQ3ZDE5NjU2YzRjY2JhM2U2YzYyYmVhN0Bn",
  "created": "2025-07-21T06:37:11.000Z",
  "updated": "2025-07-31T05:10:24.168Z",
  "summary": "update2",
  "creator": {
    "email": "wiresk@gmail.com"
  },
  "organizer": {
    "email": "100c2fc7868d7d42cb9da8dcff79d0b39b80defdd7d19656c4ccba3e6c62bea7@group.calendar.google.com",
    "displayName": "wiresk",
    "self": true
  },
  "start": {
    "date": "2025-07-22"
  },
  "end": {
    "date": "2025-07-23"
  },
  "transparency": "transparent",
  "iCalUID": "2ho74gc2pk1rrhvsq42mi4ibih@google.com",
  "sequence": 0,
  "reminders": {
    "useDefault": false
  },
  "eventType": "default"
}

Configuration Table:

Input Options (Field Mapping):

  • Input: Allows dynamic inputs, e.g., from a Trigger or from Step responses. Input tab>uncheck “Show recommended” to see all fields).
  • Default Value: Select value from a defined list or specify a fixed attribute.
  • Manual input: Set a custom value by using the Lightning Bold feature (⚡ icon).

(*) required field

Name* Delete Event
Connection*Select your Google connection or create one.

MATCHING CRITERIA

Calendar ID*:

Choose the Calendar that contain the event.

Or Map the calendar ID.

Event ID*:

Choose the event to delete.

Or Map the event ID.

Sample response 
{
  "delete": "the event has been deleted succesfully"
}
Google Calendar Google Calendar - Methods

Configuration Table:

Input Options (Field Mapping):

  • Input: Allows dynamic inputs, e.g., from a Trigger or from Step responses. Input tab>uncheck “Show recommended” to see all fields).
  • Default Value: Select value from a defined list or specify a fixed attribute.
  • Manual input: Set a custom value by using the Lightning Bold feature (⚡ icon).

(*) required field

Name* Create ACL
Connection*Select your Google connection or create one.

MATCHING CRITERIA

Calendar ID*:

Choose the Calendar in which you want to create the ACL.

Or Map the calendar ID.

MAP FIELDS

Role*:

The role assigned to the scope. Possible values are:

  • “owner” – Provides ownership of the calendar. This role has all of the permissions of the writer role with the additional ability to manipulate ACLs.
  • “none” – Provides no access.
  • “free Busy Reader” – Provides read access to free/busy information.
  • “reader” – Provides read access to the calendar. Private events will appear to users with reader access, but event details will be hidden.
  • “writer” – Provides read and write access to the calendar. Private events will appear to users with writer access, and event details will be visible. Provides read access to the calendar’s ACLs.

Scope*:

Type*:

The type of the scope. Possible values are:

  • “default” – The public scope. This is the default value.
  • “user” – Limits the scope to a single user.
  • “group” – Limits the scope to a group.
  • “domain” – Limits the scope to a domain.

Note: The permissions granted to the “default“, or public, scope apply to any user, authenticated or not.

+ Add Field ↓
Additional fields to configure the Scope

Email Address

The email address of a user or group, or the name of a domain, depending on the scope type. Omitted for type “default“.

Sample response 
{
  "kind": "calendar#aclRule",
  "etag": "\"00001753945421481199\"",
  "id": "default",
  "scope": {
    "type": "default",
    "value": "__public_principal__@public.calendar.google.com"
  },
  "role": "reader"
}

Configuration Table:

Input Options (Field Mapping):

  • Input: Allows dynamic inputs, e.g., from a Trigger or from Step responses. Input tab>uncheck “Show recommended” to see all fields).
  • Default Value: Select value from a defined list or specify a fixed attribute.
  • Manual input: Set a custom value by using the Lightning Bold feature (⚡ icon).

(*) required field

Name* Update ACL
Connection*Select your Google connection or create one.

MATCHING CRITERIA

Calendar ID*:

Choose the Calendar that contain the Rule ACL.

Or Map the calendar ID.

Rule ID*:

ACL rule identifier.

Choose the Rule to update.

Or Map it ID.

MAP FIELDS

Role*:

The role assigned to the scope. Possible values are:

  • “owner” – Provides ownership of the calendar. This role has all of the permissions of the writer role with the additional ability to manipulate ACLs.
  • “none” – Provides no access.
  • “free Busy Reader” – Provides read access to free/busy information.
  • “reader” – Provides read access to the calendar. Private events will appear to users with reader access, but event details will be hidden.
  • “writer” – Provides read and write access to the calendar. Private events will appear to users with writer access, and event details will be visible. Provides read access to the calendar’s ACLs.

Scope*:

Type*:

The type of the scope. Possible values are:

  • “default” – The public scope. This is the default value.
  • “user” – Limits the scope to a single user.
  • “group” – Limits the scope to a group.
  • “domain” – Limits the scope to a domain.

Note: The permissions granted to the “default“, or public, scope apply to any user, authenticated or not.

+ Add Field ↓
Additional fields to configure the Scope

Email Address

The email address of a user or group, or the name of a domain, depending on the scope type. Omitted for type “default“.

Sample response 
{
  "kind": "calendar#aclRule",
  "etag": "\"00001753945421481199\"",
  "id": "default",
  "scope": {
    "type": "default",
    "value": "__public_principal__@public.calendar.google.com"
  },
  "role": "reader"
}

Configuration Table:

Input Options (Field Mapping):

  • Input: Allows dynamic inputs, e.g., from a Trigger or from Step responses. Input tab>uncheck “Show recommended” to see all fields).
  • Default Value: Select value from a defined list or specify a fixed attribute.
  • Manual input: Set a custom value by using the Lightning Bold feature (⚡ icon).

(*) required field

Name* Delete ACL
Connection*Select your Google connection or create one.

MATCHING CRITERIA

Calendar ID*:

Choose the Calendar that contain the Rule ACL.

Or Map the calendar ID.

Rule ID*:

ACL rule identifier.

Choose the Rule to delete.

Or Map it ID.

Sample response 
{
  "kind": "calendar#aclRule",
  "etag": "\"00001753945421481199\"",
  "id": "default",
  "scope": {
    "type": "default",
    "value": "__public_principal__@public.calendar.google.com"
  },
  "role": "reader"
}

Once your Flow is configured, you can test or automate it using the Run panel or by managing Triggers from the Flow Management screen.

  • Run Flow: Manually runs the Flow once using sample data. Ideal for testing logic and field mapping. See How to Run a Flow.
  • Run Scheduler: Force-runs the Trigger immediately using live input. This bypasses the recurrence rule and is useful for verifying real data mapping. Learn more in Wiresk Scheduler – The Fundamentals.

From the Trigger management panel (clock icon), you can:

  • Activate or deactivate Triggers
  • Force-run the scheduler
  • Copy Routing Keys (for HTTP Triggers)

If your Flow uses a Webhook Trigger, it runs automatically on each incoming webhook—no scheduler required. It remains active until you manually deactivate it.