Open a Zoho Desk ticket when a GitHub check run concludes as failed
A single failing check is easy to override and forget, right up until it blocks a release later. Notis watches a check run's status and conclusion and opens a Zoho Desk ticket when it fails, so recurring red checks become tracked work instead of background noise.
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 Ticket
Tool to create a new Zoho Desk ticket with subject, description, department, and requester details. Use when you need to create a support ticket in Zoho Desk. Returns the created ticket with id and webUrl for downstream chaining.
Why this helps
One check keeps failing, you keep re-running it, and the underlying problem never gets a real task attached to it.
- Persistent check failures get an owner and a ticket
- You stop masking a real issue by re-running checks
- The failure sits in the queue you review, not lost in logs
- Each ticket carries the check context so debugging is faster
Setup
Build it in a few focused steps.
- 1Connect GitHub and Zoho Desk to Notis once in the portal.
- 2Create a new automation and write it plainly: when the monitored GitHub check run concludes as a failure, open a Zoho Desk ticket about it.
- 3Pick the GitHub check run status change trigger and choose the channel for run reports.
- 4Force one failing check and confirm the ticket appears in Zoho Desk.
Questions about this workflow
Can I ignore flaky checks that pass on retry?
Yes. Tell Notis to only file a ticket when the final conclusion is a failure, and transient states are ignored.
Which check runs does it watch?
It monitors the check run you point it at, so you can focus on the ones that matter most.
Do I configure this in code?
No. It is a single plain-language instruction to Notis, with no scripts to maintain.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Zoho desk. A trigger fires from one place; an action lands in another.
GitHub triggers
Zoho desk 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.
Create Contact
Tool to create a new contact in Zoho Desk with name, email, and other details. Use this action when you need to add a new contact to the system, such as when onboarding a new customer or registering a support requester. Returns the created contact with id and webUrl for downstream operations.
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 Ticket
Tool to create a new Zoho Desk ticket with subject, description, department, and requester details. Use when you need to create a support ticket in Zoho Desk. Returns the created ticket with id and webUrl for downstream chaining.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
Download Ticket Attachment
Download a file attachment from a Zoho Desk ticket by attachment ID. Use this action when you need to retrieve a specific file that was previously attached to a ticket. Requires both the ticket ID and the attachment ID to identify the file to download.
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 Agent
Tool to fetch details of a Zoho Desk agent. Use when you have an agent ID and need its full data, optionally including related resources.
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.
Get Agents Count
Tool to get the total count of agents in Zoho Desk. Use when you need the number of agents optionally filtered by status, confirmation, or light agents.
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 Contact
Tool to fetch details of a Zoho Desk contact. Use when you have a contact ID and need its full data, optionally including accounts or owner details.
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 Contacts By IDs
Tool to fetch multiple contacts by their IDs using Zoho Desk's contactsByIds endpoint.
Commit Event
Triggered when a new commit is pushed to a repository.
Get Department
Tool to fetch details of a Zoho Desk department by ID.
Connect any two apps with Notis in the middle.
Not just GitHub and Zoho desk. 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 Zoho desk.