Validate emails in changed Drive content
When Drive detects changes, check the email addresses in the affected content and get a short result summary.
Trigger
Google Drive Changes
Triggers when changes are detected in a Google Drive.
Action
Email Validation
Tool to validate whether an email address is real and deliverable. use after collecting an email address to confirm deliverability.
Why this helps
Changes across Drive can be easy to overlook when you are juggling several active documents.
- Check addresses in changed Drive content
- Reduce manual review across files
- Get a concise summary of validation results
Setup
Build it in a few focused steps.
- 1Connect Google Drive and Abstract once in the Notis portal.
- 2Create an automation by telling Notis what outcome you want, from any channel or in Automations, New Automation.
- 3In one instruction, ask Notis to inspect changed file content for email addresses, validate them with Abstract, and summarize the results.
- 4Pick the Google Drive Changes trigger and choose where run reports go.
- 5Test with one real Drive change involving a file with an email address.
Questions about this workflow
What starts this workflow?
The Google Drive Changes event starts it when changes are detected in Drive.
Can it tell whether an address is newly added?
The trigger reports Drive changes. If you need to distinguish newly added addresses from existing ones, provide that comparison data in your instruction or source material.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Google Drive to Abstract. A trigger fires from one place; an action lands in another.
Google Drive triggers
Abstract actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Validate IBAN
Tool to validate the format and country code of an iban number. use after collecting an iban to ensure it is correctly formatted.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Email reputation
Tool to enrich an email address with reputation and risk scoring data. use when you need to assess an address's deliverability and risk before outreach. use after confirming your api key is valid.
Comment Added (Docs/Sheets/Slides)
Triggers when a new comment is added to Google Docs, Sheets, or Slides.
Email Validation
Tool to validate whether an email address is real and deliverable. use after collecting an email address to confirm deliverability.
File Created
Triggers when a new file is created in Google Drive.
File Deleted or Trashed
Triggers when a file is moved to trash or permanently deleted in Drive.
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.
File Updated
Triggers when a file's metadata or content changes in Google Drive.
Google Drive Changes
Triggers when changes are detected in a Google Drive.
Connect any two apps with Notis in the middle.
Google Drive and Abstract, 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 Abstract.