Give incident follow-up a clear GitHub owner
Send a status page URL to Notis, let Airtop check the incident details, and assign the follow-up issue when your stated condition appears.
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
Status page updates can be missed or leave the follow-up issue without a clear owner.
- Check an incident page when a webhook arrives
- Assign a specified follow-up issue when the condition is met
- Make responsibility visible in the existing GitHub workflow
Setup
Build it in a few focused steps.
- 1Connect Airtop and GitHub once in the Notis portal.
- 2Create an automation in Automations, then New Automation.
- 3In one instruction, name the status page information to check, the incident condition, the GitHub repository and issue, and the assignee.
- 4Pick a webhook trigger and choose where run reports go.
- 5Test with one real status page update and confirm the user is assignable in the repository.
Questions about this workflow
Does this detect every status page incident?
It checks the page supplied to the webhook using the criteria in your instruction. Results depend on what the page exposes to Airtop.
What if the issue assignee is not eligible?
The GitHub action can fail if the user cannot be assigned in that repository. Check the run report and use an eligible username.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Airtop to GitHub. A trigger fires from one place; an action lands in another.
Airtop 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.
Airtop 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.