Give the incident team access to the follow-up project
Let confirmed incident scope determine who can coordinate the work that follows.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Add or update team project permissions
Grants or updates a team's permissions ('read', 'write', or 'admin') for a specific project, which must exist within the specified organization and be linked to it.
Why this helps
A new follow-up project is less useful if the response team must wait for separate project access.
- Keeps follow-up moving
- Reduces one-off access requests
Setup
Build it in a few focused steps.
- 1Connect incident.io and GitHub to Notis once.
- 2Create a webhook-triggered portal automation for approved project-access requests.
- 3Write a prompt asking Notis to grant the incident response team the specified permission on the named GitHub project.
- 4Choose a run-report channel and test with a low-risk project.
Questions about this workflow
What permissions can be requested?
Use the plain-language prompt to request the appropriate read, write, or admin access.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link incident.io to GitHub. A trigger fires from one place; an action lands in another.
incident.io 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.
incident.io 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.