Keep calendar and project tracker in sync automatically
Your Drive-based project tracker is the source of truth. Notis syncs it to your calendar—so changes propagate automatically.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Sync Events
Synchronizes google calendar events, performing a full sync if no `sync token` is provided or if a 410 gone error (due to an expired token) necessitates it, otherwise performs an incremental sync for events changed since the `sync token` was issued.
Why this helps
Your project tracker lives in a Drive doc, but calendar updates don't sync, creating dual-source confusion and duplicated updates.
- Calendar syncs from your Drive project tracker automatically
- Single source of truth eliminates duplicates
- Changes in Drive reflect on calendar immediately
- Reduced manual calendar maintenance
Setup
Build it in a few focused steps.
- 1Connect Google Drive and Google Calendar to Notis.
- 2Set up a webhook endpoint in Notis.
- 3Configure your Drive project tracker doc to send updates via webhook (or set up a scheduled sync).
- 4Create an automation: ask Notis 'Sync my Drive project tracker into my Google Calendar so calendar is always current.'
- 5Notis will map project tracker entries to calendar events.
- 6Test by updating a project entry in Drive and confirming it updates on your calendar within seconds.
Questions about this workflow
How does Notis handle conflicts if I update both the tracker and calendar?
You set a source of truth (typically Drive). Changes in Drive overwrite calendar; direct calendar edits are preserved unless Drive changes the same entry.
Can I exclude certain tracker entries from calendar sync?
Yes, mark entries as 'calendar-false' or ask Notis to sync only certain projects or milestone types.
What if my project tracker structure changes?
Tell Notis the new structure, and it re-maps. Notis adapts to different doc layouts (tables, bullets, etc.).
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.