Keep a seasonal conditions check on your operations routine
When conditions matter more to operations, a recurring device check can help keep the latest readings visible without relying on memory.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
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
Seasonal routines tend to start with good intentions, then disappear under the week-to-week demands of running a business.
- Keep a seasonal check visible through a recurring schedule
- Review the latest readings available from your devices
- Reduce missed checks during busy periods
Setup
Build it in a few focused steps.
- 1Connect 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 device readings for your seasonal operations review.
- 4Pick a recurring schedule trigger and choose where run reports should go.
- 5Test with one real run and confirm it fits your readiness routine.
Questions about this workflow
Does this alert me to severe weather?
No. The listed action retrieves device readings; it is not a weather alert action.
Can I set a seasonal end date?
Use the recurring schedule available in Notis. The listed action does not manage seasonal dates.
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.