Google Calendar integration

What it does

The Google Calendar integration lets your agency book, edit, and respond to client meetings without leaving TaskJuice. Connect a client's Google account once and you can read upcoming events, create new ones, patch or replace existing entries, query free and busy windows for scheduling, and start a workflow whenever a watched calendar changes.

Connect a Google Calendar account

1. Open your workspace in TaskJuice and navigate to Connections.
2. Choose Google Calendar and click Connect.
3. Sign in with the Google account whose calendar you want to manage on behalf of your client.
4. Grant the requested scopes (full read and write access to Google Calendar).
5. TaskJuice returns you to the workspace with the connection ready to use in any workflow.

To revoke access at any time, visit Google Account permissions and remove the TaskJuice entry.

Triggers

• google-calendar/calendar-changed fires whenever Google delivers a push notification for a watched calendar. The trigger reports the channel ID, resource state (sync, exists, not_exists), and resource URI so downstream actions can fetch the changed events. Inbound POSTs are authenticated by matching the X-Goog-Channel-Token header you set when the watch channel is created.

Actions

• google-calendar/create-event creates a new event on a selected calendar with start and end times, attendees, and an optional invitation send policy.
• google-calendar/list-events returns the events in a calendar with optional time bounds, ordering, and cursor pagination.
• google-calendar/get-event returns a single event by its ID.
• google-calendar/update-event replaces every field of an existing event.
• google-calendar/patch-event updates only the fields you provide on an existing event.
• google-calendar/delete-event removes an event from a calendar.
• google-calendar/check-availability runs a free or busy query for one or more calendars over a given interval.
• google-calendar/create-calendar creates a new secondary calendar on the connected account.

Known limitations

• Google Calendar push notifications expire on a schedule set by Google (typically up to seven days). TaskJuice refreshes the watch channel before it lapses; an X-Goog-Resource-State of sync indicates a freshly opened channel, not a content change.
• The Calendar API enforces per-user and per-project quotas. When a 429 is returned, TaskJuice surfaces it as a retryable rate-limit error and respects the recommended backoff.
• Recurring events are returned as a single record unless you set singleEvents to true on the list action, which expands recurrences into individual instances.