Refresh meeting details with current research
Keep a meeting event aligned with the latest information when its details need a full refresh.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Update Google 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.
Why this helps
Changes in research can leave an event with stale or incomplete details that are easy to miss.
- Bring current research into a clearly identified event
- Refresh intended event details in one step
- Reduce confusion from outdated meeting information
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 identify the exact event and provide every event field that should remain after a full replacement, using only confirmed research and supplied details.
- 4Choose notis_webhook as the trigger and send the new research with the event identifier and complete desired event details.
- 5Choose where run reports go, then test with one real event and verify its resulting details.
Questions about this workflow
Why does this use Update Google event instead of Patch Event?
Update Google event is a full replacement. Use it only when the complete desired event details are available, because unspecified fields may be cleared or reset.
What if some event details are unknown?
Do not run a full replacement with missing details. Supply the complete intended event or use a patch-style update for only the fields that should change.
How should it behave if the event match is ambiguous?
Instruct Notis to stop and report the ambiguity. A full replacement should only happen for a confidently identified 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.