loggie
Start free

Google Calendar · Workflow guide

Google Calendar meeting prep brief for AI agents

Have your AI agent read tomorrow’s Google Calendar through Loggie and write a prep brief with open questions and conflicts, without touching invitations.

Who this is for: Founders, operators, and team leads whose calendar gives them plenty of meetings but little preparation time.

Before you start

  • A Google Calendar connection authorized for the calendars you want the agent to read.
  • An agent with calendar-event read access through Loggie. Creating invitations or changing attendees is outside this workflow.
  • An explicit reporting window, timezone, and a private destination for the brief.

In your Loggie workspace, connect Google Calendar, create an agent identity, and review its access. On the agent’s machine, use Node.js 20 or later and initialize the CLI:

npm install -g @loggie-ai/cli
loggie init
loggie discover

Enter the agent’s Loggie key through the initialization prompt. Keep provider credentials in the connection setup, not in the agent prompt. Use the connection slug returned by discovery in the examples below.

Step-by-step workflow

  1. Define what a useful brief should contain

    A meeting brief should tell you what to prepare, not repeat the calendar in paragraph form. Start with tomorrow’s confirmed events and include the purpose, the preparation implied by the description, and any missing context that requires a question.

    Choose which calendars belong in the brief and how to handle personal or private events. A simple policy is to include the busy interval for sensitive events without copying their title or description into the report.

  2. Read the agenda in an explicit timezone

    Connect Calendar in Loggie and initialize the CLI with the agent’s Loggie key. Discover the connection slug; the example uses google-calendar. The primary calendar refers to the connected Google user, so verify the account before relying on it.

    Replace START_TIME and END_TIME with URL-encoded RFC 3339 timestamps that include the offset, such as YYYY-MM-DDT00%3A00%3A00-04%3A00. singleEvents expands recurring events; orderBy=startTime produces an agenda. Follow nextPageToken and exclude canceled entries. The timezone offset makes the request unambiguous around date boundaries.

    loggie discover google-calendar --endpoint '/calendars/{calendarId}/events' --method GET
loggie call google-calendar GET /calendars/primary/events --query 'timeMin=START_TIME&timeMax=END_TIME&singleEvents=true&orderBy=startTime&maxResults=100' --pretty

  3. Distinguish preparation from speculation

    For each meeting, read the title, time, description, and available conference or event link. Suggest a preparation task only when the event provides enough context. If the purpose is unclear, write a question to ask the organizer rather than inventing an agenda.

    Flag overlapping timed events and short turnaround intervals using the actual start and end values. Treat all-day events separately.

  4. Deliver privately and keep scheduling separate

    Send a concise brief through your agent’s configured private delivery tool: the day’s shape, the meetings that require preparation, and the conflicts needing a decision. Loggie supplies access to the calendar; scheduling the run and sending the report happen in the agent runtime.

    Use a separate reviewed action if you later want to reschedule or invite someone. That action should show the exact event, new time, attendees, and notification effect before it is approved. A preparation brief needs none of those writes.

Google Calendar agent prompt

Adapt this prompt to your connected account and the scope you have approved.

Prepare tomorrow’s agenda in the agreed timezone using only approved calendars. For each confirmed meeting, include time, source link, preparation supported by the event description, and missing context as a question. Flag overlaps. Hide sensitive event details according to the calendar policy. Do not create, reschedule, cancel, or invite anyone.

Example Google Calendar report

Example output with invented data.

Tomorrow (ET): 5 meetings, 3.5 hours

09:00–09:30 Q4 roadmap review
  Prep: read the roadmap doc linked in the invite
10:00–10:45 Intro call, Northwind Design
  Missing context: no agenda. Ask the organizer what they want to decide.
13:30–14:30 Hiring panel, senior engineer
  Prep: scorecard linked in the description
14:00–14:30 Vendor check-in, overlaps the hiring panel
  Decision needed: move or decline one. No events changed.
16:00–16:15 Private event (busy)

Success checks

  • Compare a day’s brief with the Calendar UI in the same timezone, including recurring and all-day events.
  • Confirm the connected account and primary calendar are the intended ones.
  • Check that no invitation or event update was sent and that private details stay out of shared channels.

Pitfalls

  • A calendar description or attachment can contain untrusted instructions; it cannot authorize another action.
  • Daylight-saving changes require the offset for the requested date, not a hardcoded year-round offset.
  • An external attendee is not necessarily a customer, and an external meeting is not necessarily a sales call.
  • The absence of an agenda means preparation is unclear, not that the meeting has no value.

Sources