> For the complete documentation index, see [llms.txt](https://docs.dapta.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dapta.ai/dapta-docs-es/flow-studio/nodes/nodo-google-calendar.md).

# Nodo Google Calendar

- [Conectar tu Cuenta](https://docs.dapta.ai/dapta-docs-es/flow-studio/nodes/nodo-google-calendar/conectar-tu-cuenta.md): Crea tus credenciales de Google Calendar en Dapta: conecta tu cuenta de Gmail desde Credentials y autoriza el acceso para usarla en tus flujos.
- [Acción Get Event](https://docs.dapta.ai/dapta-docs-es/flow-studio/nodes/nodo-google-calendar/accion-get-event.md): Usa la acción Get Event del nodo Google Calendar para obtener todos los eventos de una cuenta en un período de fechas y zona horaria definidos.
- [Acción Get Availavility](https://docs.dapta.ai/dapta-docs-es/flow-studio/nodes/nodo-google-calendar/accion-get-availavility.md): Usa la acción Get Availability de Google Calendar para consultar la disponibilidad de un calendario en un rango de fechas, con zona horaria configurable.
- [Acción Create Event](https://docs.dapta.ai/dapta-docs-es/flow-studio/nodes/nodo-google-calendar/accion-create-event.md): Usa la acción Create Event del nodo Google Calendar para crear un evento con fecha y hora de inicio y fin, incluyendo los asistentes correspondientes.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.dapta.ai/dapta-docs-es/flow-studio/nodes/nodo-google-calendar.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.