Turn a new Drive prospect brief into a personalized sales email
A new prospect brief can become a relevant first draft without switching between Drive and Autobound.
Trigger
File Created
Triggers when a new file is created in Google Drive.
Action
Generate Personalized Content
Tool to generate hyper-personalized sales content. Use after confirming contact and user details.
Why this helps
Prospect context sits in a document while writing the first outreach email becomes another task to remember.
- Use prospect details from the new brief as email context.
- Reduce copy and paste between Drive and Autobound.
- Surface missing contact or user details for follow up.
Setup
Build it in a few focused steps.
- 1Connect Google Drive and Autobound once in the Notis portal.
- 2Create an automation by telling Notis the outcome in plain language.
- 3Pick Google Drive File Created as the trigger and choose where run reports go.
- 4Test with one real prospect brief and review the generated email.
Questions about this workflow
What does this automation use as context?
It uses information available in the newly created Drive file. Contact and user details required by Autobound must be present or supplied separately.
Does it send the email automatically?
The action generates personalized content. Review the result and handle sending through your sales process.
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.