With the Google Calendar integration, your assistant checks free times in a Google calendar you choose and books appointments into it while the caller is still on the line. You connect your Google account once, on Google's own sign-in and consent screen; Loomira never sees your password.

What the integration does

  • Checks availability. During a call, the assistant reads the free/busy times of the selected calendar and offers callers slots that are actually free.
  • Books appointments. When the caller confirms, the assistant creates the appointment in the selected calendar. Free/busy data is used during the call only and is not kept afterwards.
  • Changes only its own bookings, and only if you allow it. By default the assistant only books: if a caller asks to move or cancel an appointment, it takes down the request for your team. If you allow callers to change their bookings in the booking tool, it can move or cancel appointments that Loomira itself created. It never changes or deletes any other event.

Which permissions Loomira asks for, and why

Google lists three permissions on its consent screen. Loomira asks for nothing beyond them.

  • "See the list of Google calendars you're subscribed to": so the portal can show your calendars and you can pick the one to book into. Loomira reads calendar names and identifiers, nothing else.
  • "See the availability on Google calendars you have access to": so the assistant can find free times during a call. Loomira sees only whether a time is free or busy, not what your existing events contain.
  • "See, create, change, and delete events on Google calendars you own": so the assistant can create the booking event and, if you allow caller changes, move or cancel the events Loomira created. Google offers no narrower permission for adding events to an existing calendar. Loomira never changes or deletes any other event. To move one of its own appointments, it checks which events overlap that time and uses only their start and end times; titles and other details are discarded immediately.

Connecting your calendar

  1. In the portal, open Integrations and click Connect on the Google Calendar card.
  2. Sign in to Google and choose the account whose calendar the assistant should use.
  3. Review the three permissions and click Allow. You are returned to the portal; the card now shows Connected.
  4. Open the assistant that should book appointments, go to its Tools section (step 5, "What it can do", in the step-by-step guide; see Configure Your Assistant) and under Appointment booking click Add booking calendar.
  5. Choose the Google calendar the assistant books into and save the assistant.

The booking calendar is set per assistant, so one connected Google account can serve several assistants, each with its own calendar.

Where bookings appear

Each booked appointment is one event in the calendar you selected. It carries the caller's name, the caller's phone number (if it was transmitted or the caller gave it) and the notes taken during the booking. Loomira adds no attendees and sends no invitations, so nothing goes out to the caller from your calendar. The call itself is in the portal as usual (see Transcripts & Messages).

Disconnecting and revoking access

  • In the portal, open Integrations and click Disconnect on the Google Calendar card. Loomira deletes the stored access tokens immediately; assistant tools that use this calendar stop booking until you reconnect.
  • You can also withdraw access on Google's side at any time under Third-party apps & services in your Google account. Remove Loomira there and the connection stops working; disconnect it in the portal as well so the integrations page reflects that.

For your Google Workspace administrator

Google Workspace lets administrators restrict which third-party apps may access company data. If your organisation blocks apps that are not explicitly allowed, the Connect step ends with a Google error instead of the consent screen. Your administrator can allow Loomira in the Google Admin console under Security → Access and data control → API controls → Manage third-party app access by adding Loomira's OAuth client as a trusted app. The client ID to enter is shown in the portal next to the Google Calendar integration.

Privacy

How Loomira handles calendar data is set out in section 5 of our privacy policy: what is read, written and stored, who receives it, how it is protected and deleted, that calendar data is never sold, used for advertising or used to train AI models, and that access tokens are stored encrypted in the AWS region eu-central-1 (Frankfurt am Main) and deleted when you disconnect. Loomira's use and transfer to any other app of information received from Google APIs will adhere to Google API Services User Data Policy, including the Limited Use requirements.