FeaturedPersonal Productivity#Google Meet#Google Calendar#Booking#Invitations#Scheduling

Book a Calendar with Me

Accept a visitor email and selected time, recheck your calendar, then create a Google Meet event and email the invitation from your connected account.

Workflow at a glance

The full canvas, before you import it

Click any node to see its config.

#Google Meet#Google Calendar#Booking#Invitations#Scheduling

Click a node to select it — same as the Heym editor; the panel shows its settings.

6 nodes · Free & source-available

Book a Calendar with Me

A visitor chooses a time from your availability and enters their email address. This workflow checks the selected range again, creates an event in your Google Calendar with a Google Meet conference, and asks Google to send the visitor a calendar invitation. The visitor does not need to connect a Google account to Heym.

What this workflow does

  1. BookingRequest accepts email, startTime, endTime, title and description.
  2. CheckSelectedTime reads free/busy data for exactly the selected range.
  3. SlotStillFree continues only when that range contains no busy periods. If the time is occupied, TimeUnavailable asks the visitor to choose again and no invitation is created.
  4. CreateInvitation creates a Calendar event with Meet conferencing using the owner's connected account. Google sends an invitation to $BookingRequest.email.
  5. BookingResult returns the event ID, Meet URL and conference creation status.

Setup

  1. Follow the Google Meet credential setup and connect your own Google account with Calendar events and availability permissions.
  2. Select the same Google Meet credential on CheckSelectedTime and CreateInvitation. Keep both calendar IDs at primary and set both time zones to your IANA zone.
  3. Use Available Time Slots to show your current availability in your own booking interface. Split free intervals into the meeting duration and working hours you offer.
  4. Submit the visitor's email and chosen start/end ISO datetimes to this workflow. Include explicit offsets, for example 2026-11-10T14:00:00+01:00 and 2026-11-10T14:30:00+01:00. Replace these example dates with an available future time.
  5. Set your invitation title and description in the inputs. The default title is Meet with me.

For a workflow API call, the request body can contain:

{"email":"visitor@example.com","startTime":"2026-11-10T14:00:00+01:00","endTime":"2026-11-10T14:30:00+01:00","title":"Meet with me","description":"Introductory call"}

Invitation and availability behavior

The organizer is the Google account behind your credential, while the visitor email is only an attendee. Google is called with sendUpdates=all, so the visitor receives an invitation. Their Calendar settings determine when that invitation appears in their calendar. The event's description, title and time range are included in the invitation.

The selected range must be positive and no longer than 60 calendar days. A free/busy read and event creation are separate requests, so this recheck reduces stale selections but does not lock a time against simultaneous bookings. If your booking application needs strict reservations, coordinate those requests there. This template is a workflow behind your booking interface, not a hosted booking page.

Meet creation may initially be pending: the event exists while Google finishes creating its link. The output includes conference_status as well as meet_url. Use the returned Calendar event ID for later update or cancellation with the same Google Meet node.

How to import this template

  1. 1Click Import → Copy JSON on this page.
  2. 2Open your Heym and navigate to a workflow canvas.
  3. 3Press Cmd+V / Ctrl+V — nodes appear instantly.
  4. 4Add your API keys in the node config panels and click Run.
More workflow templates
View all templates
Heym
incident analysis · production AI
Observed across 100s of AI rollouts

AI workflows don't fail because of prompts.
They fail because of orchestration.

symptom · glue code01
5 tools
Scripts, vector DB, approval bot, tracing, browser runner — none of them talk.
symptom · visibility02
~0%
Observable behavior across the stack. Debugging is guesswork.
with heym · one runtime▲
1 canvas
Agents, RAG, HITL, MCP, traces & evals. Self-hosted. Observable.
AI-Native RuntimeProduction-Grade
github.com/heymrun/heym