Keep weather-related GitHub issues visible
A scheduled weather check can help your team spot open issues that matter when local conditions turn severe.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Add labels to an issue
Adds labels (provided in the request body) to a repository issue; labels that do not already exist are created.
Why this helps
Weather risks can make relevant operational issues easy to miss in a busy GitHub backlog.
- Bring weather-sensitive issues into view
- Reduce manual checks across weather and GitHub
- Apply labels only when the prompt's conditions are met
Setup
Build it in a few focused steps.
- 1Connect Ambient weather and GitHub once in the Notis portal.
- 2Create an automation in Automations, New Automation, and name it.
- 3Tell Notis to check the forecast for your specified locations and add a severe-weather label to relevant open issues when your stated thresholds are met.
- 4Pick a recurring schedule and choose where run reports should go.
- 5Test with one real forecast and review the matching issues.
Questions about this workflow
Does Ambient weather start this automatically?
Ambient weather has no listed trigger events, so this automation starts on a Notis schedule and asks Notis to retrieve weather data.
How does Notis decide which issues are relevant?
Describe the locations, issue context, and weather thresholds in your instruction. Notis can only match against information it can access or that you provide.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Ambient weather to GitHub. A trigger fires from one place; an action lands in another.
Ambient weather triggers
GitHub actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Accept a repository invitation
Accepts a pending repository invitation that has been issued to the authenticated user.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
List repositories starred by the authenticated user
Deprecated: lists repositories starred by the authenticated user, including star creation timestamps; use 'list repositories starred by the authenticated user' instead.
List stargazers
Deprecated: lists users who have starred a repository; use `list stargazers` instead.
Star a repository for the authenticated user
Deprecated: stars a repository for the authenticated user; use `star a repository for the authenticated user` instead.
Add email for auth user
Adds one or more email addresses (which will be initially unverified) to the authenticated user's github account; use this to associate new emails, noting an email verified for another account will error, while an existing email for the current user is accepted.
Add app access restrictions
Replaces github app access restrictions for an existing protected branch; requires a json array of app slugs in the request body, where apps must be installed and have 'contents' write permissions.
Add a repository collaborator
Adds a github user as a repository collaborator, or updates their permission if already a collaborator; `permission` applies to organization-owned repositories (personal ones default to 'push' and ignore this field), and an invitation may be created or permissions updated directly.
Add a repository to an app installation
Adds a repository to a github app installation, granting the app access; requires authenticated user to have admin rights for the repository and access to the installation.
Connect any two apps with Notis in the middle.
Ambient weather and GitHub, 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 GitHub.