Label GitHub issues from carbon alerts
Keep energy-sensitive work visible without having to remember a separate follow-up.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
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
A founder sees a carbon alert, means to flag the related work, then loses the thread in a busy issue list.
- Makes urgent energy work scannable
- Cuts down on manual triage
Setup
Build it in a few focused steps.
- 1Connect Corrently and GitHub to Notis once in the portal.
- 2Create a new automation in Automations or ask Notis for it in plain language.
- 3Write that a Corrently carbon alert should label the related GitHub issue as energy-urgent.
- 4Choose Incoming webhook as the trigger, select a run-report channel, and test with one alert.
Questions about this workflow
Do I need to map alert fields?
No. Describe which issue to label and how in the automation prompt; Notis handles the interpretation.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Corrently to GitHub. A trigger fires from one place; an action lands in another.
Corrently triggers
GitHub actions
Accept a repository invitation
Accepts a pending repository invitation that has been issued to the authenticated user.
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.
Not just Corrently and GitHub. Any combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7 days free trial with 20$ free usage included.
No card. Works with personal or business GitHub.