Carry a Drive sharing handoff into Conveyor
When someone grants Drive access to a review file, keep the related Conveyor authorization step from slipping 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
Create new authorization
Tool to create a new authorization. Use when you need to grant access by email or from a prior authorization request.
Why this helps
A file may be shared in Drive while the corresponding customer access still needs to be granted in Conveyor.
- Notice permission grants while the sharing context is timely.
- Reduce the chance of a customer waiting on a separate Conveyor authorization.
- Keep an access handoff visible through Notis run reports.
Setup
Build it in a few focused steps.
- 1Connect Google Drive and Conveyor once in the Notis portal.
- 2Create an automation in Automations, New Automation, and name the access handoff.
- 3Tell Notis: when a Drive sharing permission is added, determine the intended recipient and create a matching Conveyor authorization only when the necessary recipient details are available; report missing details.
- 4Choose the Google Drive File Shared trigger and select where run reports should go.
- 5Test with one real permission change and verify the authorization details in Conveyor.
Questions about this workflow
Does every Drive share identify a valid Conveyor recipient?
Not necessarily. The workflow needs recipient details that Conveyor can use. Have Notis report missing or ambiguous details rather than guessing.
Can this revoke existing access?
No. This workflow uses Create new authorization. Revoking or changing existing authorization access uses a different action.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Google Drive to Conveyor. A trigger fires from one place; an action lands in another.
Google Drive triggers
Conveyor actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Delete a Conveyor document
Tool to delete a specific document. Use when you need to remove a document by its ID.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Delete folder
Tool to delete a folder by its ID. Use when you need to remove a specific folder after confirming its ID.
Comment Added (Docs/Sheets/Slides)
Triggers when a new comment is added to Google Docs, Sheets, or Slides.
Generate/Validate API Token Guidance
Tool to validate API token and provide guidance. Conveyor does not support API-based token creation; tokens must be created in the Conveyor UI. This action performs a real API call (using the provided metadata) to validate the existing API token and returns structured guidance.
File Created
Triggers when a new file is created in Google Drive.
Get Authorization Request
Tool to fetch details of a specific authorization request. Use when you need to retrieve metadata by authorization_request_id.
File Deleted or Trashed
Triggers when a file is moved to trash or permanently deleted in Drive.
Get Authorization Requests
Tool to fetch authorization requests. Use when you need to list authorization requests, optionally filtered by status.
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.
Get all authorization requests
Tool to retrieve all authorization requests. Use when you need to list all authorizations; optionally filter by status. Use after authenticating with a valid API token.
File Updated
Triggers when a file's metadata or content changes in Google Drive.
Get all Conveyor connections
Tool to retrieve all connections. Use when you need to fetch the complete list of your Conveyor connections. Use after authenticating with a valid API key.
Google Drive Changes
Triggers when changes are detected in a Google Drive.
Get all Conveyor documents
Tool to retrieve all documents. Use after authenticating with a valid API key.
Connect any two apps with Notis in the middle.
Google Drive and Conveyor, 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 Conveyor.