Cancel GitHub Workflows via External Webhook Trigger
Your monitoring system detects high error rates in production. A webhook fires to Notis, which immediately cancels the broken workflow run. Your deployment stops before it breaks more.
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
Broken workflows running unattended waste time and mental resources. Neurodivergent founders need automated circuit-breakers that stop problems without requiring manual intervention.
- Broken workflows stop automatically without manual action
- External systems can trigger GitHub actions through Notis
- Reduces the need to monitor GitHub while things run
- Prevents cascading failures from bad deployments
Setup
Build it in a few focused steps.
- 1Connect GitHub to Notis (Telegram is optional for this one).
- 2Create an automation with the prompt: 'When you receive a webhook request, cancel the most recent workflow run in my GitHub repository.'
- 3Select Notis Webhook as the trigger and copy your unique webhook URL.
- 4Configure your external monitoring system to POST to that URL when it detects an error condition.
Questions about this workflow
Can I cancel specific workflows, not just the most recent?
Yes—include the workflow name in your webhook payload and Notis will cancel that specific workflow.
What if no workflow is running?
Notis will report back in Telegram or via the webhook response that nothing was running to cancel.
How do I set up the webhook in my monitoring tool?
Copy the Notis webhook URL and paste it as a new alert action in your monitoring tool. It works like any other webhook endpoint.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Telegram to GitHub. A trigger fires from one place; an action lands in another.
Telegram triggers
GitHub actions
New Message Received
Triggered when your bot receives a new message in a private chat, group, or supergroup. To receive every message in a group, Privacy Mode must be disabled for the bot in BotFather.
Accept a repository invitation
Accepts a pending repository invitation that has been issued to the authenticated user.
New Channel Post
Triggered when a new post is published to a channel where your bot is an administrator.
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.
Callback Query Received
Triggered when a user taps an inline keyboard button attached to one of your bot's messages.
List stargazers
Deprecated: lists users who have starred a repository; use `list stargazers` instead.
Message Edited
Triggered when a message in a chat your bot can see is edited by its sender.
Star a repository for the authenticated user
Deprecated: stars a repository for the authenticated user; use `star a repository for the authenticated user` instead.
New Chat Member
Triggered when a new member joins a group or supergroup the bot belongs to, including when the bot itself is added.
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 Telegram and GitHub. Any combination from 985+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7 days free trial with 20$ free usage included.
No card. Works with personal or business GitHub.