Turn failed GitHub Actions runs into Freshservice tickets
Stop build failures from becoming invisible interruptions.
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 Ticket
Tool to create a new ticket. Use when you need to log an incident or service request.
Why this helps
A failed workflow can derail the day, especially when nobody remembers to document it after fixing the immediate issue.
- Preserves failure context automatically
- Makes recurring reliability work easier to spot
- Reduces interruption-driven note taking
Setup
Build it in a few focused steps.
- 1Connect GitHub and Freshservice to Notis once through the portal.
- 2Create an automation in the portal or ask Notis to set it up by chat.
- 3Tell Notis in plain language to create a Freshservice incident for each failed GitHub Actions workflow run, including the workflow, branch, commit, and run URL.
- 4Pick the workflow run state trigger, select a run-report channel, and test with one failed example.
Questions about this workflow
Can this focus on one branch?
Yes. Configure the GitHub trigger for the relevant branch when creating the automation.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Freshservice. A trigger fires from one place; an action lands in another.
GitHub triggers
Freshservice 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.
Bulk Update Tickets
Tool to bulk update multiple Freshservice tickets by sequential update calls. Use when you need to update fields across many tickets in absence of a native bulk API.
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 Service Request
Create a service request for a catalog item in Freshservice using the v2 API. The catalog item display_id can be found in Admin > Service Catalog by clicking on an item and checking the URL (e.g., /service_catalog/items/1 means display_id=1).
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 Ticket
Tool to create a new ticket. Use when you need to log an incident or service request.
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.
Delete Release
Tool to delete a release from Freshservice. Use when you need to permanently remove a release from the system. This action is irreversible — the release cannot be recovered once deleted.
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 Solution Article
Tool to delete a solution article from the knowledge base by its ID. This action is irreversible — the article cannot be recovered once deleted. Use this action when you need to permanently remove a solution article from Freshservice.
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 Solution Category
Tool to delete a solution category in Freshservice. Use this action when you need to remove a solution category that is no longer needed. This action is irreversible — the category cannot be recovered once deleted.
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.
Get Problem Form Fields by Workspace
Tool to list problem form fields. Use when you need to retrieve the form fields available for problems in a specific workspace.
Commit Event
Triggered when a new commit is pushed to a repository.
List Release Form Fields
Tool to list release form fields metadata. Use when you need to fetch release field definitions before building or validating release forms.
Connect any two apps with Notis in the middle.
Not just GitHub and Freshservice. 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 Freshservice.