Skip to main content
Google Calendar in Hiveku isn’t a separate integration — it’s bundled with the Gmail connection. Pick the Full + Calendar scope when you connect Gmail, and your workflows and sales agent can manage calendar events on the same authorized account.
Calendar access is bundled with Gmail so users consent once, with a single Google OAuth app and one redirect. That’s one fewer integration to maintain.

​
What Calendar Access Enables

With calendar.events added to a Gmail connection, Hiveku can:
  • Create calendar events from workflows — e.g., when a lead books a call, put the event on your calendar
  • Send calendar invites to leads and team members
  • Let the sales agent book meetings directly on your calendar
  • Update and cancel events it created
Read-only scenarios (reading existing calendar availability, for example) also work via the same scope.

​
Before You Start

  • Set up a Google Cloud OAuth app if you haven’t already
  • Enable the Google Calendar API in your Google Cloud project: APIs & Services > Library > Google Calendar API > Enable
  • Make sure the Gmail API is also enabled (calendar is bundled into the Gmail connection flow)

​
Connect with Calendar Access

1

Open the Gmail connection flow

In Hiveku, go to CRM > Email Connections > Add Connection > Gmail.
2

Pick the Full + Calendar scope

From the scope picker, choose Full + Calendar. This requests:
https://www.googleapis.com/auth/gmail.modify
https://www.googleapis.com/auth/calendar.events
3

Authorize with Google

Click Authorize. On the Google consent screen, review the scopes — you should see both Gmail and Calendar permissions. Click Allow.
4

Confirm the connection

Back in Hiveku, the connection listing shows Full + Calendar as the active scope.

​
Upgrading an Existing Gmail Connection

If you already connected Gmail with a smaller scope (read-only, send, or full without calendar), you have to reconnect to add calendar access.
1

Disconnect the existing Gmail connection

CRM > Email Connections — find the Gmail account, open the menu, and click Disconnect.
2

Reconnect with Full + Calendar

Start the connection flow again and pick Full + Calendar from the scope dropdown.
Reconnecting briefly interrupts any workflows that use this mailbox. If the workflow runs during the reconnection window, it may fail until you finish authorizing. Reconnect during a quiet period if possible.

​
Which Calendar Gets Used?

By default, Hiveku writes to the account’s primary calendar. If you want events on a specific secondary calendar (e.g., Team Bookings), make sure the workflow or sales agent config specifies the calendar ID. Calendar IDs look like: 
primary
team-bookings@group.calendar.google.com

​
Verify It Works

1

Trigger a test event

Run a workflow that creates a calendar event, or ask your sales agent to book a test meeting with yourself.
2

Check Google Calendar

Open calendar.google.com with the same Google account. The test event should appear on your primary calendar within seconds.

​
Troubleshooting

Most common cause: the Google Calendar API isn’t enabled in your Google Cloud project. Go to APIs & Services > Library, search for Google Calendar API, and click Enable. Reconnect the Gmail account if the scope wasn’t granted.
The default target is the account’s primary calendar. If your workflow needs to write to a specific secondary calendar, set the calendar ID in the workflow step. Find calendar IDs in Google Calendar under Settings > [calendar name] > Integrate calendar.
You likely connected Gmail with a scope that doesn’t include calendar (read-only, send-only, or full without calendar). Disconnect and reconnect with Full + Calendar.
Google sends invites automatically when you create an event with attendees — but only if the sendUpdates flag is set. Hiveku sets this by default for workflows; if you’re using a custom integration, confirm the flag is enabled.

​
What’s Next?

Connect Gmail

The underlying connection for calendar access