Bring GitHub notifications into your support review
Create one calmer place to review engineering signals and customer work.
Trigger
Repository Notification Received
Triggers when a new or newly updated notification thread appears for a specific GitHub repository. Monitors notifications for issues, pull requests, commits, releases, check suites, security alerts, and other repository activity. Supports filtering by read/unread status and by direct participation. Requires a Personal Access Token (classic) with the ``notifications``
Action
Get Tickets
Retrieves a list of tickets from freshdesk.
Why this helps
Switching between repository notifications and support tickets makes it easy to miss the connection between them.
- Consolidates related support context
- Reduces notification overload
- Creates a repeatable review habit
Setup
Build it in a few focused steps.
- 1Connect GitHub and Freshdesk to Notis once.
- 2Create the automation in the portal or ask Notis to create it conversationally.
- 3Tell Notis to retrieve relevant Freshdesk tickets when a new GitHub repository notification arrives, then summarize the tickets that need attention.
- 4Select the repository notification trigger, choose a reporting channel, and test with one real notification.
Questions about this workflow
Can this focus on unread notifications?
Yes. State that Notis should act only on unread notifications.
Does it create tickets automatically?
This workflow retrieves existing tickets. Create a separate ticket workflow if new records are needed.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Freshdesk. A trigger fires from one place; an action lands in another.
GitHub triggers
Freshdesk actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Ticket
Creates a new ticket in freshdesk.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Delete Ticket
Deletes an existing ticket in freshdesk.
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.
Get Tickets
Retrieves a list of tickets from freshdesk.
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 All Tickets
Lists all tickets in freshdesk.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
Reply to Ticket
Replies to an existing ticket in freshdesk.
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.
Update Ticket
Updates an existing ticket in freshdesk.
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.
View Ticket
Views an existing ticket in freshdesk.
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.
Connect any two apps with Notis in the middle.
GitHub and Freshdesk, or any other 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 Freshdesk.