Skip to article
Bridge

Connect Google Calendar to Bridge and check what happens next

Connecting Google Calendar lets Bridge use your upcoming events for meeting briefs and calendar workflows. Connect the right account, check that the expected events appear, and review automation settings before you rely on it.

Decide what you want the connection to do

Start with one outcome. You might want preparation context for upcoming meetings, an agent that checks your availability or an agent that schedules events. These have different consequences. Seeing an event is not the same as letting an agent create one.

A project team might start by simply seeing next week's client reviews in Bridge and preparing questions. Get that working before you add automatic attendance or scheduling. It makes a wrong event or mixed-up account easier to spot.

Connect the right Google account

In Bridge, go to Account settings → Connectors → Calendars. Choose Google Calendar and sign in. You can disconnect from the same page. Upcoming events then appear in Meetings → Upcoming and on Home.

Read Google's consent screen before you grant access. It lists exactly what data the app is asking for, and an app can only reach what you approve. If you keep separate personal and work accounts, make sure you're signing in to the one with the right calendar.

StepWhat to check
Open CalendarsYou're in the right Bridge account
Choose Google Calendar and sign inIt's the Google account you meant to connect
Look at upcoming eventsA known event appears with the expected details
Review Auto-Join in PreferencesIt only joins the meetings you want

What Bridge reads and what it can do

Bridge reads upcoming event details, participants and availability, and can turn events into preparation briefs. With a connected calendar, agents can also look up events, check availability and schedule meetings.

To test briefs, pick a meeting whose title and attendees you know, and compare it with the original event. If you try agent scheduling later, start with a low-stakes test event and check the result in your calendar.

  • Keep reading event context separate from actions that change your calendar.
  • Use a low-stakes test event when you try a new workflow.
  • Check the result in your calendar, not just in the chat.

Review auto-join separately

Agent Auto-Join is in Preferences and needs a connected calendar. It works for calendar meetings with Zoom, Google Meet or Microsoft Teams links. You can limit it in three ways:

  • Only meetings you host.
  • Only meetings where every participant shares your email domain.
  • Only meetings you've accepted.

Timing and access

You can also choose to join at the start time or two or five minutes early. Agents and automations only touch the calendars, events and meetings your connected account can already access.

Connecting a calendar doesn't replace talking to participants about recording. For the client review, decide how it will be captured and what the client expects. Test that events show up before you turn on auto-join.

If briefs or events don't appear

Most problems have a quick fix. If none of these work, email help@meetonbridge.com with a short description of the event you expected and what you see.

  • Check that the Calendars page shows Google as connected. If the token expired, disconnect and connect again.
  • Wait up to a minute after connecting, then refresh the page.
  • Look under Meetings → All or Upcoming, and Home → Upcoming. Make sure the right tab is selected and no filters are hiding the event.
  • Confirm the event exists in the Google account you connected.

Keep the connection matched to its purpose

After a trial, check whether briefs give you the context you need and auto-join suits your meetings. Turn on more workflows only when you understand what each one reads, does and produces.

If you disconnect, check that workflows you expect to stop have stopped. Deal separately with any saved content you want removed.

On Google's side, you can review or remove linked apps at any time. After revoking access, you may need to ask the developer to delete data they already hold.

Sources & further reading