Check Appdrag records when Drive changes are detected
Drive changes can affect active work in several ways. Query Appdrag for related records to make the next review more focused.
Trigger
Google Drive Changes
Triggers when changes are detected in a Google Drive.
Action
Visual SQL SELECT
Tool to execute a Visual SELECT Cloud Backend function. Use when you need to read rows from a database table using a visual SQL function configured in AppDrag.
Why this helps
Broad change activity makes it hard to tell which tracked records may need attention.
- Use the Drive changes trigger for broader change detection.
- Look up related records through an Appdrag SELECT function.
- Give reviewers a starting point for follow-up.
Setup
Build it in a few focused steps.
- 1Connect Google Drive and Appdrag once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a name and prompt.
- 3Tell Notis to run the Appdrag Visual SQL SELECT function to find records relevant to the detected Drive change.
- 4Pick the Google Drive Changes trigger and choose where run reports should go.
- 5Test with one real change and review the lookup result.
Questions about this workflow
Is this trigger limited to new files?
No. It triggers when changes are detected in a Google Drive.
Will it decide whether a record needs updating?
It can return matching data for review. A reliable decision depends on the details available from the change and the SELECT function.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Google Drive to Appdrag. A trigger fires from one place; an action lands in another.
Google Drive triggers
Appdrag actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Execute Cloud Backend function via DELETE
Tool to execute a Cloud Backend API function via DELETE on the default environment. Use when you need to call a function with DELETE parameters and optional APIKey.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Execute Preprod Function (DELETE)
Tool to execute the pre-production version of a Cloud Backend API function via DELETE. Use when you need to test or validate delete operations in the preprod environment before production deployment.
Comment Added (Docs/Sheets/Slides)
Triggers when a new comment is added to Google Docs, Sheets, or Slides.
Execute PROD API Function (GET)
Tool to execute a production Cloud Backend API function via GET. Includes robust URL handling and fallbacks to accommodate management base URLs.
File Created
Triggers when a new file is created in Google Drive.
Execute Dev Function (PATCH)
Tool to execute the development version of a Cloud Backend API function via PATCH. Use after deploying or updating your function to the dev environment.
File Deleted or Trashed
Triggers when a file is moved to trash or permanently deleted in Drive.
Execute Cloud Backend function via POST
Tool to execute a Cloud Backend API function via POST on the default environment. Use when you need to call a function with POST parameters and optional APIKey.
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.
Execute Function POST (Preprod Env)
Tool to execute a Cloud Backend API function via POST on the preprod environment. Use when you need to test a function in the preprod environment before releasing to production. Include apiKey if your function requires APIKey security.
File Updated
Triggers when a file's metadata or content changes in Google Drive.
Execute Cloud Backend function via PUT (default)
Tool to execute a Cloud Backend API function via PUT on the default environment. Use when you need to call a function with PUT parameters and optional APIKey.
Google Drive Changes
Triggers when changes are detected in a Google Drive.
Execute Cloud Backend function via PUT (preprod)
Tool to execute a Cloud Backend API function via PUT on the preprod environment. Use when you need to call a function with PUT parameters and optional APIKey in preprod.
Connect any two apps with Notis in the middle.
Google Drive and Appdrag, 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 Appdrag.