Put the failure follow-up with the owner named in the alert
When a CircleCI failure notification names both a GitHub issue and its owner, Notis can update the issue assignment in one step.
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
The person responsible for a failing build may be clear in the alert, but the GitHub issue still waits for someone to update it.
- Reduce manual issue handoff
- Use only an owner named in the notification
- Keep assignment on the relevant GitHub issue
Setup
Build it in a few focused steps.
- 1Connect CircleCI and GitHub once in Notis.
- 2Create an automation and name the assignment outcome.
- 3Tell Notis in one instruction to assign the referenced GitHub issue only when the CircleCI notification identifies one issue and explicitly names an assignable GitHub user.
- 4Pick a webhook trigger and choose where run reports should go.
- 5Test with one real notification containing an issue and a named owner.
Questions about this workflow
Can this assign an issue to someone inferred from the repository?
The instruction should require an explicitly named owner in the notification. If the owner is missing or unclear, Notis should skip the assignment.
What happens if GitHub cannot assign that person?
The GitHub action may silently ignore changes when the authenticated user lacks push access. Choose a report channel so you can review the run result.
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.