Bring new Drive folder collaborators into Breeze
When someone gets access to a shared project folder, keep the project team in sync.
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
Add Project People
Tool to add people to a project. use when you have a valid project id and one or more email addresses to invite them.
Why this helps
New collaborators can receive Drive access while remaining absent from the project team that coordinates the work.
- Reduce repeated collaborator invitations
- Keep project membership aligned with folder access
- Make newly granted access easier to follow up
Setup
Build it in a few focused steps.
- 1Connect Google Drive and Breeze once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a name.
- 3In one instruction, ask Notis to review newly granted folder permissions and add a person to the corresponding Breeze project only when the project and email identity are unambiguous.
- 4Pick the Google Drive File Shared trigger and choose where run reports should go.
- 5Test with one real folder sharing event and check the project membership.
Questions about this workflow
Does this remove people when folder access changes?
No. This workflow responds to newly granted permissions and adds people to a project.
What if the matching project is unclear?
The instruction should have Notis report the ambiguity instead of adding a person to the wrong project.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Google Drive to Breeze. A trigger fires from one place; an action lands in another.
Google Drive triggers
Breeze actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Add Project People
Tool to add people to a project. use when you have a valid project id and one or more email addresses to invite them.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Archive Project
Tool to archive a specific project. use when you need to hide a completed or inactive project from active views after confirming its details.
Comment Added (Docs/Sheets/Slides)
Triggers when a new comment is added to Google Docs, Sheets, or Slides.
Create Card
Tool to create a new card in a project. use after confirming the project id. creates a task with details like name, due date, and assignees.
File Created
Triggers when a new file is created in Google Drive.
CREATE_LIST
Tool to create a new list (stage) in a breeze project. use when you've selected a project and need to add a new stage. example: "create a new todo list for project 42."
File Deleted or Trashed
Triggers when a file is moved to trash or permanently deleted in Drive.
Create Project
Tool to create a new project in breeze. use when you have the project name and want to initialize it via the api.
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.
Create Workspace
Tool to create a new workspace. use after deciding on the workspace name.
File Updated
Triggers when a file's metadata or content changes in Google Drive.
Delete Card
Tool to delete a specific card (task) by its id. use when you need to remove a task permanently; deletions cannot be undone.
Google Drive Changes
Triggers when changes are detected in a Google Drive.
Delete Project
Tool to delete a specific project by id. use when you need to remove a project after confirming its id.
Connect any two apps with Notis in the middle.
Google Drive and Breeze, 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 Breeze.