> ## Documentation Index
> Fetch the complete documentation index at: https://docs.fetchhive.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Google Calendar

> Configure a workflow step that creates, lists, finds, and updates Google Calendar events using a connected account

Use **Google Calendar** when you want a workflow step to create events, list upcoming meetings, find events, or update calendar entries from a connected account.

## Configuration

| Option              | Required | Description                                                                                                                                                                                              |
| ------------------- | -------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Name                | No       | Label for the step in the workflow canvas.                                                                                                                                                               |
| Authentication      | Yes      | The connected Google Calendar account to use for this step.                                                                                                                                              |
| Action              | Yes      | The calendar action to perform (for example Create Event, List Events, Find Event, Update Event).                                                                                                        |
| Arguments           | Yes      | Per-action form fields generated from the action's schema. Each text field has an **Insert Variable** button for injecting `{{placeholder}}` values. A **Raw JSON** tab is available for advanced usage. |
| When the step fails | No       | Controls whether the workflow should **Terminate Workflow** or **Continue** if this step fails.                                                                                                          |

Before you configure this step, connect Google Calendar in **Integrations** for your workspace using the OAuth flow. If no active connection is available, the step shows a warning with a link to **Integrations** instead of the account selector.

## Arguments form

When you select an action, the **Arguments** section automatically renders a form driven by the action's input schema. Each field includes:

* A label and description from the action's schema.
* An **Insert Variable** button next to eligible fields that injects references like `{{step_1.output.id}}` at the cursor position.
* Validation feedback inline if a required field is left empty.

Switch to the **Raw JSON** tab for power users or when you prefer to write the full arguments object by hand. Changes in either tab stay in sync.

## Common actions

| Action                         | Description                                                            |
| ------------------------------ | ---------------------------------------------------------------------- |
| Create Event                   | Create a new calendar event with title, time, attendees, and location. |
| List Events from All Calendars | List upcoming events across calendars.                                 |
| Find Event                     | Search for an event by criteria such as time range or text.            |
| Get Event                      | Retrieve a single event by ID.                                         |
| Update Event                   | Modify an existing event.                                              |
| Free Busy Query                | Check availability across calendars for scheduling.                    |

Destructive actions such as deleting calendars or events are not exposed in the workflow action picker.

## Output

This step stores the Google Calendar API response as the step output. The shape of the response depends on the action.

Use the full output reference in later steps:

```text theme={null}
{{STEP_IDENTIFIER.output}}
```

For example, after a **Create Event** step you might reference the new event ID:

```text theme={null}
{{step_2.output.id}}
```

## Example

1. Open **Integrations** and connect Google Calendar if you have not already done that.
2. Add a **Google Calendar** step to your workflow.
3. Select a connected account in **Authentication**.
4. Choose **Create Event** in **Action**.
5. In the **Arguments** form, fill in the event title, start time, and end time. Use **Insert Variable** to reference an earlier step's output for any field value.
6. Click **Run** in the step header to test the action, then review the returned payload in **Output**.

## Notes

* This step depends on a connected Google Calendar integration in your workspace.
* The workflow action picker shows a curated subset of calendar actions. Agents with the Google Calendar tool can access the full toolkit.
* OAuth may show third-party authorization branding during the connect flow.

## Using Google Calendar as an Agent Tool

You can also add Google Calendar as a tool in the **Agent Editor**. Open the agent, click **Add tool**, and select **Google Calendar**. In the tool settings panel, choose the connected account the agent should use. The agent will call calendar actions automatically during conversations when relevant.

See also: [Integrations](../../../workspace/integrations), [Creating and Editing](../../creating-and-editing), and [Testing and Iteration](../../testing-and-iteration)