Make device readings part of a monthly review
A monthly reminder to retrieve your latest station readings can help keep your monitoring routine connected to the work you plan.
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
Monitoring routines can fade into the background when they depend on remembering to review device data.
- Create a recurring moment to review current readings.
- Keep your monitoring habit attached to an existing monthly review.
- Get a compact summary without manually visiting each device screen.
Setup
Build it in a few focused steps.
- 1Connect Ambient Weather to Notis once through the portal; connect Notion if you want to review a tracking page.
- 2Create an automation in the portal or ask Notis conversationally for a monthly device-reading review prompt.
- 3Write one plain-language instruction asking Notis to retrieve current readings and summarize them as a cue to review your monitoring routine.
- 4Choose a monthly recurring schedule and a channel for run reports.
- 5Test a run and confirm the requested summary is concise.
Questions about this workflow
Does it analyze historical trends?
The only Ambient action listed here retrieves devices with their most recent data. This workflow summarizes current readings and does not claim historical analysis.
Can I choose a review date?
Set the monthly schedule to the date and time that fits your routine.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Ambient weather. A trigger fires from one place; an action lands in another.
Notion 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.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Comment Created
Triggers when a new comment is created in Notion. Optional `page_id` filter scopes to comments on a specific page. When omitted, fires for any new comment in the workspace the integration has access to. Requires the 'Read comments' capability on the Notion integration. If a connection was authorized before that capability was enabled, the user must re-authorize the connection for comment events to flow.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Database Created
Triggers when a new Notion database (the container) is created. A database is the post-2025-09-03 container that holds one or more data sources. This trigger fires for the container's creation event (`database.created`), distinct from `NOTION_DATASOURCE_CREATED` which fires when a new data source is added to an existing database. Most customers calling Notion's `POST /v1/databases` (the legacy API) or creating a database via the Notion UI will see this event. Adding a new data source to an existing database fires `data_source.created` instead — use `NOTION_DATASOURCE_CREATED` for that. Notion's payload puts `entity.type: "block"` (the container is a `child_database` block in the content tree) and `entity.id` is the database id.
Data Source Created
Triggers when a new Notion data source is created. Fires workspace-wide. The payload's `data.parent` carries the data source's tree parent (typically the teamspace) for downstream filtering. A single template-based database creation can fire multiple `data_source.created` events at once — one per data source the template instantiates.
Data Source Schema Updated
Triggers when a Notion data source's schema is updated. Fires on column add / remove / rename. Payload includes `data.updated_properties: [{id, name, action}]` so consumers can discriminate the kind of change downstream. Optional `data_source_id` filter scopes to schema changes on a single data source. When omitted, fires for any schema change in the workspace the integration has access to. Note: adding a column also fires `page.properties_updated` once per existing row in the data source. Customers wanting a single structural-change signal should use this trigger.
Connect any two apps with Notis in the middle.
Notion 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.