Cancel stale GitHub runs after campaign windows
Old automation keeps stealing attention. Let a scheduled Notis check stop runs that no longer serve the current publishing plan.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
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
Queued jobs continue running after a campaign is delayed, canceled, or replaced.
- Cuts wasted compute
- Prevents outdated work from finishing
- Keeps active projects quieter
Setup
Build it in a few focused steps.
- 1Connect BulkPublish and GitHub to Notis once through the portal.
- 2Create the automation in the portal or ask Notis to build it conversationally.
- 3In one instruction, tell Notis to review current BulkPublish campaign windows and cancel GitHub runs that are stale or tied to canceled work.
- 4Pick a recurring schedule and a channel for run reports.
- 5Test during one known campaign window.
Questions about this workflow
Can this cancel every GitHub run?
Your instruction should limit cancellation to runs clearly tied to stale BulkPublish work.
Why use a schedule here?
A recurring check catches stale runs even when no new campaign event arrives.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link BulkPublish to GitHub. A trigger fires from one place; an action lands in another.
BulkPublish triggers
GitHub actions
Accept a repository invitation
Accepts a pending repository invitation that has been issued to the authenticated user.
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.
Not just BulkPublish and GitHub. Any 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.