Connect Google Drive to Cursor

When something happens in Google Drive, 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 Drive to Cursor

View example

Review a Cursor agent from a Drive comment

Use a Google Docs, Sheets, or Slides comment to request a review of a specific Cursor cloud agent conversation.

View example

Create a Cursor agent status brief from a Drive file

When a new Drive file signals a need for a status check, retrieve the current Cursor cloud agent list and summarize its statuses.

View example

Check Cursor repository access for a Drive request

When a new Drive file matches a query, list the GitHub repositories accessible through Cursor and report the results relevant to the request.

View example

Check Cursor model availability after a Drive update

Use an updated Drive planning file to retrieve Cursor's available models and summarize the returned list for the decision at hand.

View example

Check Cursor API key ownership after Drive sharing changes

When a Drive file or folder receives new sharing permissions, retrieve Cursor API key details and report the returned owner and key metadata for review.

View example

Review Cursor's agent list after Drive changes

Use a detected Drive change as a cue to retrieve Cursor's cloud agent list and summarize returned statuses for a handoff or project review.

View example

Capture a Cursor repository access snapshot after a Drive deletion

When a Drive file is trashed or deleted, retrieve the repositories accessible through Cursor and include the returned list in a review report.

View example

Schedule a review of Cursor API key details

On a recurring schedule, retrieve Cursor API key metadata and send the returned name, creation date, and owner email for review.

Supported Triggers and Actions

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

Google Drive 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

Comment Added (Docs/Sheets/Slides)

Triggers when a new comment is added to Google Docs, Sheets, or Slides.

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

File Created

Triggers when a new file is created in Google Drive.

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

File Deleted or Trashed

Triggers when a file is moved to trash or permanently deleted in Drive.

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

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.

TriggerPolling

File Updated

Triggers when a file's metadata or content changes in Google Drive.

TriggerPolling

Google Drive Changes

Triggers when changes are detected in a Google Drive.

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.