Skip to content
Notis

Batch verify prospects in query-matched Drive files

Let your existing Drive query determine which new files need attention, then have Notis send their email addresses to Bouncer as a batch.

Trigger

New File Matching Query

Triggers when a new Google Drive file matches a provided query. This is the legacy query-centric trigger: it preserves Drive API query config such as ``corpora`` / ``driveId`` aliases and emits the historical ``file_matching_query`` event type. ``FileCreatedTrigger`` covers the broader "new file" case and emits ``file_created``.

Action

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.

Why this helps

Relevant prospect files can be scattered across Drive, making it harder to catch each new list for verification.

  • Use a Drive query to identify relevant new files.
  • Start Bouncer verification for the matched file's addresses.
  • Avoid checking folders manually for new lists.

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 extract email addresses from each matching new file and start a Bouncer batch request.
  • 4Choose the Google Drive New File Matching Query trigger and select where run reports should go.
  • 5Test with one real file that matches the configured query and confirm a batch request starts.

Questions about this workflow

Can Notis set up the Drive query filters for me?

No. Configure the query for the Google Drive trigger in its available setup, then choose that trigger in Notis.

How is this different from the File Created trigger?

This trigger starts for new files matching its configured query, while File Created starts for new Drive files more broadly.

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.

TriggerScheduled

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.

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

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.

ActionInstant

Comment Added (Docs/Sheets/Slides)

Triggers when a new comment is added to Google Docs, Sheets, or Slides.

TriggerPolling

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.

ActionInstant

File Created

Triggers when a new file is created in Google Drive.

TriggerPolling

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.

ActionInstant

File Deleted or Trashed

Triggers when a file is moved to trash or permanently deleted in Drive.

TriggerPolling

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.

ActionInstant

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.

TriggerPolling

Finish Batch

Tool to mark a batch verification process as finished. use after batch processing completes to stop further verifications and reclaim unused credits.

ActionInstant

File Updated

Triggers when a file's metadata or content changes in Google Drive.

TriggerPolling

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.

ActionInstant

Google Drive Changes

Triggers when changes are detected in a Google Drive.

TriggerPolling

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.

ActionInstant

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.