--- title: "Connect Google Calendar and Greenhouse - APIANT.ai" description: "When \"Attendee Response Changed\" fires in Google Calendar, your agent runs \"Create Candidate Note\" in Greenhouse." canonical: "https://apiant.ai/connect/google-calendar-to-greenhouse" --- # Connect Google Calendar and Greenhouse When **Attendee Response Changed** fires in [Google Calendar](https://apiant.ai/connections/google-calendar), your agent runs **Create Candidate Note** in [Greenhouse](https://apiant.ai/connections/greenhouse), or **Application Updated** in Greenhouse to **Create Event** in Google Calendar. Describe the whole flow and it is built, tested on every scenario and kept running. Google Calendar **6** triggers Google Calendar **45** actions Greenhouse **15** triggers Greenhouse **38** 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 Greenhouse to do together? Give your AI client this address. `https://mcp.apiant.ai` One connection does both: ask your client to act in an app once, or have it build an automation that keeps running. 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 and Greenhouse can do together ### From Google Calendar to Greenhouse - When **Attendee Response Changed** in Google Calendar then **Create Candidate Note** in Greenhouse - When **Event Created** in Google Calendar then **Add Attachment to Candidate** in Greenhouse ### From Greenhouse to Google Calendar - When **Application Updated** in Greenhouse then **Create Event** in Google Calendar - When **Candidate Updated** in Greenhouse then **Update Event** in Google Calendar 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 Greenhouse ## Triggers and actions 21 triggers · 83 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 **Acl Delete** Deletes an access control rule from a Google Calendar. Use when you need to remove sharing permissions for a user, group, or domain. - Action **Acl Get** Retrieves a specific access control rule for a calendar. Use when you need to check permissions for a specific user, group, or domain. - Action **Acl Insert** Creates an access control rule for a calendar. Use when you need to grant sharing permissions to a user, group, or domain. - Action **Acl List** 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 **Acl Patch** Updates an existing access control rule for a calendar using patch semantics (partial update). This allows modifying specific fields without affecting other properties. IMPORTANT: The ACL rule must already exist on the calendar. This action cannot create new rules. If you receive a 404 Not Found error, the rule does not exist - use ACL insert to create it first, or use ACL list to verify available rules. Each patch request consumes three quota units. For domain-type ACL rules, if PATCH fails with 500 error, this action will automatically fallback to UPDATE method. - Action **Acl Update** Updates an access control rule for the specified calendar. - Action **Acl Watch** Tool to watch for changes to ACL resources. Use when you need to set up real-time notifications for access control list modifications on a calendar. - Action **Batch Events** Execute up to 1000 event mutations (create/patch/delete) in one Google Calendar HTTP batch request with per-item status/results. Use this to materially reduce round-trips for bulk operations like migrations, cleanup, or large-scale updates. - Action **Calendar List Delete** Tool to remove a calendar from the user's calendar list. Use when you need to unsubscribe from or hide a calendar from the user's list. - Action **Calendar List Get** Retrieves metadata for a SINGLE specific calendar from the user's calendar list by its calendar ID. This action requires a calendarId parameter and returns details about that one calendar only. NOTE: This does NOT list all calendars. To list all calendars in the user's calendar list, use GOOGLECALENDAR_CALENDAR_LIST_LIST instead. - Action **Calendar List Insert** Inserts an existing calendar into the user's calendar list. - Action **Calendar List Patch** Updates an existing calendar on the user's calendar list using patch semantics. This method allows partial updates, modifying only the specified fields. - Action **Calendar List Update** Updates an existing entry on the user\'s calendar list. - Action **Calendar List Watch** Watch for changes to CalendarList resources using push notifications. Use this to receive real-time updates when calendar list entries are modified. - 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 **Channels Stop** Tool to stop watching resources through a notification channel. Use when you need to discontinue push notifications for a specific channel subscription. - Action **Create Calendar** Creates a new secondary Google Calendar with the specified title and optional settings. Use this action when you need to create a new calendar for organizing events separately from the primary calendar. The authenticated user becomes the owner of the newly created calendar. Optional parameters include description, location, and timezone. - 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 Get** Retrieves a SINGLE event by its unique event_id (REQUIRED). This action does NOT list or search events - it fetches ONE specific event when you already know its ID. If you want to list events within a time range, search for events, or filter by criteria like time_min/time_max, use GOOGLECALENDAR_EVENTS_LIST instead. - Action **Events Import** Tool to import an event as a private copy to a calendar. Use when you need to add an existing event to a calendar using its iCalUID. Only events with eventType='default' can be imported. - Action **Events Instances** Returns instances of the specified recurring event. - Action **Events List** Returns events on the specified calendar. - Action **Events List All Calendars** Return a unified event list across all calendars in the user's calendar list for a given time range. Use when you need a single view of all events across multiple calendars. An inverted or incorrect time range silently returns empty results rather than an error. An empty `items` list means no events matched the filters—adjust `time_min`, `time_max`, or `q` before concluding no events exist. - 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 Get** Tool to return a single user setting for the authenticated user. Use when you need to retrieve a specific calendar setting value. - 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. - Trigger **Application Rejected** Triggers when an application in Greenhouse is rejected, returning the rejected application with its candidate, job, rejection reason and custom fields. - Trigger **Application Updated** Triggers when an application is created or updated in Greenhouse, including stage moves, rejections and hires. - Trigger **Candidate Hired** Triggers when a candidate's application is marked as hired in Greenhouse, delivering the hired application. - Trigger **Candidate Updated** Triggers when a candidate is created or updated in Greenhouse, returning the candidate's profile, contact details, tags and custom fields. - Trigger **Job Updated** Triggers when a job (hiring plan) is created or updated in Greenhouse. - Trigger **New Candidate** Triggers when a new candidate or prospect is added to Greenhouse. - Trigger **New Candidate Application** Triggers when a new application is submitted or added for a candidate in Greenhouse, optionally limited to specific jobs, stages, sources or statuses. - Trigger **New Job** Triggers when a new job (requisition / hiring plan) is created in Greenhouse. - Trigger **New Job Post** Triggers when a new job post (a candidate-facing listing of a job) is created in Greenhouse. - Trigger **New Note** Triggers when a new note is added to a candidate's profile in Greenhouse, including logged emails and activity entries. - Trigger **New Offer** Triggers when a new offer is created on a candidate's application in Greenhouse. - Trigger **New Scheduled Interview** Triggers when an interview on a candidate's application is scheduled on the calendar in Greenhouse. - Trigger **New Scorecard** Triggers when an interviewer submits a scorecard for a candidate's interview in Greenhouse. - Trigger **New Scorecard Due** Triggers when an interview has taken place and the interviewer's scorecard is still in draft, waiting to be submitted. - Trigger **Offer Updated** Triggers when an offer is created or updated in Greenhouse, including status changes such as accepted or rejected. - Action **Add Attachment to Candidate** Attaches a file (resume, cover letter, offer letter or other document) to a candidate's application in Greenhouse, from a public file URL or base64 file content. - Action **Add Candidate Education** Adds an education entry (school, degree, field of study and dates) to a candidate's profile in Greenhouse. - Action **Add Candidate Employment** Adds a work history entry (employer, job title and dates) to a candidate's profile in Greenhouse. Leave the end date blank to record it as the candidate's current job. - Action **Add Tag to Candidate** Applies an existing tag from your organization's tag list to a candidate. Returns the applied tag record. - Action **Convert Prospect to Candidate** Converts a prospect application into a candidate application on a job, optionally placing it on a chosen interview stage. Returns the new candidate application. - Action **Create Application** Creates a new application for an existing Greenhouse candidate, either on a job or as a prospect application. - Action **Create Candidate** Creates a new candidate in Greenhouse, either applied to a job or as a prospect, and returns the new candidate and their application. - Action **Create Candidate Note** Adds a note, logged email, or activity-feed entry to a Greenhouse candidate, optionally tied to one of their applications. - Action **Create Interview** Records an interview that is already scheduled on an external calendar against a candidate's application, at a chosen slot on the job's interview plan. It does not create a calendar event or send invites. - Action **Create Job** Creates a new job in Greenhouse from an existing template job, with the requested number of openings, department, offices and custom field values. - Action **Create Job Note** Adds a note to a job in Greenhouse, written on behalf of the user you choose and visible to job admins or to users allowed to see private job notes. - Action **Create Job Post** Creates a new job post by copying an existing job post onto a job board, optionally with a new title, description, and publication status. - Action **Create Offer** Creates an offer on an existing Greenhouse application, with an optional start date, opening and offer/compensation custom field values. - Action **Create Opening** Adds a new opening (headcount slot) to an existing Greenhouse job, optionally with your own position id and opening custom field values. - Action **Create Prospect** Creates a new prospect in Greenhouse: a candidate profile with a prospect application, optionally tied to jobs, a prospect pool, a department or an office. - Action **Delete Application** Permanently deletes a single application, along with its interview stages, scorecards and rejection details. The candidate and their other applications are kept. - Action **Delete Candidate** Permanently deletes a candidate along with all of their applications, attachments, scorecards and notes. This cannot be undone. - Action **Delete Interview** Cancels and deletes a scheduled interview in Greenhouse, along with its interviewer assignments and reminders. Only interviews that are scheduled or awaiting feedback can be deleted. - Action **Delete Note** Permanently deletes a note from a candidate's activity feed. This cannot be undone. - Action **Delete Opening** Permanently removes an opening from its job. Only closed openings with no offer and no hired application can be deleted. - Action **Find Application** Returns up to 100 job applications that match a free-text search and/or filters such as candidate, job, stage, source, department, office or hiring team. - Action **Find Candidate** Returns up to 100 candidates and prospects that match a free-text search and/or filters such as job, stage, tag, source or recruiter, plus the first match on its own. - Action **Find Due Scorecard** Finds scorecards that are still due — interview evaluations an interviewer has not yet submitted — for the applications, interviewers or interview kits you specify. - Action **Find Job** Returns up to 100 jobs matching a free-text search term and optional filters such as status, department, office, hiring team member or custom field answer. - Action **Find Offer** Finds offers extended to candidates, filtered by application, candidate, job, opening, status or date, and returns the matching offers plus the first match. - Action **Hire Application** Marks a candidate's application as hired and closes the matching opening on the job. - Action **Merge Candidates** Merges a duplicate candidate into another candidate. The primary candidate keeps its profile and absorbs the duplicate's applications, attachments, notes and tags; the duplicate is deleted. - Action **Move Application** Moves an application to a different interview stage on the same job, or transfers it to another job. Stage transition rules, including automated emails, fire as they would in Greenhouse. - Action **Reject Application** Rejects a candidate's application with a rejection reason, optionally sending the candidate a templated rejection email and setting application custom fields. - Action **Remove Tag from Candidate** Removes a tag from a candidate by deleting the applied-tag record. The tag itself stays in your Greenhouse tag list. - Action **Unreject Application** Reverses a rejection on an application, returning it to the in-process state on the stage it was rejected from. The earlier rejection reason and notes are cleared. - Action **Update Application** Updates the attribution and details of an existing Greenhouse application, such as its source, referrer, recruiter, coordinator, prospect pool and stage, and custom fields. - Action **Update Candidate** Updates an existing Greenhouse candidate's profile — name, company, title, contact details, tags, linked users and custom fields. Only the values you fill in are changed. - Action **Update Interview** Updates a scheduled interview's time, location, video conferencing link, calendar event id, organizer or interviewer panel. Changes the Greenhouse record only and sends no calendar invites. - Action **Update Job** Updates an existing Greenhouse job's name, notes, offices, department, requisition id and custom fields, and returns the updated job. - Action **Update Job Post** Updates a Greenhouse job post: change its public title, replace its description, or publish it (live) or return it to draft. - Action **Update Offer** Updates an existing offer's start date, opening, sent/created/resolved dates and offer custom fields, including compensation. Returns the updated offer. - Action **Update Opening** Updates an opening on a Greenhouse job — its external id, target start date, custom fields, or open/closed status with a close reason. ## 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) - [ **Greenhouse** Greenhouse is a hiring software company. We create the technology, know-how and support for your business'...](https://apiant.ai/connections/greenhouse) 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 Greenhouse - [ **Google Sheets to Greenhouse** Google Sheets](https://apiant.ai/connect/google-sheets-to-greenhouse) - [ **Gmail to Greenhouse** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-greenhouse) - [ **Google Drive to Greenhouse** Google Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...](https://apiant.ai/connect/google-drive-to-greenhouse) - [ **ActiveCampaign to Greenhouse** ActiveCampaign is a marketing automation, email marketing, and CRM platform.](https://apiant.ai/connect/activecampaign-to-greenhouse) - [ **Airtable to Greenhouse** Organize anything with Airtable, a modern database created for everyone.](https://apiant.ai/connect/airtable-to-greenhouse) - [ **Asana to Greenhouse** Asana is a collaborative information manager for workspace.](https://apiant.ai/connect/asana-to-greenhouse) Questions ## Google Calendar and Greenhouse, 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 Greenhouse when something happens in Google Calendar? Any of Greenhouse's 38 actions, including Create Application, Create Candidate, Create Candidate Note and Create Interview. Your agent maps the data both ways and tests every scenario before it ships. ### ### Can it also run from Greenhouse to Google Calendar? Yes. When something happens in Greenhouse, your agent can act in Google Calendar too. This page covers both directions: Greenhouse's triggers and Google Calendar's actions are listed here as well. ### ### Do I have to build a connector for Google Calendar or Greenhouse? 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. ### ### Can my AI client use Google Calendar and Greenhouse without building an automation? Yes. With your AI client connected to APIANT, ask it to do something in either app once and it runs that action on the spot. Ask for an automation and your agent builds it, tests every scenario and keeps it running. One connection covers both. ### ### 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.