> For the complete documentation index, see [llms.txt](https://university.mindstudio.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://university.mindstudio.ai/building-ai-agents/blocks-reference/create-calendar-event.md). # Create Calendar Event Create a Google Calendar event. ## Configuration ### Account #### Add account Connect your Google Calendar account by signing in with the proper credentials. #### Dynamic (Ask at Runtime) Ask the user to connect their account when the AI agent runs. ### Event Title Add a name for the event. ### Description Add an event description. ### Location Add the physical location or a link to the event. ### Time Add a start time and end time for the event. Make sure to use ISO format (YYYY-MM-DD). ### Attendees At the email addresses for the attendees of the event. Only 1 address per line. ### Output Variable Save the event ID and url as a variable. --- # 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://university.mindstudio.ai/building-ai-agents/blocks-reference/create-calendar-event.md?ask=&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.