Review BTCPay webhooks when a runbook is shared
When a runbook is shared with new collaborators, make the store's current webhook setup easy to review alongside it.
Trigger
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.
Action
List Store Webhooks
Tool to list all webhooks registered for a store. use when you need to retrieve the configured webhooks for management or auditing.
Why this helps
Sharing an integration runbook can widen access to operational context while the actual webhook configuration remains out of sight.
- Pair a sharing event with a webhook inventory report
- Make configuration review part of sharing handoffs
- Get results in your chosen Notis report channel
Setup
Build it in a few focused steps.
- 1Connect Google Drive and BTCPay Server once in the Notis portal.
- 2Create an automation in Automations, New Automation, or tell Notis what you want from any channel.
- 3In one instruction, ask Notis to list webhooks for the confirmed store when the specified runbook gains sharing permissions.
- 4Pick the Google Drive File Shared trigger and choose where run reports should go.
- 5Test by sharing the runbook with one collaborator and reviewing the returned webhook list.
Questions about this workflow
Does this change sharing or webhook permissions?
No. The workflow responds to a Drive sharing event by listing configured store webhooks.
What if the store has no webhooks?
The run report can show the result returned by BTCPay. Include the store ID so Notis can query the intended store.
When this happens · Trigger
Do this · Action
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.
Create Payment Request
Tool to create a new payment request for a store. use after confirming store id.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Store
Tool to create a new store in btcpay server. use when you need to provision a new store before processing transactions.
Comment Added (Docs/Sheets/Slides)
Triggers when a new comment is added to Google Docs, Sheets, or Slides.
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.
File Created
Triggers when a new file is created in Google Drive.
Register a Webhook
Tool to register a new webhook. use when you need to receive store event notifications.
File Deleted or Trashed
Triggers when a file is moved to trash or permanently deleted in Drive.
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.
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.
Delete Payment Request
Tool to delete a specific payment request. use when you need to archive/remove an existing payment request for a store.
File Updated
Triggers when a file's metadata or content changes in Google Drive.
Delete Store Payout
Tool to delete a specific payout from a store. use when you need to cancel a payout no longer needed.
Google Drive Changes
Triggers when changes are detected in a Google Drive.
Get API Key
Tool to retrieve the current api key. use after authentication to get api key details.
Connect any two apps with Notis in the middle.
Google Drive and Btcpay server, 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 Btcpay server.