Review the learner roster when a training list is shared
When a roster is shared in Drive, Notis can retrieve Coassemble users and summarize the available records for review, keeping a common follow-up task from falling through the cracks.
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
Get Users
Tool to retrieve a paginated list of users. use when you need to browse or process user records optionally filtered by clientidentifier.
Why this helps
A shared roster may prompt enrollment planning, but checking user records means switching between tools and comparing lists manually.
- Prompt a user list review when roster access changes.
- Summarize returned Coassemble user records for follow-up.
- Keep the report connected to the Drive sharing event.
Setup
Build it in a few focused steps.
- 1Connect Google Drive and Coassemble once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a name and prompt.
- 3In one instruction, ask Notis to retrieve Coassemble users and summarize the records for roster review when a Drive file or folder is shared.
- 4Pick the Google Drive File Shared trigger and choose where run reports should go.
- 5Test with one real sharing event and review the report.
Questions about this workflow
Does sharing a roster automatically enroll its listed people?
No. The available Coassemble action retrieves users; it does not enroll learners. Sharing also does not establish that anyone is eligible for enrollment.
Can it match Drive roster names to Coassemble accounts?
Not reliably without matching details. Supply a clear identifier or review the returned user list manually.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Google Drive to Coassemble. A trigger fires from one place; an action lands in another.
Google Drive triggers
Coassemble actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Clients
Tool to retrieve a paginated list of clients. use when you need to browse or process organisation records sequentially.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Courses
Tool to retrieve all courses with optional filters and pagination. use when you need to list courses after setting identifier and client identifier, and control page size and number.
Comment Added (Docs/Sheets/Slides)
Triggers when a new comment is added to Google Docs, Sheets, or Slides.
Get Trackings
Tool to retrieve tracking objects with filters. use when you need to fetch learner progress data filtered by course id, date range, identifier, or completion status.
File Created
Triggers when a new file is created in Google Drive.
Get Users
Tool to retrieve a paginated list of users. use when you need to browse or process user records optionally filtered by clientidentifier.
File Deleted or Trashed
Triggers when a file is moved to trash or permanently deleted in Drive.
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.
File Updated
Triggers when a file's metadata or content changes in Google Drive.
Google Drive Changes
Triggers when changes are detected in a Google Drive.
Connect any two apps with Notis in the middle.
Google Drive and Coassemble, 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 Coassemble.