Prerequisites
- Glean action must be enabled for your instance and the Google Calendar action pack must be available.
- Ensure a connected Google Calendar account exists for the user. The connected account must have permission in Google Calendar to create events.
- Google Calendar must be connected as a data source for Glean actions.
Supported parameters
| Parameter | Type | Description |
|---|---|---|
| Attendees | Array | List of attendees for the event. |
| Birthday properties | Object | Provider-specific object reserved for configuring birthday-style events, if supported. |
| Calendar ID | String | Identifier of the target calendar where the event will be created. |
| Create meeting room | Boolean | Whether to generate an online meeting link (for example, a video-conferencing room) for this event. |
| Description | String | Longer free-form description or agenda text for the event. |
| Event type | String | Event type value used by the provider (for example, standard meeting vs focus time or out of office, where supported). |
| Event Duration (Hours) | Integer | Number of whole hours in the event duration. |
| Event Duration (Minutes) | Integer | Number of minutes in the event duration, combined with event_duration_hour to get total length. The default duration is 30 minutes. |
| Exclude organizer | Boolean | Whether to exclude the organizer from the attendee list, even though they own the event. |
| Focus time properties | Object | Additional configuration for focus time events when the event type indicates focus time (for example, special visibility or blocking behavior). |
| Guests can invite others | Boolean | Whether guests are allowed to invite additional attendees to the event. |
| Guests can see other guests | Boolean | Whether guests can see the full attendee list on the event. |
| Guests can modify | Boolean | Whether guests are allowed to modify event details such as time, location, or description. |
| Location | String | Human-readable location for the event (for example, a room name or address). |
| Out of office properties | Object | Additional configuration for out-of-office events when the event type indicates out of office. |
| Recurrence | Array | Recurrence rules that define how and when the event repeats (for example, weekly or monthly patterns). |
Usage example
You want to schedule a team planning meeting by first finding available time slots and then creating the event with appropriate settings. Instruction to an agent: “Find a time when Alice, Bob, and Carol are all available next week for a 1-hour meeting, then schedule our Q1 Planning Session with a meeting link. Set it so guests can invite others but cannot modify the event.” Resulting behavior:- Calls Find free slots to identify available time slots for Alice, Bob, and Carol next week.
- Presents available slots to the user and confirms which slot to book.
-
Calls Create event with:
-
Start datetimeset to the selected slot (for example, 2025-01-15T14:00:00). -
Attendeesset to [“[email protected]”, “[email protected]”, “[email protected]”]. -
Summaryset to “Q1 Planning Session”. -
Event Duration (Hours)set to 1. -
Create meeting roomset to true to generate a video conference link. -
Guests can invite othersset to true. -
Guests can modifyset to false.
-
- Creates the calendar event on the connected user’s calendar.
- Automatically includes the event creator in the attendee list.
- Returns the event details including the meeting link.
Event Duration parameters to specify custom meeting lengths, and leverage guest permission flags to control meeting management capabilities.
Troubleshooting
Action not available in a given environment
Action not available in a given environment
- Possible cause: Internal restriction level or beta status prevents the action from being listed in that context.
- Fix: Ask your Glean admin to confirm whether this action is enabled for your tenant and whether your environment is configured to surface beta actions.
FAQs
Is Create event action considered destructive?
Is Create event action considered destructive?
No. Create event is a non-destructive creation action that adds new events without deleting or modifying existing calendar data.