Find a free slot and send the Google Calendar invite

Google Calendar in MadMax answers two questions a workflow keeps asking: when is this person free, and can you put something on their calendar. free_busy returns the busy blocks between two instants, and the gaps are the free time an AI step or a code step can pick a slot from. create_event sends real invites to every attendee, so the workflow can finish the scheduling job rather than hand it back, and an approval step can sit in front of it when the slot commits someone's time. Everything works on the primary calendar of the account you connect. There are no calendar triggers, so these runs start from a schedule, an inbound email, a form, a webhook or another app's event; for "new event" polling, the watch trigger fires once per unseen event id from list_events. Describe it in plain English and MadMax builds the workflow, runs the availability check against your actual calendar, and previews the invite before any attendee gets an email.

What teams build

• An email trigger receives a meeting request, an AI agent extracts the requested window and duration, free_busy checks the next five working days, a second agent picks the earliest gap that fits, and create_event sends the invite while a send email step confirms the time to the requester.
• A 7 a.m. schedule lists today's events, an AI summarize step turns them into three lines (first meeting, the one that needs prep, the gap for lunch), and a send text step delivers it to your verified phone.
• A hosted form collects a candidate's email and preferred days, an agent proposes a slot from the interviewer's free_busy, an approval posts the proposal to Slack with one-click buttons, and only on approve is the event created and the candidate invited; a later submission moves it with update_event.

How it connects

One click. Press Connect on the Google Calendar card in Settings → connectors and approve the calendar permission on Google's consent screen. MadMax stores the grant encrypted and refreshes the access token before it expires; nobody sees the token afterwards, and a revoked grant shows a reconnect button that re-authorizes the same connection. Connections are per workspace, private to you or shared with the team, and each calendar step chooses which account it acts on. See managing connections.

Related

• Email trigger
• Schedule trigger
• Approval step
• Managing connections
• Gmail automation