Make failed checks visible in the plan
When automation breaks, the recovery work gets a place to land immediately.
Trigger
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.
Action
Create Milestone
Tool to create a new milestone for a project in Hub Planner. Use when you need to set up a milestone with a specified name, date, and project association.
Why this helps
Failed checks create vague anxiety but no scheduled recovery step.
- Turns technical failures into explicit work
- Makes recovery ownership easier to see
- Reduces repeated checking and worry
Setup
Build it in a few focused steps.
- 1Connect GitHub and Hub Planner to Notis once through the portal.
- 2Create an automation or ask Notis to create a recovery milestone for critical check runs whose conclusion is failure or timed_out.
- 3Pick the Check Run Status / Conclusion Changed trigger and choose a channel for run reports.
- 4Test with one deliberately monitored failing check or a real failure.
Questions about this workflow
Can it focus on critical checks only?
Yes. Specify the check names, repositories, or branches that deserve a planning milestone.
What should happen when the check recovers?
Create a separate follow-up automation if you want successful recovery to close or reschedule related work.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Hub Planner. A trigger fires from one place; an action lands in another.
GitHub triggers
Hub Planner actions
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.
Add Clients to Project
Tool to add clients to a project by project ID. Use when you need to associate one or more clients with a specific project.
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.
Add project custom field choices
Add choices to a project custom field template of SELECT, RADIO, or CHECKBOX type. Use when you need to add new options to an existing dropdown, radio button, or checkbox custom field in Hub Planner projects.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
Add Projects to Group
Tool to add projects to a project group in Hub Planner. Use when you need to associate one or more projects with a specific project group.
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.
Add Project Tags
Tool to add tags to a Hub Planner project. Preserves existing tags and appends new ones. Use when you need to add one or more tags to a project without removing existing tags.
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.
Add Resource Custom Field Choices
Tool to add choices to a resource custom field template of SELECT, RADIO, or CHECKBOX type. Use when you need to add new selection options to an existing custom field template.
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.
Add Resources to Project
Tool to add resources to a project by project ID. Use when you need to associate one or more resources with a specific project.
New Repository Collaborator Added
Triggers when a new collaborator is added to a GitHub repository. Monitors the full list of collaborators on a repository and fires an event for each newly added collaborator. The payload includes the collaborator's GitHub username, account ID, profile URL, avatar URL, permission flags (pull, triage, push, maintain, admin), and assigned role name.
Add Resources to Resource Group
Tool to add resources to a resource group by group ID. Use when you need to associate one or more resources with a specific resource group.
Commit Event
Triggered when a new commit is pushed to a repository.
Add Resource Tags
Tool to add tags to a resource in Hub Planner. Preserves existing tags and appends new ones. Use when you need to categorize, label, or organize resources using tags.
Connect any two apps with Notis in the middle.
Not just GitHub and Hub Planner. Any combination from 1,000+ 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 Hub Planner.