Route parsed incident reports to the right GitHub issue owners
When an incident report arrives, use its extracted details to assign the existing GitHub issue and make ownership visible.
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
Incident details can be captured quickly, but assigning the corresponding issue often gets lost between inboxes and GitHub.
- Turn extracted ownership details into issue assignments.
- Make responsibility clearer after an incident report arrives.
- Avoid retyping assignees into GitHub.
Setup
Build it in a few focused steps.
- 1Connect Airparser and GitHub once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a name.
- 3Describe in one instruction how to identify the existing issue and assign only the people named in the parsed report.
- 4Pick the Notis webhook trigger and choose where run reports should go.
- 5Send one real incident report through the webhook and review the result.
Questions about this workflow
Can the automation create an issue if none exists?
No. This GitHub action adds or removes assignees on an issue. The parsed report should identify an existing issue.
What if a named person cannot be assigned?
GitHub may ignore assignment changes when the authenticated account lacks push access. Review the run report and repository permissions.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Airparser to GitHub. A trigger fires from one place; an action lands in another.
Airparser 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.
Airparser 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.