Connect Google Calendar to B6AI
Set up the Google Calendar integration end to end, from creating credentials in Google Calendar to verifying the live connection and using it in your bots.
Overview
The Google Calendar integration lets bots check availability and book appointments during a conversation, perfect for demos, callbacks, consultations and service bookings.
Customers pick a time in chat and the event lands on your calendar, with an invite sent automatically.
What you can do with Google Calendar
Once connected, your bots and agents can use Google Calendar inside conversations and automations. Typical uses include:
- Check free/busy on a calendar before offering a slot.
- Create an event/booking and invite the customer.
- Reschedule or cancel an existing event.
- List upcoming available slots for the customer to choose from.
How the integration works
You connect with one click, B6AI uses its own Google app, so there is nothing to create in Google Cloud and no Client ID/Secret to copy.
Clicking Connect sends you to Google to sign in and approve calendar access; Google returns a secure token that B6AI stores encrypted at rest.
B6AI reads availability and creates events on your behalf, limited to what you approved.
Prerequisites
Make sure all of the following are in place before you start. Each one is required, skipping any will cause the connection to fail later.
- A Google account (or Workspace) with the calendar you want bots to use.
- The Enterprise Admin role in B6AI.
Generate your Google Calendar connection
B6AI authenticates with Google Calendar using your Google Calendar connection. Follow these steps exactly, each field you copy here is entered into B6AI later.
- Unlike a manual API setup, Google Calendar needs no Google Cloud project, OAuth client or Client ID/Secret from you, B6AI provides the Google app.
- You only need a Google account that can access the target calendar.
- The connection is created during Connect (next section), where you sign in to Google and approve calendar access.
Required permissions & scopes
Grant only the scopes below. Each one maps to a specific B6AI capability; requesting fewer reduces risk and speeds up any review your Google Calendar administrator performs. The table explains exactly what each scope allows and why it is needed.
| Scope / permission | What it allows | Why B6AI needs it |
|---|---|---|
| calendar.events | Create, read and update events | Book, reschedule and cancel appointments |
| calendar.readonly | Read calendars and free/busy | Check availability before offering a slot |
Connect Google Calendar in B6AI
Now enter your credentials in B6AI. Signed in as an Enterprise Admin, open Settings → Integrations, find the Google Calendar card and click Connect, then complete the form. Every field is explained below.
- In B6AI, open Settings → Integrations and click Connect on the Google Calendar card.
- Sign in to Google and approve the calendar permissions B6AI requests.
- You’re returned to B6AI and the card shows “Connected”.
- When building a bot, add a Calendar node and pick the target calendar, time zone and slot length there.
Verify the connection
Confirm the integration is live before you rely on it in a bot.
- Confirm the Google Calendar card shows “Connected”.
- In a bot with a Calendar node, run the test: it creates a test event about an hour ahead.
- Confirm the event appears on the calendar, then delete it.
Troubleshooting
If the connection fails or an action does not work, match the symptom below to its cause and fix.
| Symptom / error | Likely cause | How to fix it |
|---|---|---|
| “Please reconnect” / invalid_grant | The Google authorization expired or was revoked | Click Connect again and re-approve access |
| 403 / access denied | You declined a calendar permission during consent | Reconnect and approve all requested permissions |
| Wrong calendar used | The Calendar node points at a different calendar | Set the correct Calendar ID on the Calendar node in Bot Builder |
| Double-booking | Availability wasn’t checked first | Enable the free/busy check before booking on the node |
Limitations & rate limits
Keep these constraints in mind so your bots behave predictably at scale.
- The Calendar API enforces per-user and per-project quotas.
- Time zones must be consistent between the bot’s Calendar node and the calendar.
- B6AI reads and writes only the calendars you grant access to.
Security best practices
- Grant only the scopes and permissions listed above, never request more “just in case”.
- Rotate your Google Calendar connection on a regular schedule, and immediately if you suspect exposure.
- Restrict the Enterprise Admin role (which manages integrations) to a small, trusted group.
- Prefer a dedicated service account or bot user over a personal login, so access survives staff changes.
- Review the integration’s activity in the B6AI Activity Logs periodically for unexpected calls.
- Disconnect the integration the moment a credential leaks; then rotate it in Google Calendar before reconnecting.
Recommendations
- Test against a sandbox or non-production Google Calendar account before connecting live data.
- Document which bots and flows depend on this integration so changes are predictable.
- Set a recurring reminder to review scopes and rotate credentials.
- Enable only the capabilities you actually use today; you can widen scopes later.