Create Hubspot email records from Drive meeting notes
Your team creates meeting notes in Drive. Notis creates corresponding email records in Hubspot so all follow-ups are tracked in one system.
Trigger
File Created
Triggers when a new file is created in Google Drive.
Action
Create email
Creates a new email engagement record in hubspot, requiring portal-specific `properties` (e.g., `hs timestamp` as a utc millisecond timestamp), and that association `to id`s and `associationtypeid`s are valid and existing.
Why this helps
Meeting action items are captured in Drive but never make it to Hubspot, so follow-up emails and tasks exist in two places.
- Track meeting follow-ups in Hubspot with full context
- Associate emails with contacts and deals from the meeting
- Stop managing action items in two places
Setup
Build it in a few focused steps.
- 1Connect Google Drive and Hubspot to Notis.
- 2Create an automation: 'When I create new meeting notes in Drive, create email records in Hubspot for the follow-ups mentioned.'
- 3Select the trigger: 'File Created' in your meeting notes folder.
- 4Set your notification channel.
- 5Test by creating meeting notes with follow-up items and verifying email records appear in Hubspot.
Questions about this workflow
Does Notis extract who was in the meeting automatically?
Notis reads attendee names from the document. Mention attendees at the top of your notes and Notis creates email associations automatically.
Can Notis create email records for each action item mentioned?
Yes. Use bullet points or a consistent format for action items and Notis creates one email record per item.
What if I have multiple meeting notes from one day?
Notis processes each file separately, creating email records for each set of meeting notes.
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 1,000+ 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.