Check availability for pending meeting requests
A recurring review can surface free slots for pending requests that include a usable date range, so scheduling does not depend on remembering to check each one.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
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.
Why this helps
Pending requests can sit untouched because finding a suitable time means revisiting each response and checking calendar availability.
- Revisit pending requests on a predictable schedule.
- Find candidate slots for requests with clear date ranges.
- Reduce missed scheduling follow-up.
Setup
Build it in a few focused steps.
- 1Connect Basin and Google Calendar once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a name.
- 3In one instruction, tell Notis how to retrieve pending Basin responses through its API or MCP and find free slots for requests with defined time ranges.
- 4Pick a recurring schedule and choose where run reports should go.
- 5Test with one real pending request and a verifiable calendar range.
Questions about this workflow
Does this automatically book a slot?
No. It finds and reports candidate slots for review.
What if a request has no time range?
Have Notis flag the missing range instead of searching an arbitrary period.
Does this use Basin trigger events?
No. Basin exposes no trigger events here, so the workflow runs on a Notis recurring schedule and retrieves response data through its API or MCP.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Basin to Google Calendar. A trigger fires from one place; an action lands in another.
Basin 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.
Basin 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.