Record calls automatically with Google Calendar

Connect your Google Calendar and Glitchgrab sends its recording bot to your client calls on its own, a few minutes before each one starts. After the call, you get:

• the recording
• a transcript with speaker names
• a button that turns what was asked into GitHub issues

Before you start

• A Google account whose calendar holds your client calls.
• The calls are Google Meet calls, with the Meet link on the calendar event.
• You own each project you want to record into, or have Context access to it (see Add team members and give them access).

1. Connect the calendar

Use either of these:

• Settings → Google Calendar → Connect Google Calendar
• Calls → the Schedule tab → the banner Connect Google Calendar and booked demos record themselves. → Connect calendar

Sign in to Google and allow access. You come back to Glitchgrab, but there is no confirmation message. Open Settings: the Google Calendar panel now shows your account's email and last synced … or not synced yet.

If the panel offers reconnect (needed once, to allow creating demo events), press it once and allow access again.

2. Check the upcoming calls

Open Calls and pick the Schedule tab. The Upcoming calls panel shows the connected Google account and lists calls in the next 24 hours that have a Meet link.

First, make sure the toggle at the top right reads auto-record on. When it is off, the panel warns Auto-record is off — no bot will be sent. Turn it on above. Press the toggle to turn it on.

Then, for each call:

1. Pick the project it belongs to. The picker starts at no project. A call left on "no project" is never recorded: no bot is sent and nothing warns you.
2. Leave it pending. Press skip if you don't want this one recorded.

Press refresh to pull the latest events (Calendar refreshed). In Settings, the same button is sync now (Calendar synced).

Demos booked through Glitchgrab are the exception. They are recorded even when auto-record is off, and they are filed under the project they were booked for. You don't pick anything for them. See Book demos from your website.

3. What happens at call time

• About 6 minutes before the start time, Glitchgrab sends the bot. The call's status changes from pending to dispatched.
• If you organise the event, the bot is added to it as an optional guest (guests are not emailed), so Meet lets it straight in.
• If someone else organises the event, the bot knocks, and someone in the call must press Admit. It waits up to 10 minutes.
• The bot records for up to 3 hours, and leaves on its own 60 seconds after everyone else has gone.

Everyone in the call sees the bot as a participant. That visible participant is your record that the call was recorded.

Which events are picked up

• Your primary calendar only.
• Events with a Google Meet link and a start time.
• Not all-day events, and not cancelled ones.

After the call

Open Calls (the Calls tab) and click the call. The recording uploads, then transcription runs; a one-hour call takes a few minutes. See Read a call's transcript, Turn a call into GitHub issues and Share a call with your client.

Troubleshooting

• A call was not recorded: the call was on no project, auto-record was off, it was skipped, or it had no Meet link. Check its status in Calls → Schedule. (Booked demos don't need auto-record.)
• A call shows "A bot was already on this call": it was already being recorded, for example by a bot sent by hand.
• The bot is waiting in the lobby: you are not the event's organiser. Press Admit in Meet, or send future invites from your own calendar.
• No calls listed: nothing with a Meet link is on your calendar in the next 24 hours. Press refresh after creating the event.
• Removing the bot mid-call: see Remove the Glitchgrab bot from a call.