Create Apollo contacts from shared Drive prospect files
When a prospect file is shared with your team, Notis can carry the details into Apollo so the handoff includes a contact record.
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
Create Apollo contact
Creates a new contact in apollo.io; use `account id` to link to an organization and `contact stage id` for sales stage, noting that apollo does not perform automatic deduplication.
Why this helps
A shared prospect file can start a handoff, but the contact still needs to be entered in Apollo by hand.
- Connect a file sharing event to a contact creation step.
- Use prospect details contained in the shared file.
- Make a shared lead easier to follow up in Apollo.
Setup
Build it in a few focused steps.
- 1Connect Google Drive and Apollo once in the Notis portal.
- 2Create an automation in the portal or tell Notis from any channel.
- 3In one instruction, ask Notis to create an Apollo contact from prospect details in the newly shared file.
- 4Pick the Google Drive File Shared trigger and choose where run reports should go.
- 5Test with one real shared prospect file containing the required contact details.
Questions about this workflow
Does sharing a file provide enough information to create a contact?
Only if the file or available sharing details contain the contact information needed for the Apollo contact. Notis should not guess missing details.
Will Apollo check for an existing contact first?
The create contact action does not automatically deduplicate. Review for an existing contact before relying on repeated sharing events.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Google Drive to Apollo. A trigger fires from one place; an action lands in another.
Google Drive triggers
Apollo actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Add Contacts to Sequence
Adds contacts to a specified apollo email sequence by initiating an asynchronous background job and returning its details.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Bulk organization enrichment
Enriches data for up to 10 organizations simultaneously by providing a list of their base company domains (e.g., 'apollo.io', not 'www.apollo.io').
Comment Added (Docs/Sheets/Slides)
Triggers when a new comment is added to Google Docs, Sheets, or Slides.
Bulk people enrichment
Use to enrich multiple person profiles simultaneously with comprehensive data from apollo's database.
File Created
Triggers when a new file is created in Google Drive.
Bulk update account stage
Bulk updates the stage for specified existing apollo.io accounts, moving them to a valid new account stage.
File Deleted or Trashed
Triggers when a file is moved to trash or permanently deleted in Drive.
Create an Apollo account
Creates a new account in apollo.io; a new record is created even if a similar account exists, and provided `owner id` or `account stage id` must be valid existing ids.
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.
Create Apollo contact
Creates a new contact in apollo.io; use `account id` to link to an organization and `contact stage id` for sales stage, noting that apollo does not perform automatic deduplication.
File Updated
Triggers when a file's metadata or content changes in Google Drive.
Create Apollo deal
Creates a new sales opportunity (deal) in apollo.io; all provided ids (`owner id`, `account id`, `opportunity stage id`) must be valid existing apollo identifiers.
Google Drive Changes
Triggers when changes are detected in a Google Drive.
Create Apollo Task
Creates a distinct apollo.io task for each contact id in contact ids, assigning them to user id; this action is not for free plan users and repeated calls create duplicate tasks.
Connect any two apps with Notis in the middle.
Google Drive and Apollo, 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 Apollo.