# Connect Google Calendar to Workato Api Proxy

When **Attendee Response Changed** fires in [Google Calendar](https://apiant.ai/connections/google-calendar), your agent runs **Update recipe** in [Workato Api Proxy](https://apiant.ai/connections/workato-api-proxy). Describe the whole flow and it is built, tested on every scenario and kept running.

Google Calendar **6** triggers Google Calendar **27** actions Workato Api Proxy **5** actions

What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.

## What do you want Google Calendar and Workato Api Proxy to do together?

Give your AI client this address.

`https://mcp.apiant.ai`

Any client that takes a remote MCP server. Nothing to install. Create your free account, then sign in once in your browser.

### Set it up in your client

### Claude Code

Run this in the directory you want to work in.

`claude mcp add --transport http -s project apiant-ai https://mcp.apiant.ai`

Start Claude Code there, approve the server, and sign in in the browser page it opens.

[Claude Code guide (opens in a new tab)](https://apiant.ai/docs/mcp/claude-code)

### Claude, web and desktop

Open Customize, then Connectors, then Add custom connector, and paste the address. On Team and Enterprise an owner adds it first.

[Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp)

### Cursor

Add the address to your MCP configuration as a server URL. Cursor signs you in in your browser.

[Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp)

### Zed

Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.

[Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp)

### Codex and the ChatGPT desktop app

Open Settings, then MCP servers, then Add server, and choose Streamable HTTP. From the terminal, Codex takes the address with its own add command and then signs you in.

[Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp)

### Any other MCP client

Paste the address where the client asks for a remote MCP server URL, and name the server apiant-ai where it lets you. APIANT's skills reach the client over the same connection.

[Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp)

Example flows

## What Google Calendar can start in Workato Api Proxy

- When **Attendee Response Changed** in Google Calendar then **Update recipe** in Workato Api Proxy
- When **Event Created** in Google Calendar then **Start recipe** in Workato Api Proxy

Starting points drawn from the triggers and actions in the catalog today. Describe the flow you need, at any depth, and your agent builds it and tests every scenario before it ships.

Everything your agent can do with Google Calendar and Workato Api Proxy

## Triggers and actions 6 triggers · 32 actions

- Trigger

**Attendee Response Changed**

Polling trigger that fires when any attendee's RSVP changes to accepted, declined, or tentative. Returns attendee info and current status.

- Trigger

**Calendar Event Sync**

Polling trigger that returns full event data including details, attendees, and metadata. For real-time notifications with basic info, use Calendar Event Changes (webhook).

- Trigger

**Event Canceled or Deleted**

Triggers when a Google Calendar event is cancelled or deleted. Returns minimal data: event_id, summary (if available), and cancellation timestamp.

- Trigger

**Event Created**

Polling trigger that fires when a new calendar event is created. Returns event ID, summary, start/end times, and organizer info.

- Trigger

**Event Starting Soon**

Triggers when a calendar event is within a configured number of minutes from starting. Returns event details, time remaining, attendees, and join links when available.

- Trigger

**Event Updated**

Triggers when an existing Google Calendar event is modified. Returns the event ID, change type, and the specific fields that changed with their previous and new values.

- Action

**Calendar List Insert**

Inserts an existing calendar into the user's calendar list.

- Action

**Calendar List Update**

Updates an existing entry on the user\'s calendar list.

- Action

**Calendars Delete**

Deletes a secondary calendar. use calendars.clear for clearing all events on primary calendars.

- Action

**Calendars Update**

Updates metadata for a calendar.

- Action

**Create Event**

Creates an event on a google calendar, needing rfc3339 utc start/end times (end after start) and write access to the calendar. by default, adds the organizer as an attendee unless exclude organizer is set to true.

- Action

**Delete Event**

Deletes a specified event by `event id` from a google calendar (`calendar id`); this action is idempotent and raises a 404 error if the event is not found.

- Action

**Duplicate Calendar**

Creates a new, empty google calendar with the specified title (summary).

- Action

**Events Instances**

Returns instances of the specified recurring event.

- Action

**Events List**

Returns events on the specified calendar.

- Action

**Events Move**

Moves an event to another calendar, i.e., changes an event's organizer.

- Action

**Events Watch**

Watch for changes to events resources.

- Action

**Find Event**

Finds events in a specified google calendar using text query, time ranges (event start/end, last modification), and event types; ensure `timemin` is not chronologically after `timemax` if both are provided.

- Action

**Find Free Slots**

Finds free/busy time slots in google calendars for specified calendars within a defined time range (defaults to the current day utc if `time min`/`time max` are omitted), enhancing busy intervals with event details; `time min` must precede `time max` if both are provided.

- Action

**Free Busy Query**

Returns free/busy information for a set of calendars.

- Action

**Get Calendar**

Retrieves a specific google calendar, identified by `calendar id`, to which the authenticated user has access.

- Action

**Get Current Date Time**

Gets the current date and time, allowing for a specific timezone offset.

- Action

**List Acl Rules**

Retrieves the list of access control rules (acls) for a specified calendar, providing the necessary 'rule id' values required for updating specific acl rules.

- Action

**List Calendars**

Retrieves calendars from the user's google calendar list, with options for pagination and filtering.

- Action

**Patch Calendar**

Partially updates (patches) an existing google calendar, modifying only the fields provided; `summary` is mandatory and cannot be an empty string, and an empty string for `description` or `location` clears them.

- Action

**Patch Event**

Updates specified fields of an existing event in a google calendar using patch semantics (array fields like `attendees` are fully replaced if provided); ensure the `calendar id` and `event id` are valid and the user has write access to the calendar.

- Action

**Quick Add**

Parses natural language text to quickly create a basic google calendar event with its title, date, and time, suitable for simple scheduling; does not support direct attendee addition or recurring events, and `calendar id` must be valid if not 'primary'.

- Action

**Remove Attendee**

Removes an attendee from a specified event in a google calendar; the calendar and event must exist.

- Action

**Settings List**

Returns all user settings for the authenticated user.

- Action

**Settings Watch**

Watch for changes to settings resources.

- Action

**Sync Events**

Synchronizes google calendar events, performing a full sync if no `sync token` is provided or if a 410 gone error (due to an expired token) necessitates it, otherwise performs an incremental sync for events changed since the `sync token` was issued.

- Action

**Update Acl Rule**

Updates an access control rule for the specified calendar.

- Action

**Update Event**

Updates an existing event by `event id` in a google calendar; this is a full put replacement, so provide all desired fields as unspecified ones may be cleared or reset.

- Action

**Get job**

Returns one job run of a recipe, including its status, timing, error details and the input and output of each step.

- Action

**Get recipe**

Returns the details of a Workato recipe, including its name, status, connections and step definitions.

- Action

**List jobs**

Returns the jobs run by a recipe, up to 1,000 at a time, along with succeeded and failed job counts.

- Action

**Start recipe**

Starts a stopped Workato recipe so it begins processing trigger events.

- Action

**Update recipe**

Updates an existing stopped recipe's name, steps, connections, folder or description. Running recipes cannot be updated.

## Each app on its own

- [ **Google Calendar** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connections/google-calendar)
- [ **Workato Api Proxy** REST API for managing integration recipes, connections, jobs, and folders on an automation orchestration...](https://apiant.ai/connections/workato-api-proxy)

Reviews

## What our customers say

## More from Google Calendar

- [ **Google Calendar to HubSpot** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/google-calendar-to-hubspot)
- [ **Google Calendar to Salesforce** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/google-calendar-to-salesforce)
- [ **Google Calendar to Slack** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/google-calendar-to-slack)
- [ **Google Calendar to Google Sheets** Google Sheets](https://apiant.ai/connect/google-calendar-to-google-sheets)
- [ **Google Calendar to Stripe** Stripe is a payment processing platform for online businesses.](https://apiant.ai/connect/google-calendar-to-stripe)
- [ **Google Calendar to Shopify** Shopify is a commerce platform for online stores and retail point-of-sale.](https://apiant.ai/connect/google-calendar-to-shopify)

## More into Workato Api Proxy

- [ **HubSpot to Workato Api Proxy** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-workato-api-proxy)
- [ **Salesforce to Workato Api Proxy** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/salesforce-to-workato-api-proxy)
- [ **Slack to Workato Api Proxy** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/slack-to-workato-api-proxy)
- [ **Google Sheets to Workato Api Proxy** Google Sheets](https://apiant.ai/connect/google-sheets-to-workato-api-proxy)
- [ **Gmail to Workato Api Proxy** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-workato-api-proxy)
- [ **Google Drive to Workato Api Proxy** Google Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...](https://apiant.ai/connect/google-drive-to-workato-api-proxy)

Questions

## Google Calendar and Workato Api Proxy, answered

###

### What can start an automation from Google Calendar?

Any of Google Calendar's 6 triggers in the catalog, including Attendee Response Changed, Event Created, Event Updated and Calendar Event Sync. Describe the moment in plain language and your agent picks the right one.

###

### What can your agent do in Workato Api Proxy when something happens in Google Calendar?

Any of Workato Api Proxy's 5 actions, including Update recipe, Get job, Get recipe and List jobs. Your agent maps the data both ways and tests every scenario before it ships.

###

### Can it also run from Workato Api Proxy to Google Calendar?

Workato Api Proxy has no triggers in the catalog today, so automations start in Google Calendar. If you need the other direction, ask: your agent reads Workato Api Proxy's API documentation and adds it.

###

### Do I have to build a connector for Google Calendar or Workato Api Proxy?

No. Both are in the catalog with their triggers and actions. You describe the automation; your agent builds it, tests every scenario and keeps it running.

###

### What happens when something fails?

Your agent works that out for you. It plans the failure paths along with the happy path, then tests every scenario before it ships.

###

### Is there a free plan?

Yes. Every plan includes the agent, including free, and building from your own AI client spends no assistant credits.
