Keep calendar events current with new research
Bring useful new context into the event where you will need it.
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
Relevant research arrives after an event is created, leaving its description out of date.
- Keep event context current as research changes
- Reduce last-minute searching before a commitment
- Make the related event easier to prepare for
Setup
Build it in a few focused steps.
- 1Connect Browserbase MCP and Google Calendar once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a name.
- 3In one instruction, ask Notis to match the supplied browser findings to a clearly identified existing event and patch only its description with concise source context.
- 4Choose notis_webhook as the trigger and send new findings with enough detail to identify the event.
- 5Choose where run reports go, then test with one real finding and event.
Questions about this workflow
What information is needed to identify the event?
Supply a clear event identifier or enough matching context, such as its title and date. Notis should ask for clarification or skip if the match is uncertain.
Will the update replace all event details?
No. Patch Event updates only the fields Notis is instructed to change. Array fields are replaced if provided, so avoid changing them unless necessary.
Can this create an event if none matches?
This workflow is for updating an existing event. If no reliable match is found, instruct Notis to report that instead of creating or changing an unrelated event.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Browserbase MCP to Google Calendar. A trigger fires from one place; an action lands in another.
Browserbase MCP 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.
Browserbase MCP 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.