Draft sales email from a query-matched Drive file
Turn a file that matches your Drive prospect query into a timely personalized email draft.
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
Generate Personalized Content
Tool to generate hyper-personalized sales content. Use after confirming contact and user details.
Why this helps
A promising prospect file can sit unnoticed after it matches a saved Drive search.
- Use a file match as a prompt to create a timely sales draft.
- Keep query-driven prospect research connected to outreach.
- Flag missing recipient or user details before content generation.
Setup
Build it in a few focused steps.
- 1Connect Google Drive and Autobound once in the Notis portal.
- 2Create an automation and describe the email outcome in one instruction.
- 3Pick Google Drive New File Matching Query as the trigger and choose where run reports go.
- 4Test with one real file that matches your Drive query.
Questions about this workflow
Does Notis create or configure the Drive query?
No. Choose the New File Matching Query trigger and use the existing query configuration. The automation instruction describes the desired outcome.
What if the matching file does not identify a contact?
Provide confirmed contact and user details in the instruction or resolve them before generating personalized content.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Google Drive to Autobound. A trigger fires from one place; an action lands in another.
Google Drive triggers
Autobound actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Generate Insights
Tool to generate ranked prospect or company insights. Use after resolving identifiers to retrieve the most relevant insights.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Generate Personalized Content
Tool to generate hyper-personalized sales content. Use after confirming contact and user details.
Comment Added (Docs/Sheets/Slides)
Triggers when a new comment is added to Google Docs, Sheets, or Slides.
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 Autobound, 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 Autobound.