Bring current readings to site-planning conversations
A brief before the meeting can help you spend less time gathering context and more time deciding what the plan needs.
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
Meetings can lose time while everyone catches up on information you could have checked beforehand.
- Retrieve readings ahead of a recurring planning conversation.
- Start the meeting with concise conditions context.
- Reduce last-minute prep and context switching.
Setup
Build it in a few focused steps.
- 1Connect Ambient Weather to Notis once through the portal; connect Notion if you want to refer to a planning page.
- 2Create an automation in the portal or ask Notis conversationally for a pre-meeting site-planning brief.
- 3Use one plain-language instruction asking Notis to retrieve latest Ambient readings and summarize them before the meeting.
- 4Choose a recurring schedule shortly before the meeting and select a channel for run reports.
- 5Test a run before the next real planning meeting.
Questions about this workflow
Can it pull a meeting calendar automatically?
This workflow uses a recurring schedule and the listed Ambient retrieval action; it does not specify a calendar trigger.
Are the readings a forecast for the site?
No. The action retrieves current device data, which may be useful context for the discussion.
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.