Keep customer tickets current from GitHub comments
Turn meaningful engineering updates into support-ready context.
Trigger
New GitHub Issue Comment
Triggers when a new comment is added to a specific GitHub issue. Only genuinely new comments are emitted; edits to existing comments do not produce duplicate events. The payload includes the comment ID, text body, author details, timestamps, and direct links to the comment on GitHub.
Action
Reply to Ticket
Replies to an existing ticket in freshdesk.
Why this helps
Progress updates often appear in issue comments but never reach the customer conversation.
- Keeps ticket history complete
- Reduces manual copy and paste
- Helps support respond with current information
Setup
Build it in a few focused steps.
- 1Connect GitHub and Freshdesk once in Notis.
- 2Create the automation in the portal or ask Notis to create it in plain language.
- 3Instruct Notis to reply to the matching Freshdesk ticket when a new GitHub issue comment contains a meaningful customer update, including the author and comment link.
- 4Select the new GitHub issue comment trigger, choose a reporting channel, and test with one comment.
Questions about this workflow
Can internal-only comments be excluded?
Yes. Define which authors, phrases, labels, or comment types should be included.
Can the reply be internal instead of customer-facing?
State the intended Freshdesk reply style in the instruction.
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.