Review DPD notification authenticity alongside sharing changes
When a Drive file is shared, Notis can run a DPD notification verification if the original notification signature and payload are available in the automation context.
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
Verify DPD Notification
Tool to verify a webhook notification's authenticity by posting back the original signature and payload. use after receiving a notification to confirm it originates from dpd.
Why this helps
A permissions change can trigger review work, while notification authenticity checks require locating the right verification step and original payload.
- Use a concrete Drive sharing event to start a review run.
- Invoke DPD's notification verification action when its required inputs are available.
- Keep verification runs visible through Notis reporting.
Setup
Build it in a few focused steps.
- 1Connect Google Drive and DPD once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a name.
- 3Describe in one instruction when to verify a DPD notification and ensure its original signature and payload are available to the run.
- 4Choose the File Shared trigger and select where run reports go.
- 5Test with a real sharing event and a real DPD notification payload.
Questions about this workflow
Does sharing a Drive file provide the DPD signature and payload?
No. The Drive sharing event describes a permission change. DPD verification requires the original notification signature and payload, which must be available separately in the run context.
Will the workflow approve a notification if verification fails?
The listed action verifies authenticity. The available action description does not specify additional response or approval behavior.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Google Drive to Dpd2. A trigger fires from one place; an action lands in another.
Google Drive triggers
Dpd2 actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Storefront
Tool to retrieve details of a specific storefront by its id. use when you need storefront metadata after you have its id.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
List DPD Customers
Tool to list customers in your dpd account. use when you need a filtered or paginated list of customers for reporting or synchronization.
Comment Added (Docs/Sheets/Slides)
Triggers when a new comment is added to Google Docs, Sheets, or Slides.
List DPD Purchases
Tool to list all purchases made through your dpd account. use when you need to retrieve purchase records with optional date filters and pagination for reporting or analysis.
File Created
Triggers when a new file is created in Google Drive.
List Storefronts
Tool to list all storefronts in your dpd account. use after authenticating to fetch storefront details before managing products or purchases.
File Deleted or Trashed
Triggers when a file is moved to trash or permanently deleted in Drive.
List Subscribers
Tool to list subscribers for a given storefront. use when you need a paginated and filtered list of subscribers after storefront setup.
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.
DPD: Ping API
Tool to ping the api to check its status. use when verifying api connectivity before further operations.
File Updated
Triggers when a file's metadata or content changes in Google Drive.
Verify DPD Notification
Tool to verify a webhook notification's authenticity by posting back the original signature and payload. use after receiving a notification to confirm it originates from dpd.
Google Drive Changes
Triggers when changes are detected in a Google Drive.
Connect any two apps with Notis in the middle.
Google Drive and Dpd2, 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 Dpd2.