Test query-matched Drive intake in Appdrag preprod
Check how matching files move through your Appdrag intake function before you rely on the process in production.
Trigger
New File Matching Query
Triggers when a new Google Drive file matches a provided query. This is the legacy query-centric trigger: it preserves Drive API query config such as ``corpora`` / ``driveId`` aliases and emits the historical ``file_matching_query`` event type. ``FileCreatedTrigger`` covers the broader "new file" case and emits ``file_created``.
Action
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.
Why this helps
A new intake rule can behave differently than expected, and production is a poor place to discover it.
- Use query-based matching to scope the incoming files.
- Exercise a pre-production Appdrag function.
- Catch intake issues before production use.
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.
- 3Describe how matching files should be sent to the Appdrag preprod POST function for validation.
- 4Pick the New File Matching Query trigger and choose where run reports should go.
- 5Test with one real query-matched file and inspect the preprod result.
Questions about this workflow
How does this trigger differ from File Created?
It is the legacy query-centric trigger and preserves Drive API query configuration such as corpora or driveId aliases.
Does this publish changes to production?
No. The selected POST action calls the Appdrag preprod environment.
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.