Meeting prep brief in your inbox
Each weekday morning, the agent reads your recent emails with today's outside guests and emails you one short prep brief.
Letaido's Google Calendar integration lets an AI agent read and book your meetings, then act on them in 64 other apps.
Checked step by step. Open one to watch it run.
Each weekday morning, the agent reads your recent emails with today's outside guests and emails you one short prep brief.
Ask in plain words, and the agent finds the first time you and a teammate are both open, then books it with a Meet link.
Every morning, the agent logs yesterday's meetings with customers and prospects as Salesforce events on the matching contact and account.
Every morning, the agent puts upcoming publish dates from your Notion content calendar on a shared Google Calendar and moves the ones that changed.
Every Monday, the agent checks your late-stage Salesforce deals against the team's calendars and posts the ones with no meeting booked in Slack.
Every Friday, the agent reads next week on your shared marketing calendar and posts each event with its day, time and organizer.
Six ways to connect Google Calendar, and where each one fits.
| Option | Set up by asking | Works across your apps | Runs on its own | No code | Connects thousands of apps |
|---|---|---|---|---|---|
| Yes | Yes | Yes | Yes | No | |
| Calendar sync and iCal links | No | No | Yes | Yes | Partly |
| Google Workspace Marketplace add-ons | No | Partly | Yes | Yes | Partly |
| Zapier, Make and similar | No | Yes | Yes | Partly | Yes |
| Google Calendar API | No | Partly | Partly | No | Partly |
| Google Calendar MCP server | Yes | No | Partly | Partly | No |
| Option | How it works | Best for | Watch out for |
|---|---|---|---|
| Letaido AI agent | You describe the job. The agent reads and books meetings, and uses 64 other apps, on a schedule or when you ask. | Meeting logs, prep briefs and booking that need a judgement call. | 65 apps, not thousands. Calendar changes can't start a job; it runs on a schedule or when you ask. |
| Calendar sync and iCal links | Sign in with Google in another calendar app, or paste a calendar's secret iCal address for a read-only view. | Seeing one calendar inside Outlook or Apple Calendar. | It shows events. It doesn't act on them. |
| Google Workspace Marketplace add-ons | Add-ons such as Zoom for Google Workspace work inside Calendar. | Adding a tool's features to the Calendar screen. | Each add-on does one tool's job. |
| Zapier, Make and similar | Workflows built from Calendar triggers and actions, like a new or updated event, or an event ending. | Fixed handoffs, such as a form entry into a calendar event. | You build and fix one workflow per job. |
| Google Calendar API | Developers call the API from their own code with an OAuth client in a Google Cloud project. | In-house tools with exact needs. | Needs developers to build and keep it running. |
| Google Calendar MCP server | Google's remote MCP server lets AI apps like Claude and Google Antigravity list, create and update events. | Checking and booking time while you chat. | In Developer Preview: needs the preview program and a Google Cloud project. |
Connect Google Calendar once. After that, you describe each job in plain English.
Allow all read operations once per app; approve each kind of write once.
Save it to run every weekday.
A schedule starts the job, or you do by asking.
Click Connect with Google Calendar in Letaido and approve Google's consent screen. No Cloud project needed.
To use your own Google Cloud project, create an OAuth client and a refresh token, then paste the client ID, secret and token. Set the consent screen to In production or Internal.
Jobs read the calendars the connected account can see. Share team calendars with that account first.
Allow all read operations once per app; approve each kind of write once. Then save it to repeat.
8 actions: read, find open time, create, update, move and delete events.
Click Connect with Google Calendar and approve Google's consent screen. If you'd rather use your own Google Cloud OAuth client, paste its client ID, client secret and refresh token, and set the consent screen to In production or Internal: tokens minted in Testing expire after 7 days.
No. Google Calendar has no trigger in Letaido, so calendar jobs run on a schedule, like every weekday at 8am, or when you ask.
Only if the job asks for it. Events it creates or changes notify nobody by default; the booking job above sends invites because the request says so.
Yes. Ask in a chat, and it finds the first time everyone is open and books it, with a Google Meet link if you want one. It can only check calendars shared with you.
Yes. Google runs a remote Calendar MCP server for AI apps like Claude and Google Antigravity, in Developer Preview. Letaido is not an MCP server. It has its own Google Calendar connector, mixes it with your other apps, and runs jobs on a schedule.
Allow all read operations once per app; approve each kind of write once.
In Zapier you build one workflow per job from fixed triggers and actions. With Letaido you describe the job, and the agent decides what to do, like which meetings are worth logging. It connects 65 apps, not thousands.
Connect Google Calendar, then ask for a job like "Email me a meeting prep brief each weekday morning". Leta gets it done on your schedule, or the moment you ask.
Get LetaidoCreate new calendar events with optional attendees, Google Meet links, and full event details.
List and filter events within a time window or fetch full details of a single event including attendee RSVP statuses.
Edit an existing event's title, time, location, guests, or status, or move it to a different calendar.
Permanently delete a calendar event.
Find times when all the chosen calendars are open, within working hours.
Retrieve all calendars the connected account can access, including their IDs, timezones, and permission levels.