Make failed workflow runs hard to miss
When automation fails, give someone a clear place to investigate and resolve the issue.
Trigger
GitHub Workflow Run State Changed
Triggers when a GitHub Actions workflow run's status or conclusion changes. Monitors a single workflow run and fires an event whenever it transitions between states (e.g., queued to in_progress, or in_progress to completed) or when its conclusion is set (e.g., success, failure, cancelled).
Action
Create Card
Tool to create a new card in a project. use after confirming the project id. creates a task with details like name, due date, and assignees.
Why this helps
Failed builds can be lost in notifications, delaying fixes and blocking other work.
- Bring failed runs into the team's active work view.
- Include the run link and available status details for investigation.
- Make build failures easier to follow through to resolution.
Setup
Build it in a few focused steps.
- 1Connect GitHub and Breeze once in the Notis portal.
- 2Create an automation in Automations, New Automation, or tell Notis what you want from any channel.
- 3Ask Notis to create a Breeze investigation card when a GitHub Actions run completes with a failure, including the available run details and link.
- 4Pick the GitHub Workflow Run State Changed trigger and choose where run reports should go.
- 5Test with one real failed run and confirm the card points to the right run.
Questions about this workflow
Will this create a task for every run state change?
The event tracks changes in run status and conclusion. In your instruction, have Notis create a card only when the run is completed with a failure conclusion.
Can the card explain why the run failed?
Notis can include failure details that the event provides. If the payload does not include a cause, the task can link to the run for investigation but cannot invent one.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Breeze. A trigger fires from one place; an action lands in another.
GitHub triggers
Breeze actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Add Project People
Tool to add people to a project. use when you have a valid project id and one or more email addresses to invite them.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Archive Project
Tool to archive a specific project. use when you need to hide a completed or inactive project from active views after confirming its details.
New Workflow Artifact Created
Triggers when a new workflow artifact is created in a GitHub repository. Monitors for newly created GitHub Actions workflow artifacts. Optionally filters by artifact name to restrict monitoring to specific artifacts.
Create Card
Tool to create a new card in a project. use after confirming the project id. creates a task with details like name, due date, and assignees.
Branch Changed
Triggers when a GitHub branch changes. Monitors a specific branch for: - New commits pushed (head commit SHA changes) - Protection status toggled (branch becomes protected or unprotected) - Protection settings changed, including: required status checks and their enforcement level, admin enforcement, required pull request reviews (dismiss stale reviews, code owner reviews, approving review count, last push approval), required linear history, force push allowance, deletion allowance, conversation resolution, branch locking, and fork syncing.
CREATE_LIST
Tool to create a new list (stage) in a breeze project. use when you've selected a project and need to add a new stage. example: "create a new todo list for project 42."
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
Create Project
Tool to create a new project in breeze. use when you have the project name and want to initialize it via the api.
Check Run Status / Conclusion Changed
Triggers when a specific GitHub check run changes its status or conclusion. Monitors a single check run for changes to: status (queued, in_progress, completed, etc.), conclusion (success, failure, neutral, cancelled, skipped, timed_out, action_required), started_at, and completed_at.
Create Workspace
Tool to create a new workspace. use after deciding on the workspace name.
Check Suite Status / Conclusion Changed
Triggers when a GitHub check suite changes its status or conclusion for a given ref. Monitors all check suites associated with a git reference (branch, tag, or commit SHA) for changes to status (queued, in_progress, completed, etc.) and conclusion (success, failure, neutral, cancelled, skipped, timed_out, action_required, startup_failure, stale). Optionally filters by GitHub App ID.
Delete Card
Tool to delete a specific card (task) by its id. use when you need to remove a task permanently; deletions cannot be undone.
New Code Scanning Alert Created
Triggers when a new code scanning alert is created in a repository. Fires an event for each newly created code scanning alert detected in the configured repository. Alerts can be filtered by Git reference, scanning tool, state, and severity. The payload includes the alert number, rule details, tool information, state, severity, and the location of the most recent instance.
Delete Project
Tool to delete a specific project by id. use when you need to remove a project after confirming its id.
Connect any two apps with Notis in the middle.
GitHub and Breeze, 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 Breeze.