Keep event file handoffs visible in ChMeetings
A shared planning file can signal that someone is ready to review or act. Let Notis send a ChMeetings notification when Drive sharing permissions are added.
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
ChMeetings: Send Notification
Tool to attempt sending a notification.
Why this helps
A new collaborator gets access to an event file, but the people coordinating the event may not notice the handoff.
- Make new file-sharing handoffs easier for the team to spot.
- Reduce the need to check Drive permissions manually.
- Include available file and sharing context in the notification.
Setup
Build it in a few focused steps.
- 1Connect Google Drive and ChMeetings once in the Notis portal.
- 2Create an automation in the portal or tell Notis in plain language from any channel.
- 3In one instruction, ask Notis to send a ChMeetings notification when a relevant event file or folder gets new sharing permissions.
- 4Pick the Google Drive File Shared trigger and choose where run reports should go.
- 5Test with one real sharing change.
Questions about this workflow
Does the trigger identify a newly shared file or folder?
Yes. The File Shared trigger detects added sharing permissions on files or folders and includes the current permission set with the change.
Can I tell Notis which sharing changes matter?
Yes. Describe the relevant event files or sharing context in your instruction. Notis uses the trigger data and can report when it cannot determine relevance.
What does the ChMeetings action do?
It attempts to send a notification. The instruction should make clear what information to include and who or what the notification should address, using information available to the connected apps.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Google Drive to Chmeetings. A trigger fires from one place; an action lands in another.
Google Drive triggers
Chmeetings actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Invite Meeting Attendee
Tool to invite a new attendee to a specified meeting. Use when you need to add attendees before the meeting begins.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Attendee Details
Tool to retrieve details for a specific attendee. Use when you have an attendee_id and need the attendee's full profile.
Comment Added (Docs/Sheets/Slides)
Triggers when a new comment is added to Google Docs, Sheets, or Slides.
ChMeetings: Create Meeting
Tool to create a new meeting in ChMeetings. Use when you have all meeting details and need to schedule it via the ChMeetings API.
File Created
Triggers when a new file is created in Google Drive.
ChMeetings: Create Organization
Tool to create a new organization.
File Deleted or Trashed
Triggers when a file is moved to trash or permanently deleted in Drive.
ChMeetings: Create Reminder
Tool to create/schedule a reminder for a meeting in ChMeetings.
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.
Delete Meeting Attendee
Tool to remove an attendee from a meeting. Use after confirming attendee details.
File Updated
Triggers when a file's metadata or content changes in Google Drive.
List Meeting Attendees
Tool to list attendees of a meeting. Use when you need to retrieve attendees for a specific meeting.
Google Drive Changes
Triggers when changes are detected in a Google Drive.
ChMeetings: Delete Meeting
Tool to delete an existing meeting. Use when you have confirmed the meeting ID to permanently remove the meeting.
Connect any two apps with Notis in the middle.
Google Drive and Chmeetings, 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 Chmeetings.