Turn failed GitHub runs into automatic follow-up
A failed build should create a clear next step, not another tab to remember.
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
Trigger Nango Action
Tool to trigger nango workflow actions via api. use when you need to execute an action by specifying the connection, provider config, and action identifier.
Why this helps
Build failures can disappear into notification noise while founders are focused on customers, hiring, or shipping.
- Create consistent follow-up for every failed run.
- Send useful run context to the Nango action that owns the next step.
- Reduce repeated checking across repositories and dashboards.
Setup
Build it in a few focused steps.
- 1Connect GitHub and Nango to Notis once through the portal.
- 2Create the automation in the portal or ask Notis in plain language.
- 3Tell Notis: When a GitHub workflow run fails, trigger my configured Nango incident action with the repository, run, branch, and failure details.
- 4Pick the GitHub workflow-run trigger, choose where Notis reports runs, and test it with one failed example.
Questions about this workflow
Can this cover more than one repository?
Yes. Configure the GitHub trigger for the repositories or workflow runs you want monitored, and let the same Nango action handle the follow-up.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Nango. A trigger fires from one place; an action lands in another.
GitHub triggers
Nango 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.
Trigger Nango Action
Tool to trigger nango workflow actions via api. use when you need to execute an action by specifying the connection, provider config, and action identifier.
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.
List Connections
Tool to list all connections. use when you need to retrieve existing connections.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
List Connections
Tool to list all connections without credentials. use when you need connection metadata across your account without exposing credentials.
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.
Get Provider Details
Tool to retrieve details for a specific provider. use when you need to fetch provider configuration details by name (e.g., 'salesforce'). use after selecting the provider.
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.
List Providers
Tool to retrieve a list of all available providers. use when you need to display or iterate through every provider before creating connections.
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.
Get Scripts Configuration
Tool to fetch the nango scripts configuration. use when you need to get the available scripts and their triggers.
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.
Trigger Sync
Tool to trigger a sync process manually. use after establishing a connection and defining a sync.
Commit Event
Triggered when a new commit is pushed to a repository.
Connect any two apps with Notis in the middle.
Not just GitHub and Nango. 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 Nango.