Keep interview calendar details in sync with corrections
When updated interview details arrive, have Notis patch the existing calendar event with the supplied changes.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
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.
Why this helps
A changed interview detail can remain wrong on the calendar if the correction is buried in a recruiting workflow or message.
- Apply targeted changes to an existing event.
- Keep calendar details current when interview information changes.
- Avoid rewriting unrelated event information when only a few details changed.
Setup
Build it in a few focused steps.
- 1Connect Ashby and Google Calendar once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a name.
- 3Tell Notis in one instruction to patch the identified Google Calendar event using only the interview corrections supplied in the webhook request.
- 4Choose a webhook trigger and select where run reports should go.
- 5Test with one real correction and verify the intended event was updated.
Questions about this workflow
What does the request need to identify?
It must provide a valid calendar ID and event ID, along with the updated values. The listed Patch Event action requires those identifiers and write access.
Does patching preserve other event fields?
Patch semantics update only supplied fields. If an array field such as attendees is provided, that array is fully replaced.
Can this start from an Ashby trigger?
Ashby has no trigger events listed here. Use a Notis webhook request carrying the correction details.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Ashby to Google Calendar. A trigger fires from one place; an action lands in another.
Ashby triggers
Google Calendar actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Insert Calendar into List
Inserts an existing calendar into the user's calendar list.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Update Calendar List Entry
Updates an existing entry on the user\'s calendar list.
Delete Calendar
Deletes a secondary calendar. use calendars.clear for clearing all events on primary calendars.
Update Calendar
Updates metadata for a calendar.
Clear Calendar
Clears a primary calendar. this operation deletes all events associated with the primary calendar of an account.
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.
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.
Create a calendar
Creates a new, empty google calendar with the specified title (summary).
Connect any two apps with Notis in the middle.
Ashby and Google Calendar, or any other combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Google Calendar.