Turn browser research into your next work block
Finish a web research session with a clear time reserved to act on what you found.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
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.
Why this helps
Useful research often ends in open tabs and an unclear next step, so follow-through slips.
- Convert findings into a scheduled next step
- Avoid revisiting tabs to remember what to do
- Keep the calendar focused on actionable work
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 review the supplied browser research, identify one actionable follow-up, and create a realistic calendar work block with a specific title and duration.
- 4Choose notis_cron as the trigger and set a schedule after your research sessions are ready for review.
- 5Choose where run reports go, then test with one real research example.
Questions about this workflow
Does Browserbase MCP provide an event trigger for this automation?
No. Browserbase MCP exposes no trigger events in this workflow package, so the automation starts on a Notis schedule.
Will it schedule research automatically as soon as I browse?
No. The notis_cron trigger runs on the schedule you choose. Make the research available to Notis for review at that time.
Can Notis decide what work block to add?
Yes. Tell it how to select a useful follow-up and what duration or calendar constraints to respect. Supply any priorities it cannot infer from the research.
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.