Turn new GitHub issues into Zoho Desk tickets automatically
Issues pile up in GitHub while your customer conversations live in Zoho Desk, and keeping them in sync by hand is exhausting. Notis watches for each new issue and opens a matching Zoho Desk ticket, so nothing reported ever falls through the crack between the two tools.
Trigger
New Issue Created
Triggers when a new issue is created in a GitHub repository. Pull requests are automatically excluded -- only true issues produce events. Results can be filtered by labels, assignee, creator, and mentioned user. The payload includes the issue number, title, body, state, labels, assignees, comment count, creator details, timestamps, and direct links to the issue on GitHub.
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
Bug reports land in GitHub, support requests land in Zoho Desk, and you are the only bridge between them until something gets dropped.
- Every reported issue automatically has a support ticket, no manual copying
- Your team triages bugs and customer requests in one familiar place
- You stop being the human relay between GitHub and Zoho Desk
- The issue's full description carries over so nobody re-reads the repo
Setup
Build it in a few focused steps.
- 1Connect GitHub and Zoho Desk to Notis one time from the portal.
- 2Add a new automation and describe it in plain words: when a new issue is created in GitHub, create a matching Zoho Desk ticket.
- 3Choose the GitHub new issue trigger and set the channel where Notis reports each run.
- 4Open one test issue and check that the ticket shows up in Zoho Desk.
Questions about this workflow
Does this include pull requests?
No. The new issue trigger only fires for true issues, so your pull requests will not create tickets.
Can I limit it to issues with a certain label?
Yes. Just say so in your plain-language instruction and Notis will only create tickets for issues that match.
What if I want the ticket in a specific department?
Name the department in your instruction and Notis will place the ticket there when it creates it.
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 985+ 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.