Add a current device check to an incident review
When an incident review needs current conditions, an HTTP request can start a Notis retrieval of the latest readings from your Ambient Weather devices.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
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
During an incident, the person coordinating a review may not have time to search for current readings in another app.
- Request latest readings at the point of review
- Keep the retrieval available to an existing HTTP process
- Reduce context switching during incident follow-up
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 device readings when an incident review requests current conditions.
- 4Pick the webhook trigger and choose where run reports should go.
- 5Test with one real HTTP request from your incident review process.
Questions about this workflow
Does this contact anyone during an incident?
No. The available action retrieves device data. Choose a report channel in Notis to see the workflow run.
Does this provide an alert about dangerous conditions?
No alert action is listed. It returns the latest data available from your devices.
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.