Connect Google Drive to Btcpay server

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

View example

Turn a Drive payment brief into a BTCPay request

Create a BTCPay payment request when a new Drive document contains a complete payment brief and confirmed store details.

View example

Register a BTCPay webhook from an updated runbook

Use an updated Drive runbook to register a BTCPay store webhook when it specifies the store and webhook requirements.

View example

Review BTCPay requests when a Drive payment doc gets a comment

When a comment is added to a payment document, retrieve the store's BTCPay payment requests for a focused review.

View example

Audit BTCPay webhooks when a Drive runbook is shared

When a Drive runbook receives new sharing permissions, list the store's BTCPay webhooks and send the results to your chosen report channel.

View example

Check BTCPay store settings for a matching Drive file

When a new Drive file matches your configured query, retrieve the specified BTCPay store configuration for a contextual review.

View example

Retire a BTCPay request when its Drive campaign file is trashed

When a designated campaign file is trashed, delete its explicitly identified BTCPay payment request after confirming the request and store.

View example

Check BTCPay server readiness after Drive changes

Use a Google Drive change event to retrieve BTCPay server information for an operations readiness report.

View example

Pair a new store brief with a BTCPay app inventory

When a new Drive store brief is created, list the apps associated with its confirmed BTCPay store for an onboarding report.

Supported Triggers and Actions

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

Google Drive triggers

Btcpay server actions

Recurring trigger

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

TriggerScheduled

Create Payment Request

Tool to create a new payment request for a store. use after confirming store id.

ActionInstant

Webhook trigger

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

TriggerInstant

Create Store

Tool to create a new store in btcpay server. use when you need to provision a new store before processing transactions.

ActionInstant

Comment Added (Docs/Sheets/Slides)

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

TriggerPolling

Create BTCPay Server User

Tool to create a new btcpay server user. use when you need to register a new user programmatically as an administrator.

ActionInstant

File Created

Triggers when a new file is created in Google Drive.

TriggerPolling

Register a Webhook

Tool to register a new webhook. use when you need to receive store event notifications.

ActionInstant

File Deleted or Trashed

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

TriggerPolling

Delete API Key

Tool to revoke a specific api key. use when you need to remove an api key to immediately prevent its use. call after identifying the key to revoke.

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

Delete Payment Request

Tool to delete a specific payment request. use when you need to archive/remove an existing payment request for a store.

ActionInstant

File Updated

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

TriggerPolling

Delete Store Payout

Tool to delete a specific payout from a store. use when you need to cancel a payout no longer needed.

ActionInstant

Google Drive Changes

Triggers when changes are detected in a Google Drive.

TriggerPolling

Get API Key

Tool to retrieve the current api key. use after authentication to get api key details.

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.