Stop a workflow run when a browser regression is confirmed
When a Browserbase report confirms a regression, have Notis assess the evidence and cancel the specific GitHub run if it is still cancellable.
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 confirmed browser regression can leave a related workflow consuming time while someone has to find and stop it manually.
- Bring browser regression evidence into the decision to stop a run.
- Cancel the identified run when it is queued or in progress.
- Keep a record of the run and the report that informed the action.
Setup
Build it in a few focused steps.
- 1Connect Browserbase and GitHub once in Notis.
- 2Create an automation in plain language or in Automations, New Automation.
- 3In one instruction, ask Notis to assess each regression report and cancel only the identified GitHub workflow run when cancellation is appropriate.
- 4Choose the Notis webhook as the trigger and have the Browserbase report start it with an HTTP request.
- 5Choose a run report destination, then test with one real regression report and cancellable run.
Questions about this workflow
Will this cancel completed workflow runs?
No. GitHub allows cancellation only for runs in a cancellable state, such as queued or in progress.
What does the report need to identify?
It needs to provide the GitHub repository and workflow run details so Notis can act on the intended run.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Browserbase tool to GitHub. A trigger fires from one place; an action lands in another.
Browserbase tool 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.
Browserbase tool 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.