Keep Drive sharing changes visible for review
When a file or folder is shared, create a clear review task in Bitbucket so permission changes do not go unnoticed.
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 an issue
Creates a new issue in a bitbucket repository, setting the authenticated user as reporter; ensures assignee (if provided) has repository access, and that any specified milestone, version, or component ids exist.
Why this helps
New sharing permissions can be easy to miss when access reviews happen across several tools.
- Make new sharing changes visible in an existing work queue.
- Include the affected file or folder in the issue context.
- Support a consistent human review process for access changes.
Setup
Build it in a few focused steps.
- 1Connect Google Drive and Bitbucket once in the Notis portal.
- 2Create an automation in Automations, then choose New Automation.
- 3In one instruction, tell Notis what sharing changes should create an issue and what review context to include.
- 4Pick the Google Drive File Shared trigger and choose where run reports should go.
- 5Test with one real permission change and review the issue details.
Questions about this workflow
What does the File Shared trigger detect?
It starts when new sharing permissions are granted to a Drive file or folder.
Does the workflow revoke or change permissions?
No. The selected Bitbucket action creates an issue so a person can review and follow up.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Google Drive to Bitbucket. A trigger fires from one place; an action lands in another.
Google Drive triggers
Bitbucket actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create a branch
Creates a new branch in a bitbucket repository from a target commit hash; the branch name must be unique, adhere to bitbucket's naming conventions, and not include the 'refs/heads/' prefix.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create an issue
Creates a new issue in a bitbucket repository, setting the authenticated user as reporter; ensures assignee (if provided) has repository access, and that any specified milestone, version, or component ids exist.
Comment Added (Docs/Sheets/Slides)
Triggers when a new comment is added to Google Docs, Sheets, or Slides.
Create an issue comment
Adds a new comment with markdown support to an existing bitbucket issue.
File Created
Triggers when a new file is created in Google Drive.
Create a pull request
Creates a new pull request in a specified bitbucket repository, ensuring the source branch exists and is distinct from the (optional) destination branch.
File Deleted or Trashed
Triggers when a file is moved to trash or permanently deleted in Drive.
Create repository
Creates a new bitbucket 'git' repository in a specified workspace, defaulting to the workspace's oldest project if `project key` is not provided.
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 snippet comment
Posts a new top-level comment or a threaded reply to an existing comment on a specified bitbucket snippet.
File Updated
Triggers when a file's metadata or content changes in Google Drive.
Delete issue
Permanently deletes a specific issue, identified by its `issue id`, from the repository specified by `repo slug` within the given `workspace`.
Google Drive Changes
Triggers when changes are detected in a Google Drive.
Delete repository
Permanently deletes a specified bitbucket repository; this action is irreversible and does not affect forks.
Connect any two apps with Notis in the middle.
Google Drive and Bitbucket, 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 Bitbucket.