Skip to content
Notis

Stop a cancellable GitHub run when the rig overheats

If a hardware test rig reports an overheat, stop the related workflow run before it keeps consuming time or equipment access.

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 long-running hardware workflow can continue after the physical test environment becomes unsafe or unreliable.

  • React to an overheat alert without switching to GitHub.
  • Stop a run that is still queued or in progress.
  • Keep the cancellation tied to a run reference provided by the alert.

Setup

Build it in a few focused steps.

  • 1Connect Bolt IoT and GitHub once in Notis.
  • 2Create an automation from any channel or in Automations, New Automation.
  • 3Tell Notis to cancel the referenced GitHub workflow run when the alert reports a rig overheat.
  • 4Choose the webhook trigger and where run reports should go.
  • 5Test with a real alert and a queued or in-progress run reference.

Questions about this workflow

Can this cancel a completed workflow run?

No. GitHub only permits cancellation while a run is in a cancellable state, such as queued or in progress.

Does the webhook need to identify the run?

Yes. The alert or your instruction needs to provide enough information to identify the repository and workflow run.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

Notis builds workflows that link Bolt iot to GitHub. A trigger fires from one place; an action lands in another.

Bolt iot triggers

GitHub actions

Recurring trigger

Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.

TriggerScheduled

Accept a repository invitation

Accepts a pending repository invitation that has been issued to the authenticated user.

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

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.

ActionInstant

List stargazers

Deprecated: lists users who have starred a repository; use `list stargazers` instead.

ActionInstant

Star a repository for the authenticated user

Deprecated: stars a repository for the authenticated user; use `star a repository for the authenticated user` instead.

ActionInstant

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.

ActionInstant

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.

ActionInstant

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.

ActionInstant

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.

ActionInstant

Connect any two apps with Notis in the middle.

Bolt iot 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.