Connect Hubspot to Google Calendar

When something happens in Hubspot, Notis takes the next step in Google Calendar. Describe what you want in plain English, or start from one of the examples below.

When this happens · Trigger

Do this · Action

Build an automation Browse examples

Examples

Ways Notis can move work from Hubspot to Google Calendar

View example

Book a discovery call the moment a new HubSpot contact lands

A new contact in HubSpot instantly turns into a scheduled discovery call on your Google Calendar, so fresh leads never sit and cool off.

View example

Schedule the next-step meeting automatically when a deal moves stage

Every time a HubSpot deal advances, Notis creates the right next-step meeting on your Google Calendar so momentum never stalls between stages.

View example

Drop a follow-up reminder on your calendar for every new contact

A new HubSpot contact triggers a quick, natural-language follow-up event on Google Calendar, so first-touch reminders write themselves.

View example

Surface open calendar slots the moment a deal is ready to close

When a HubSpot deal reaches a key stage, Notis finds your free slots on Google Calendar so you can offer times without hunting through your week.

View example

Update the linked meeting automatically when a deal changes stage

When a HubSpot deal moves, Notis patches the related Google Calendar event so the meeting title, notes, and agenda always match the current stage.

View example

Clear the scheduled follow-up automatically when a deal is lost

When a HubSpot deal moves to closed lost, Notis deletes the related Google Calendar event so dead deals stop cluttering your week.

View example

Pull open meeting times the instant a new lead is created

A new HubSpot contact prompts Notis to find your free Google Calendar slots, so you can propose times to a fresh lead without opening your calendar.

View example

Get a daily agenda of your Google Calendar every morning

On a recurring schedule, Notis lists your Google Calendar events and sends you a clean morning briefing so your day starts with clarity, not surprises.

View example

Move the meeting to your clients calendar when a deal is won

When a HubSpot deal closes won, Notis moves the related event to your dedicated clients calendar so active work is cleanly separated from your pipeline.

Supported Triggers and Actions

Notis builds workflows that link Hubspot to Google Calendar. A trigger fires from one place; an action lands in another.

Hubspot triggers

Google Calendar actions

Contact Created Trigger

TriggerInstant

Insert Calendar into List

Inserts an existing calendar into the user's calendar list.

ActionInstant

Deal Stage UpdatedTrigger

TriggerInstant

Update Calendar List Entry

Updates an existing entry on the user\'s calendar list.

ActionInstant

Delete Calendar

Deletes a secondary calendar. use calendars.clear for clearing all events on primary calendars.

ActionInstant

Update Calendar

Updates metadata for a calendar.

ActionInstant

Clear Calendar

Clears a primary calendar. this operation deletes all events associated with the primary calendar of an account.

ActionInstant

Create Event

Creates an event on a google calendar, needing rfc3339 utc start/end times (end after start) and write access to the calendar. by default, adds the organizer as an attendee unless exclude organizer is set to true.

ActionInstant

Delete event

Deletes a specified event by `event id` from a google calendar (`calendar id`); this action is idempotent and raises a 404 error if the event is not found.

ActionInstant

Create a calendar

Creates a new, empty google calendar with the specified title (summary).

ActionInstant

Trigger Types

Four ways to start an automation.

A trigger is the event that kicks a workflow off. Notis supports four kinds: an event in a connected app, an inbound webhook, a recurring schedule, and soon, your own database.

Integration triggers

Fire when something happens inside a connected app. New Notion page, Stripe charge, Linear issue: any of 1,000+ apps can start a workflow.

New Notion pageStripe chargeCalendar event

Webhook triggers

A unique URL per workflow. Anything that can send an HTTP POST can start an automation, including no-code tools that speak webhooks.

Any HTTP POSTCustom backendIoT event

Works with

ZapierPipedream

Most used

Recurring triggers

Cron-style schedules run a workflow on the clock. Daily standups, hourly syncs, business-hours-only digests: the workhorse of Notis.

Daily · 8:00HourlyWeekdays only

Coming soon

Database triggers

Watch a row, query, or threshold in your own database and fire the moment the data changes. Row inserted, value crosses a limit, query starts matching.

Row insertedValue > limitQuery match

Why AI automation

Classic automation breaks. AI adapts.

Same triggers and actions, smarter middle. AI handles the fuzziness that breaks traditional Zapier-style workflows the moment a field gets renamed.

Classic automationAI automation

Cost

$ · pay per run

$$ · AI models per run

Reliability

Breaks on schema change

Adapts to format changes

Setup

Click 8 dropdowns

Describe it in English

Handles fuzzy

Hard-coded fields only

Reads intent, summarises

Human in loop

Bolted on

Built in · approval inbox

Maintenance

You own every break

Self-heals · we own it

Ease of use

Describe it. Notis builds it.

Skip the visual builder. Tell Notis what you want, in plain English. It writes the workflow, you review and deploy.

You · in the Notis Builder

NEW

“When a row gets added to the Q4 OKRs Notion database and the status is Blocked, send a Telegram message to the owner with a summary of what's blocking, and ping me if there's no reply within 24 hours.”

Notis built this automation:

TriggerRow added to "Q4 OKRs"

Condition✦Status = "Blocked"

AI step✦Summarise the blocker in plain English

ActionDM the row owner with summary

Timeout✦No reply in 24h → ping you

Observability

Watch every run.

Notis Desktop is Mission Control for your AI automations. See every run, replay, edit, or rewind. Set approval gates so Notis pauses before destructive actions.