Gmail + HubSpot: every email logged as CRM activity.
Log Gmail messages as HubSpot engagements, find or create contacts from email recipients, and trigger HubSpot workflows from Gmail events.
Pick the way that fits your stack.
Pair pages are mirrored. Each direction gets its own dedicated page.
When something happens in Gmail, do it in HubSpot.
1 Gmail triggers wired to 23 HubSpot actions. Most-used pairing: New Email → Create Company.
Or fire it the other way around.
18 HubSpot triggers wired to 27 Gmail actions downstream.
See HubSpot → Gmail →Common Gmail → HubSpot workflows.
Pick a pairing to set it up in two minutes. Each one is a fully editable recipe.
Fires when a new email is received in Gmail. Returns full email content; enable "Include Attachments" to automatically download all file attachments.
Fires when a new email is received in Gmail. Returns full email content; enable "Include Attachments" to automatically download all file attachments.
Fires when a new email is received in Gmail. Returns full email content; enable "Include Attachments" to automatically download all file attachments.
Fires when a new email is received in Gmail. Returns full email content; enable "Include Attachments" to automatically download all file attachments.
Connect Gmail and HubSpot in five steps.
No code, no glue, no half-day setup. Each step is one click.
- 1ConnectAuthorize Gmail and HubSpot
Open TinyCommand, authorize Gmail and HubSpot once each. Both connections are available to every workflow on your account.
- 2TriggerPick a Gmail trigger
Drop the Gmail → New Email trigger onto the canvas. TinyCommand auto-registers the webhook.
POST /v1/webhooks/google-gmail.trigger-email-received - 3TransformAdd a filter or AI step
Optionally add a Filter node ("subject contains URGENT") or an AI step ("classify intent") between trigger and action.
- 4ActionAdd the HubSpot action
Drop the HubSpot → Create Company action below it. Map fields from the Gmail payload into the HubSpot inputs.
hubspot.create-company - 5PublishPublish and forget
Hit Publish. TinyCommand runs it in production from second one. Watch the run-log fill up.