Add prospects from Drive doc comments to Hubspot automatically
Your team discusses new prospects in a shared Google Doc. Every mention turns into a Hubspot contact automatically, no separate data entry needed.
Trigger
Comment Added (Docs/Sheets/Slides)
Triggers when a new comment is added to Google Docs, Sheets, or Slides.
Action
Create batch of contacts
Creates up to 100 new contact records in hubspot crm, optionally associating them with existing crm objects; ensure associated object ids are valid.
Why this helps
Great prospect ideas get lost in comment threads. You either forget to log them in Hubspot or re-read docs to find them all.
- Capture every prospect mentioned in team discussion without losing any
- Let your team brainstorm naturally while Hubspot stays updated
- Stop manually re-reading documents to find missed prospects
Setup
Build it in a few focused steps.
- 1Connect Google Drive and Hubspot to Notis.
- 2Create an automation: 'When someone comments with a prospect name or email in my shared Google Doc, add them as a contact in Hubspot.'
- 3Select the trigger: 'Comment Added' on your prospect document in Drive.
- 4Set your notification channel.
- 5Test by adding a comment in the doc mentioning a new prospect name and email, then verify in Hubspot.
Questions about this workflow
How does Notis know if a comment is about a prospect vs. random discussion?
You set this in your prompt. Tell Notis what format to watch for (e.g., 'names with email addresses' or comments marked with a tag like #prospect).
Does Notis create duplicates if a prospect is mentioned multiple times?
Notis checks Hubspot for existing contacts before creating new ones, avoiding duplicates.
Can this work for other fields besides prospect name and email?
Yes. Include company, title, or any field from the comment in your automation prompt and Notis extracts it.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Google Drive to Hubspot. A trigger fires from one place; an action lands in another.
Google Drive triggers
Hubspot actions
Comment Added (Docs/Sheets/Slides)
Triggers when a new comment is added to Google Docs, Sheets, or Slides.
Add asset association
Associates an existing asset ('form', 'object list', or 'external web url') with a specified hubspot marketing campaign.
File Created
Triggers when a new file is created in Google Drive.
Add token to event template
Adds a new custom data token to an existing event template for a specified hubspot application, optionally populating a crm object property if objectpropertyname is provided.
File Deleted or Trashed
Triggers when a file is moved to trash or permanently deleted in Drive.
Archive email
Archives the hubspot email specified by `emailid` by moving it to the recycling bin, making it inaccessible unless restored.
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.
Archive a batch of emails by ID
Archives multiple hubspot crm emails by id; ids must exist as archiving is irreversible.
File Updated
Triggers when a file's metadata or content changes in Google Drive.
Archive a batch of quotes by id
Archives a batch of existing, non-archived quotes by their ids; this action is irreversible and useful for managing outdated or irrelevant quotes.
Google Drive Changes
Triggers when changes are detected in a Google Drive.
Archive batch of companies by id
Archives a batch of companies by their unique ids; targeted companies must exist, not be previously archived, and this api operation is irreversible.
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``.
Archive batch of contacts by id
Archives a batch of existing contacts by their hubspot crm ids, rendering them inactive; this action is irreversible via the api and requires manual restoration or a separate unarchive endpoint.
Archive batch of deals by id
Archives a batch of existing deals by their unique hubspot ids, removing them from active views and reports (soft delete); archived deals may be restorable.
Connect any two apps with Notis in the middle.
Not just Google Drive and Hubspot. Any combination from 985+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7 days free trial with 20$ free usage included.
No card. Works with personal or business Hubspot.