Skip to content
Notis

Check accessible Cursor repositories from a matching Drive file

Turn a matching Drive request into a quick inventory of GitHub repositories accessible through the connected Cursor account.

Trigger

New File Matching Query

Triggers when a new Google Drive file matches a provided query. This is the legacy query-centric trigger: it preserves Drive API query config such as ``corpora`` / ``driveId`` aliases and emits the historical ``file_matching_query`` event type. ``FileCreatedTrigger`` covers the broader "new file" case and emits ``file_created``.

Action

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.

Why this helps

Repository access checks can become a separate task that gets postponed while a founder is already working through a handoff.

  • Start an access inventory when a relevant Drive file appears.
  • See which GitHub repositories Cursor reports as accessible.
  • Keep the check attached to the request that prompted it.

Setup

Build it in a few focused steps.

  • 1Connect Google Drive and Cursor once in the Notis portal.
  • 2Create an automation in Automations, New Automation, and give it a clear name and prompt.
  • 3In one instruction, tell Notis to list accessible GitHub repositories and summarize them for the matching file's request.
  • 4Pick New File Matching Query as the trigger and choose where run reports should go.
  • 5Test with a real newly created file that matches your Drive query.

Questions about this workflow

Does the action change repository permissions?

No. It lists repositories accessible through the authenticated Cursor account and does not change access.

What does the Drive query control?

The trigger uses the query configured for New File Matching Query. Notis setup uses the selected trigger and does not require building filters as setup steps.

When this happens · Trigger

Do this · Action

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

Connect any two apps with Notis in the middle.

Google Drive and Cursor, or any other combination from 1,000+ integrations.

When this happens · Trigger

Do this · Action

Save your first hour today.

7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Cursor.