Connect Google Drive to Bugherd

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

View example

Turn Drive review notes into Bugherd tasks

Convert actionable comments on Google Docs, Sheets, or Slides into clear Bugherd tasks for the right project.

View example

Create Bugherd tasks from new Drive bug reports

When a new Drive file is a bug report, create a structured Bugherd task with its source link.

View example

Refresh Bugherd tasks when Drive specs change

Use updates to a Drive specification to revise the related Bugherd task when the change affects its scope or acceptance details.

View example

Attach shared Drive design files to Bugherd tasks

When a Drive file is shared, attach its link to the related Bugherd task when the task reference is clear.

View example

Add Drive review comments to Bugherd discussions

Append relevant document feedback to an existing Bugherd task discussion when the comment identifies that task.

View example

Attach new Drive reproduction videos to Bugherd

Attach a new Drive reproduction video to its referenced Bugherd task when the file has an accessible URL.

View example

Post changed QA notes to the Bugherd task

When a QA notes file changes, add a concise update to the referenced Bugherd task discussion.

View example

Record Drive access changes in the related Bugherd task

Add a task discussion note when a shared Drive file's access changes and the related task is clearly identified.

View example

Turn Drive design approval requests into Bugherd tasks

Create a Bugherd task for a new Drive design approval request when it describes review work.

Supported Triggers and Actions

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

Google Drive triggers

Bugherd actions

Recurring trigger

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

TriggerScheduled

Add Guest to Project

Tool to add a guest (client) to a project. use when you want to add an existing client by id or invite a new client by email.

ActionInstant

Webhook trigger

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

TriggerInstant

Add Member to Project

Tool to add a member to a project in bugherd. use when you need to add an existing user to a specific project.

ActionInstant

Comment Added (Docs/Sheets/Slides)

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

TriggerPolling

Create Attachment

Tool to add a new attachment to a task using an existing url. use when you have project and task ids and the external file url ready.

ActionInstant

File Created

Triggers when a new file is created in Google Drive.

TriggerPolling

Create Column

Tool to create a new column in a project. use when you need to add a custom workflow column after identifying the project id.

ActionInstant

File Deleted or Trashed

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

TriggerPolling

Create Comment

Tool to add a new comment to a task. use when you need to record discussion or feedback on an existing task.

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

Create Project

Tool to create a new project. use when you need to initialize a project after gathering its name and url. example: "create a new project named 'my website' with url 'http://www.example.com'."

ActionInstant

File Updated

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

TriggerPolling

Create Task

Tool to add a new task in a project. use when you have the project id and full task details ready.

ActionInstant

Google Drive Changes

Triggers when changes are detected in a Google Drive.

TriggerPolling

Create Webhook

Tool to create a new webhook for real-time event notifications. use when you need to configure a callback endpoint for task or comment events. example: "create a webhook for 'task create' events to be sent to 'https://example.com/webhook'."

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.