Connect Google Drive to Anchor browser

When something happens in Google Drive, Notis takes the next step in Anchor browser. 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 Anchor browser

View example

Turn Drive comments into browser research context

When a comment is added to a Drive document, retrieve the referenced webpage so the team has the source context alongside the discussion.

View example

Prepare new Drive files for browser forms

When a new file is created in Drive, upload it as an agent resource to an active Anchor browser session for a web form workflow.

View example

Check a webpage after a Drive document changes

When a Drive file is updated, retrieve a related webpage in Anchor browser to support a quick content or source review.

View example

Capture a browser snapshot when a Drive file is shared

When Drive grants new file permissions, capture a screenshot of the related webpage in a specified Anchor browser session for a visual review record.

View example

Review browser sessions on a schedule

On a recurring schedule, list Anchor browser sessions so you can spot active and inactive sessions that need attention.

View example

Review a reference webpage after Drive changes

When Google Drive changes are detected, retrieve a specified reference webpage in Anchor browser to support a timely review.

View example

Snapshot a webpage for a matching Drive file

When a newly created Drive file matches a query, capture a screenshot of a specified webpage in an Anchor browser session for quick review.

Supported Triggers and Actions

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

Google Drive triggers

Anchor browser actions

Recurring trigger

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

TriggerScheduled

Create Profile

Tool to create a new browser profile from an active session. use after ending a session to persist cookies and cache.

ActionInstant

Webhook trigger

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

TriggerInstant

Delete Profile

Tool to delete a browser profile by id. use after confirming the profile exists.

ActionInstant

Comment Added (Docs/Sheets/Slides)

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

TriggerPolling

End All Sessions

Tool to end all active browser sessions. use after confirming a security concern when you need to immediately close every session for the authenticated user.

ActionInstant

File Created

Triggers when a new file is created in Google Drive.

TriggerPolling

End Browser Session

Tool to end a specific browser session by id. use after confirming the session id you want to terminate.

ActionInstant

File Deleted or Trashed

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

TriggerPolling

Get Profile

Tool to fetch details for a specific browser profile by id. use after you know the profile id and need its settings and session information.

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

Get Webpage Content

Tool to retrieve rendered content of a webpage in html or markdown format. use when you need to fetch a page’s full content, optionally within an existing browser session.

ActionInstant

File Updated

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

TriggerPolling

List Agent Resources

Tool to list agent resources (files) for a given session. use after establishing a browser session to retrieve agent-uploaded files.

ActionInstant

Google Drive Changes

Triggers when changes are detected in a Google Drive.

TriggerPolling

List All Sessions Status

Tool to list the status of all active browser sessions. use after authenticating when you need to retrieve an up-to-date overview of all sessions.

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.