> For the complete documentation index, see [llms.txt](https://mind-expression-docs.gitbook.io/home/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://mind-expression-docs.gitbook.io/home/how-to-guides/integration/google-calendar/google-calendar-use-cases.md).

# Google Calendar: Use Cases

## Integrate with Google Calendar&#x20;

Check, Create, Change, Add, Remove

### Case 1: To check the schedule in google calendar

**1.1. Assistance Scope:**&#x20;

* User: Do I have any meetings today?
* AI: Your google calendar showed you would have {{summary}} with {{attendees}} at {{start.dateTime}} to {{end.dateTime}}.

**1.2. Company Admin Scope:**

* User: Is the meeting room available at {{date\_start}}?
* AI: The meeting room is booked from {{start.dateTime}} to {{end.dateTime}}.\
  It is available for booking at other times.

**1.3. Company Admin Scope:**

* User: Can I deploy to me-demo, right now?
* AI: Sorry, Your google calendar showed you would have {{summary}} at {{start.dateTime}} to {{end.dateTime}}. Please avoid updating me-demo.

### Case 2: To create a schedule in google calendar

**2.1. Secretary Scope:**

User: Can you help me add an event to my calendar?

AI: Of course! What's the title of the event?\
User: {{summary}}

AI: When is the event?\
User: {{date\_start}}\
AI: I have added {{summary}} to your calendar on {{start.dateTime}}.

### Case 3: To delete a schedule in google calendar

**3.1. Secretary Scope:**

* User: Can I cancel a meeting with {{user\_email}} tomorrow at 3 pm?
* AI: Your meeting has been canceled with the following:\
  &#x20;     {{attendees}}

### Case 4: To add people to a schedule in the google calendar

**4.1 Company Admin Scope**

* User: Can you invite {{user\_email}} to the meeting on Monday 9am?
* AI: The meeting you have on Monday 9am is {{meeting\_title}}, is this correct?
* User: Yes
* AI: {{user\_email}} has been added to your meeting: {{title}}.\
  &#x20;     The new list of attendees are: {{attendees}}

### Case 5: To change a schedule in google calendar

**5.1. Administrator Booking Scope:**&#x20;

* User: I want to change my booking on {{from\_date}}.
* AI: Let me check the schedule first!\
  &#x20;    You have schedule on {{from\_date}}.&#x20;

  &#x20;    Title : {{summary}}

  &#x20;    Do you want to change this?&#x20;
* User: Yes&#x20;
* AI: Great! When do you want me to change this schedule?
* User: {{to\_date}}
* AI: Cool! Schedule has been changed! \
  &#x20;    Title : {{summary}}

  &#x20;    Description : {{description}}

  &#x20;    When : {{to\_date}}&#x20;

### Case 6: To check the description of the meeting in google calendar

**6.1. Assistance Scope:**&#x20;

* User: What is the objective of the meeting at {{date}}?
* AI: The objective of the meeting is as below.\
  &#x20;    Title: {{summary}}

  &#x20;    Description: {{description}}

&#x20;    &#x20;

<br>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://mind-expression-docs.gitbook.io/home/how-to-guides/integration/google-calendar/google-calendar-use-cases.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
