Turn a shared brief into a meeting request
A shared brief can be the start of a working session. Notis can check the available context and carry a clear scheduling request into Calendarhero.
Trigger
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.
Action
Create Meeting Request V2
Tool to create a new meeting request in calendarhero. use when scheduling a meeting with participants, time range, and additional details.
Why this helps
A newly shared document signals that work is starting, but arranging the kickoff still takes a separate round of coordination.
- Use a new sharing event to surface meeting intent in a brief.
- Carry relevant file context into Calendarhero.
- Reduce the chance that kickoff scheduling gets lost after sharing.
Setup
Build it in a few focused steps.
- 1Connect Google Drive and Calendarhero once in the Notis portal.
- 2Create an automation and give it a name.
- 3In one instruction, ask Notis to create a Calendarhero meeting request only when a newly shared file's available content clearly calls for a meeting and provides usable details.
- 4Choose the Google Drive File Shared trigger and select where run reports should go.
- 5Test with one real shared brief that includes a clear meeting purpose and scheduling details.
Questions about this workflow
Does a new permission always mean a meeting should be scheduled?
No. Ask Notis to create a request only when the available file content clearly calls for a meeting.
Can the trigger tell who should attend?
The listed trigger detects new sharing permissions, but the event description does not guarantee that attendee details are available for scheduling. Use participant information only when the available context provides it.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Google Drive to Calendarhero. A trigger fires from one place; an action lands in another.
Google Drive triggers
Calendarhero actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Add Calendar Connection
Tool to add a calendar integration to a user's account. use after gathering provider credentials.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Contact
Tool to create a new contact. use after confirming contact details before making the api call.
Comment Added (Docs/Sheets/Slides)
Triggers when a new comment is added to Google Docs, Sheets, or Slides.
Create Meeting Request V2
Tool to create a new meeting request in calendarhero. use when scheduling a meeting with participants, time range, and additional details.
File Created
Triggers when a new file is created in Google Drive.
Fetch Contact
Fetch contact
File Deleted or Trashed
Triggers when a file is moved to trash or permanently deleted in Drive.
Fetch Meeting Details
Tool to fetch details for meetings within a specified timeframe. use this after user provides start and end datetimes in iso8601.
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.
Fetch User Profile
Tool to fetch the profile details of the authenticated user. use after obtaining a valid access token.
File Updated
Triggers when a file's metadata or content changes in Google Drive.
List Meetings
Tool to retrieve the user's meetings within a specified timeframe. use after confirming date range to fetch raw calendar data.
Google Drive Changes
Triggers when changes are detected in a Google Drive.
List Meeting Templates
Tool to list all meeting templates available for quick scheduling. use after authenticating and when you need to retrieve available templates before scheduling.
Connect any two apps with Notis in the middle.
Google Drive and Calendarhero, 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 Calendarhero.