Refresh local conditions as outage tickets change
As an outage ticket changes, the conditions around the site may matter to the next decision. Have Notis retrieve the latest available station readings when the Jira issue is updated.
Trigger
Updated Issue
Fires when an existing issue is changed in the Jira project you configure — for example its status, assignee, or any other field on the issue is updated. Only issues in that project produce an event. It does not fire on comment activity: adding, editing, or deleting a comment on an issue will not produce an event from this trigger.
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
Incident context can go stale while a ticket is active, and checking a separate weather app adds another interruption during response.
- Prompt a fresh device reading lookup after an issue change.
- Keep weather context close to the incident workflow.
- Help responders revisit local conditions without manually checking another app.
Setup
Build it in a few focused steps.
- 1Connect Jira and Ambient Weather once in the Notis portal.
- 2Create an automation in the portal or tell Notis in plain language.
- 3In one instruction, ask Notis to retrieve the latest device data and summarize relevant conditions whenever an outage issue changes.
- 4Pick the Jira Updated Issue trigger for the project you use.
- 5Choose a report channel, then test with one real issue update and review the run report.
Questions about this workflow
What changes trigger this workflow?
An update to an existing issue in the configured project can trigger it, including a status, assignee, or other issue-field change. Comment activity does not trigger it.
Can it determine whether the weather caused the outage?
It can summarize available latest readings as context, but the readings alone do not establish causation.
Does it create a Jira comment or change the issue?
No. The only allowed action here retrieves Ambient Weather devices and their most recent data.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Jira to Ambient weather. A trigger fires from one place; an action lands in another.
Jira 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.
New Issue
Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.
New Project
Triggered when a new project is added in Jira
Updated Issue
Fires when an existing issue is changed in the Jira project you configure — for example its status, assignee, or any other field on the issue is updated. Only issues in that project produce an event. It does not fire on comment activity: adding, editing, or deleting a comment on an issue will not produce an event from this trigger.
Connect any two apps with Notis in the middle.
Jira 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.