Know your availability when Drive changes happen
Drive changes just detected. Notis checks your calendar—telling you if you have bandwidth to respond now or need to reschedule.
Trigger
Google Drive Changes
Triggers when changes are detected in a Google Drive.
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
Batch Drive changes land but you don't know if you're available to respond, so urgent changes might be missed.
- Automatic availability check on Drive changes
- Know immediately if you can respond
- Reduce missed urgent updates
- Better coordination of reactive work
Setup
Build it in a few focused steps.
- 1Connect Google Drive and Google Calendar.
- 2Create an automation: ask Notis 'When Drive changes are detected, check if I have free time in the next hour to respond and let me know.'
- 3Select 'Google Drive Changes' as the trigger.
- 4Set your availability window (next hour, next 2 hours, etc.).
- 5Configure your notification channel so you're alerted immediately.
- 6Test by making changes to several Drive files in sequence.
Questions about this workflow
What counts as 'Drive changes'? Will this trigger on every single edit?
It detects batch changes—not every keystroke. Ask Notis to focus on specific file types, folders, or change types if you want to narrow the scope.
Can I set different availability windows for different types of changes?
You can create separate automations, e.g., 'check 1-hour availability for client files' and '24-hour availability for internal updates'.
Will this block time, or just report availability?
It reports availability. You stay in control of whether to block time or respond immediately.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Google Drive to Google Calendar. A trigger fires from one place; an action lands in another.
Google Drive triggers
Google Calendar actions
Comment Added (Docs/Sheets/Slides)
Triggers when a new comment is added to Google Docs, Sheets, or Slides.
Insert Calendar into List
Inserts an existing calendar into the user's calendar list.
File Created
Triggers when a new file is created in Google Drive.
Update Calendar List Entry
Updates an existing entry on the user\'s calendar list.
File Deleted or Trashed
Triggers when a file is moved to trash or permanently deleted in Drive.
Delete Calendar
Deletes a secondary calendar. use calendars.clear for clearing all events on primary calendars.
File Shared (Permissions Added)
Triggers when new sharing permissions are granted to a file or folder. Uses Drive's `changes.list` endpoint with inline `permissions` in the `fields` mask so each change carries the file's current permission set provider-atomically. We diff that against `seen_permission_keys` to identify newly added grants. Drive page tokens are the primary cursor; if Drive rejects a stored token, the trigger raises `PollingTriggerError` without clearing state rather than silently re-baselining and dropping events. Limitation: truly ephemeral permissions (added and revoked between two polls without any other file modification in between) are not detected. Drive Activity API would catch those but requires an additional OAuth scope and a different payload contract.
Update Calendar
Updates metadata for a calendar.
File Updated
Triggers when a file's metadata or content changes in Google Drive.
Clear Calendar
Clears a primary calendar. this operation deletes all events associated with the primary calendar of an account.
Google Drive Changes
Triggers when changes are detected in a Google Drive.
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.
New File Matching Query
Triggers when a new Google Drive file matches a provided query. This is the legacy query-centric trigger: it preserves Drive API query config such as ``corpora`` / ``driveId`` aliases and emits the historical ``file_matching_query`` event type. ``FileCreatedTrigger`` covers the broader "new file" case and emits ``file_created``.
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.
Not just Google Drive and Google Calendar. Any combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7 days free trial with 20$ free usage included.
No card. Works with personal or business Google Calendar.