Connect Google Calendar to Cursor

When something happens in Google Calendar, Notis takes the next step in Cursor. 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 Google Calendar to Cursor

View example

Get a Cursor agent brief before your meeting

Before a calendar event starts, review active Cursor agents and bring their status into your meeting prep.

View example

Check which Cursor repositories are available for a new meeting

When a calendar event is created, list repositories accessible through Cursor and prepare a concise context note for the event.

View example

Review a Cursor agent conversation when an attendee accepts

When an attendee accepts a calendar invite, retrieve a specified Cursor agent conversation and summarize relevant discussion for meeting prep.

View example

Check Cursor agents after a meeting detail changes

When an event changes, review Cursor agent statuses and prepare a note that helps you reassess the meeting plan.

View example

Recover Cursor agent context after a meeting is canceled

When a calendar event is canceled, retrieve a specified Cursor agent conversation and summarize any useful follow-up context.

View example

Review Cursor Cloud agents on a recurring schedule

On a schedule, list Cursor Cloud agents and produce a compact status review to help keep open work visible.

View example

Check available Cursor models when a project needs a model review

Start a Notis webhook when you want a current list of Cursor models, then receive a concise model availability report.

View example

Keep Cursor API key details in a scheduled review

On a recurring schedule, retrieve Cursor API key information and report its name, creation date, and owner email for an access review.

View example

Create an on-demand inventory of Cursor-accessible repositories

Trigger a Notis webhook to retrieve the GitHub repositories accessible through Cursor and receive a concise inventory.

Supported Triggers and Actions

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

Google Calendar triggers

Cursor actions

Recurring trigger

Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.

TriggerScheduled

Get Agent Conversation

Tool to retrieve the conversation history for a specific cloud agent. Use when you need to view the messages exchanged between the user and the agent. Returns error with status 404 if the agent is not found or access is denied.

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

Get API Key Info

Tool to retrieve API key information including the key name, creation date, and owner email. Use when you need to verify API key details or validate authentication.

ActionInstant

Attendee Response Changed

Polling trigger that fires when any attendee's RSVP changes to accepted, declined, or tentative. Returns attendee info and current status.

TriggerPolling

List Agents

Tool to retrieve a paginated list of all Cursor Cloud agents. Use when you need to view existing agents, their status, or iterate through agents with pagination.

ActionInstant

Event Canceled or Deleted

Triggers when a Google Calendar event is cancelled or deleted. Returns minimal data: event_id, summary (if available), and cancellation timestamp.

TriggerPolling

List Available Models

Tool to retrieve the list of available AI models in Cursor. Use when you need to discover which models are available for API requests.

ActionInstant

Event Starting Soon

Triggers when a calendar event is within a configured number of minutes from starting. Returns event details, time remaining, attendees, and join links when available.

TriggerPolling

List GitHub Repositories

Tool to list GitHub repositories accessible to the authenticated user. Use when you need to retrieve all repositories the user has access to through their Cursor account.

ActionInstant

Calendar Event Changes

**SOON TO BE DEPRECATED** - Use Calendar Event Sync (polling trigger) instead. Real-time webhook trigger for calendar event changes. Returns event metadata only. For full event data, use Calendar Event Sync (polling trigger).

TriggerInstant

Event Created

Polling trigger that fires when a new calendar event is created. Returns event ID, summary, start/end times, and organizer info.

TriggerPolling

Calendar Event Sync

Polling trigger that returns full event data including details, attendees, and metadata. For real-time notifications with basic info, use Calendar Event Changes (webhook).

TriggerPolling

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.