Turn GitHub issues into Freshdesk tickets
Keep customer-impacting issues visible without copying them by hand.
Trigger
Issue Added Event
Triggered when a new issue is added to the repository.
Action
Create Ticket
Creates a new ticket in freshdesk.
Why this helps
Important customer problems can sit in GitHub while support has no shared follow-up record.
- Creates one support record from each relevant GitHub issue
- Reduces duplicate copying between engineering and support
- Gives founders a clear place to track customer-facing follow-up
Setup
Build it in a few focused steps.
- 1Connect GitHub and Freshdesk to Notis once through the portal.
- 2Create an automation in Automations or ask Notis to create it conversationally.
- 3Use one plain-language instruction: create a Freshdesk ticket from every new GitHub issue that describes a customer-impacting problem, including the issue context and link.
- 4Choose the GitHub new issue trigger and a channel for run reports, then test with one real issue.
Questions about this workflow
Can Notis include the original GitHub context?
Yes. Tell Notis to include the issue title, description, author, labels, and direct link in the Freshdesk ticket.
Will every GitHub issue create a ticket?
You can state which kinds of issues should create tickets in the plain-language 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
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 Ticket
Creates a new ticket in 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.
Delete Ticket
Deletes an existing ticket 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.
Get Tickets
Retrieves a list of tickets from 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.
List All Tickets
Lists all tickets 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.
Reply to Ticket
Replies to 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.
Update Ticket
Updates an existing ticket in freshdesk.
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.
View Ticket
Views an existing ticket in freshdesk.
Commit Event
Triggered when a new commit is pushed to a repository.
Connect any two apps with Notis in the middle.
Not just GitHub and Freshdesk. 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 Freshdesk.