Verify an email address when a Drive file is shared
New sharing can signal that a collaborator is ready to work. Have Notis check a relevant email address in the file with Bouncer as part of the handoff.
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
Verify Email
Tool to verify a single email address in real-time. use when validating email entry form inputs instantly.
Why this helps
A new collaborator or partner can get access before anyone checks whether the related contact address is valid.
- Tie an email check to a file sharing change.
- Avoid manually switching to an email validation tool during a handoff.
- Get a report when the verification runs.
Setup
Build it in a few focused steps.
- 1Connect Google Drive and Bouncer once in the Notis portal.
- 2Create an automation in Notis, or tell Notis from any channel what you want it to do.
- 3In one instruction, ask Notis to identify the relevant email address in a newly shared file and verify it with Bouncer.
- 4Choose the Google Drive File Shared trigger and select where run reports should go.
- 5Test with one real file sharing change and confirm the intended address is verified.
Questions about this workflow
Does Bouncer verify the person who received file access?
The action verifies a single email address. Tell Notis which address to identify from the available file context; do not assume that a permission change alone contains the intended contact address.
Will it verify every address in a shared file?
Verify Email checks one address per action. For a list of multiple addresses, use a batch request workflow.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Google Drive to Bouncer. A trigger fires from one place; an action lands in another.
Google Drive triggers
Bouncer actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Check Toxicity List Job Status
Tool to check the status of a specific toxicity list job. use after creating a toxicity list job to poll its status until completion.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Batch Request
Tool to initiate a batch email verification request. use when you have multiple emails to verify in one api call. returns a batch id and initial status.
Comment Added (Docs/Sheets/Slides)
Triggers when a new comment is added to Google Docs, Sheets, or Slides.
Create Toxicity List Job
Tool to create a toxicity analysis job for a list of email addresses. use when you need to batch-process toxicity checks for multiple emails at once.
File Created
Triggers when a new file is created in Google Drive.
Delete batch request
Tool to delete a batch verification request. use when you need to remove all associated emails and results for a specific batch after confirming that the batch data is no longer required.
File Deleted or Trashed
Triggers when a file is moved to trash or permanently deleted in Drive.
Delete Toxicity List Job
Tool to delete a specific toxicity list job. use when you need to remove a completed or unwanted toxicity analysis job after confirming its id.
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.
Finish Batch
Tool to mark a batch verification process as finished. use after batch processing completes to stop further verifications and reclaim unused credits.
File Updated
Triggers when a file's metadata or content changes in Google Drive.
Get Batch Results
Tool to retrieve the results of a batch verification process. use after submitting a batch to fetch all processed email verification outcomes.
Google Drive Changes
Triggers when changes are detected in a Google Drive.
Verify Domain
Tool to verify the validity and configuration of a domain. use when you need to confirm the domain's mx records and catch-all behavior.
Connect any two apps with Notis in the middle.
Google Drive and Bouncer, 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 Bouncer.