Check current readings when a relevant Drive file appears
Use an existing Drive query to identify the files that matter, then have Notis retrieve your Ambient Weather devices' latest readings.
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
Get Devices
Tool to retrieve a list of user's ambient weather devices with their most recent data. use when you need to list your stations and view their latest readings.
Why this helps
Important planning files can get buried among unrelated Drive uploads, making it harder to remember the supporting conditions check.
- Start from files that match your Drive query
- Pair relevant new files with a current device check
- Keep routine review work focused
Setup
Build it in a few focused steps.
- 1Connect Google Drive and Ambient Weather once in the Notis portal.
- 2Create an automation in Automations, then New Automation, and give it a name.
- 3Describe in one instruction how to retrieve current readings when a matching operations file appears.
- 4Pick the Google Drive New File Matching Query trigger and choose where run reports should go.
- 5Test with one real file that matches your query.
Questions about this workflow
How is this different from the File Created trigger?
This legacy query-centric trigger starts when a new file matches a provided Drive query, while File Created covers new files broadly.
Can Notis create the Drive query for me?
The trigger preserves Drive query configuration. Use an existing query setup for the files you want it to match.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Google Drive to Ambient weather. A trigger fires from one place; an action lands in another.
Google Drive triggers
Ambient weather actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Devices
Tool to retrieve a list of user's ambient weather devices with their most recent data. use when you need to list your stations and view their latest readings.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Comment Added (Docs/Sheets/Slides)
Triggers when a new comment is added to Google Docs, Sheets, or Slides.
File Created
Triggers when a new file is created in Google Drive.
File Deleted or Trashed
Triggers when a file is moved to trash or permanently deleted in Drive.
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.
File Updated
Triggers when a file's metadata or content changes in Google Drive.
Google Drive Changes
Triggers when changes are detected in a Google Drive.
Connect any two apps with Notis in the middle.
Google Drive and Ambient weather, 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 Ambient weather.