Real-time triggers from Google Drive, ready-made actions in HubSpot. Filter, transform, and route without writing a line of code.
Workflows fire when something happens in Google Drive.
Pair pages are mirrored. Each direction gets its own dedicated page.
3 Google Drive triggers wired to 23 HubSpot actions. Most-used pairing: New File → Create Company.
18 HubSpot triggers wired to 8 Google Drive actions downstream.
See HubSpot → Google Drive →Pick a pairing to set it up in two minutes. Each one is a fully editable recipe.
Fires when a new file is created in Google Drive (optionally scoped to a specific folder). Common use: ingest new docs into your CMS, OCR receipts, or alert the team when a contract drops.
Fires when a new file is created in Google Drive (optionally scoped to a specific folder). Common use: ingest new docs into your CMS, OCR receipts, or alert the team when a contract drops.
Fires when a new file is created in Google Drive (optionally scoped to a specific folder). Common use: ingest new docs into your CMS, OCR receipts, or alert the team when a contract drops.
Fires when a new file is created in Google Drive (optionally scoped to a specific folder). Common use: ingest new docs into your CMS, OCR receipts, or alert the team when a contract drops.
Fires when a file in Google Drive is updated (content edited, renamed, moved, or re-shared). Used to re-index search, re-sync into your KB, or notify watchers.
Fires when a file in Google Drive is updated (content edited, renamed, moved, or re-shared). Used to re-index search, re-sync into your KB, or notify watchers.
Fires when a file in Google Drive is updated (content edited, renamed, moved, or re-shared). Used to re-index search, re-sync into your KB, or notify watchers.
Fires when a file in Google Drive is updated (content edited, renamed, moved, or re-shared). Used to re-index search, re-sync into your KB, or notify watchers.
Fires when a new folder is created in Google Drive (optionally scoped to a parent). Use for templated folder provisioning or governance audit logs.
No code, no glue, no half-day setup. Each step is one click.
Open TinyCommand, authorize Google Drive and HubSpot once each. Both connections are available to every workflow on your account.
Drop the Google Drive → New File trigger onto the canvas. TinyCommand auto-registers the webhook.
Optionally add a Filter node ("subject contains URGENT") or an AI step ("classify intent") between trigger and action.
Drop the HubSpot → Create Company action below it. Map fields from the Google Drive payload into the HubSpot inputs.
Hit Publish. TinyCommand runs it in production from second one. Watch the run-log fill up.
