Route weather-disrupted work to an owner
Turn an incoming weather update into a clear owner for the GitHub issues tied to the affected location or work.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Add assignees to an issue
Adds or removes assignees for a github issue; changes are silently ignored if the authenticated user lacks push access to the repository.
Why this helps
Weather updates arrive in one place while the issues they affect remain unowned in GitHub.
- Connect a weather update to an accountable issue owner
- Cut down on manual backlog searches
- Keep assignment decisions tied to the instructions you provide
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 use the incoming weather update to find relevant open issues and assign them to the specified responsible person.
- 4Pick a webhook trigger and choose where run reports should go.
- 5Test with one real weather update and review the issue assignments.
Questions about this workflow
Does the webhook come directly from Ambient weather?
Ambient weather has no listed trigger events. The webhook is a Notis-native trigger that starts the automation when an HTTP request arrives.
How does Notis know who owns an area?
Include the relevant owner and location context in your instruction or provide it in data Notis can access. The available action adds assignees to issues.
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.