Skip to main content

​
Overview

Voxworks offers a Google Calendar integration, connected with a Google sign-in (OAuth 2.0): It’s managed from Integrations (under Admin in the sidebar). The page is split into Connected Integrations and Available Integrations, and every card’s footer shows how many built-in tools the connection unlocks — for example “1 tool” or “No tools yet”. Tools that require an integration only appear in the script editor’s tool picker once that integration is connected. Each team holds one Google Calendar connection, shared by all team members.
Integrations are typically built out for specific clients, so the full functionality of Google Calendar’s interface might not be available. If your team needs additional features from this integration, contact the Voxworks team directly to discuss what can be added.

​
Connecting Google Calendar

  1. Go to Integrations in the sidebar (under Admin).
  2. Find the Google Calendar card under Available Integrations and click Connect. As soon as a connection is started the card moves up to Connected Integrations, where its badge tracks the connection status.
  3. A dialog opens: “Connect Google Calendar”, explaining “You will be redirected to authenticate with your account.” Make sure you have the necessary permissions in the Google account you plan to use.
  4. Click Authorize. Voxworks shows “Redirecting to authentication…” and sends you to Google’s sign-in and consent screen.
  5. Choose the Google account, review the requested permissions, and approve.
  6. Google returns you to the Integrations page. On success you see a confirmation such as “Google Calendar connected successfully” and the card shows a green Connected badge. If authorisation fails or you deny access, an error message shows the reason; the card stays Pending, and you can restart with its Setup button.
Google shows the full consent screen on every authorisation, including reauthorisations — this is expected and keeps the connection’s offline access current.

​
What Voxworks asks Google for

The connection requests your basic profile (name and email address) so Voxworks can identify the connected account, plus read access to free/busy availability across your calendars and the ability to create and manage calendars that Voxworks itself creates. Voxworks cannot read or edit events on your existing calendars; it only writes to the dedicated calendar it creates (see below). Access and refresh tokens are encrypted before they are stored.

​
Connection statuses

Each card under Connected Integrations shows a status badge: The same statuses appear inside the Integration Settings dialog (where Pending is shown as “Pending Setup”), along with the connection’s auth type badge (“OAuth 2.0”), how long ago it was connected, a masked OAuth Token row, and an Available Tools count for the integration.

​
The dedicated Voxworks calendar

Google Calendar is the only Google integration with an extra setup step. On your first successful authorisation, Voxworks creates a new, separate calendar inside the connected Google account: This is the calendar Voxworks uses for new events — appointments booked on calls are created here rather than on your personal or business calendars, and invitees are added to those events as attendees. You can view it alongside your other calendars in Google Calendar. In Integration Settings, the Connection Details section shows an App Calendar row with the calendar’s ID — or “Not created” if the dedicated calendar doesn’t exist yet.

​
Create Calendar

If the connection shows Connected but no dedicated calendar is on record (for example, calendar creation failed during the original authorisation), the settings dialog shows a notice: “Authorize Google Calendar again to create the VoxWorks calendar used for new events.” The primary button reads Create Calendar instead of Authorize Again. Clicking it sends you back through Google authorisation, and the calendar is created when you return.

​
Reauthorising

Google Calendar can be reauthorised at any time while connected. Open the card’s settings and click Authorize Again (or Create Calendar when the dedicated calendar is missing). Your existing dedicated calendar is always kept — reauthorising never creates a duplicate when one is already on record. The status stays Connected throughout unless the dedicated calendar is missing, in which case the connection shows Pending until authorisation completes. The connection can also be re-run from the card while it shows Pending (Setup) or Error (Reconnect).

​
Disconnecting

Open the connected card’s settings and click Disconnect. A confirmation dialog warns that disconnecting will:
  • Stop all active workflows using this integration
  • Remove access to its features from your AI agents
  • Delete any stored authentication tokens
You can reconnect at any time, but you’ll need to authorise with Google again. Two things to know for Google Calendar specifically:
  • Disconnecting removes the connection from Voxworks but does not delete the dedicated Voxworks calendar from your Google account — it remains there with all its events.
  • Reconnecting later creates a new dedicated calendar; earlier bookings stay in the old one. If you no longer need the old calendar, delete it in Google Calendar.
You can also revoke Voxworks’ access from your Google Account’s security settings at any time; if you do, reconnect from the Integrations page to restore the connection.

​
Next Steps