Stop a related GitHub workflow run during an incident
When an incident makes a deployment or workflow unsafe, send Notis the alert and the GitHub run to cancel.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Cancel a workflow run
Cancels a workflow run in a github repository if it is in a cancellable state (e.g., 'in progress' or 'queued').
Why this helps
A queued or active workflow can continue during an incident if someone has to switch tools and stop it manually.
- Shorten the path from incident alert to intervention
- Avoid switching tools to locate a workflow run
- Make the cancellation decision explicit in the automation prompt
Setup
Build it in a few focused steps.
- 1Connect Better Stack and GitHub once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a name and prompt.
- 3Tell Notis to cancel only the specified GitHub workflow run when the incoming alert indicates it should be stopped.
- 4Choose the webhook trigger and where run reports should go.
- 5Test with one real example and confirm the run is in a cancellable state.
Questions about this workflow
Does this cancel every run when any alert arrives?
No. State the incident conditions and the specific run identification details in the instruction so Notis can make the cancellation decision from the supplied context.
Can GitHub cancel any workflow run?
The run must be in a cancellable state, such as queued or in progress.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Better stack to GitHub. A trigger fires from one place; an action lands in another.
Better stack 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.
Better stack 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.