Keep CircleCI failures visible on the linked GitHub issue
When a failure alert names a GitHub issue, Notis can add a consistent label so the follow-up stays with the work already being tracked.
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 CI failure can arrive in a separate channel from the issue, leaving the issue without a clear signal for follow-up.
- Keep failure follow-up attached to its referenced issue
- Apply a consistent label without manually opening GitHub
- Skip alerts that do not identify one issue
Setup
Build it in a few focused steps.
- 1Connect CircleCI and GitHub once in Notis.
- 2Create an automation and name the issue triage outcome.
- 3In one instruction, tell Notis to read a CircleCI failure notification and add the agreed CI failure label only to the GitHub issue explicitly referenced.
- 4Pick a webhook trigger and choose where run reports should go.
- 5Test with one real failure notification that references an issue.
Questions about this workflow
Will the action create the label if it does not exist?
The listed GitHub action adds labels and creates labels that do not already exist.
What if a CircleCI alert does not include an issue number?
Have Notis skip the GitHub update and report that the issue reference was missing.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Circleci to GitHub. A trigger fires from one place; an action lands in another.
Circleci 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.
Circleci 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.