Route customer issues to GitHub automatically
Turn incoming customer context into clear ownership before another task steals your attention.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Add assignees to an issue
Adds or removes assignees for a github issue; changes are silently ignored if the authenticated user lacks push access to the repository.
Why this helps
Customer problems sit unowned when triage depends on remembering to check several tools.
- Reduce manual triage
- Make ownership visible quickly
- Prevent support items from disappearing
Setup
Build it in a few focused steps.
- 1Connect Nango and GitHub to Notis once through the portal.
- 2Create an automation in the portal or ask Notis to create one in plain language.
- 3Tell Notis to assign the matching GitHub issue to the appropriate owner when customer issue data arrives.
- 4Choose an incoming webhook trigger and a channel for run reports, then test with one real issue.
Questions about this workflow
Does Notis require field mapping?
No. You describe the routing outcome in one plain-language instruction and Notis interprets the available context.
Can this work with an existing GitHub issue?
Yes, when the incoming request identifies the issue clearly enough for Notis to locate it.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Nango to GitHub. A trigger fires from one place; an action lands in another.
Nango triggers
GitHub actions
Accept a repository invitation
Accepts a pending repository invitation that has been issued to the authenticated user.
List repositories starred by the authenticated user
Deprecated: lists repositories starred by the authenticated user, including star creation timestamps; use 'list repositories starred by the authenticated user' instead.
List stargazers
Deprecated: lists users who have starred a repository; use `list stargazers` instead.
Star a repository for the authenticated user
Deprecated: stars a repository for the authenticated user; use `star a repository for the authenticated user` instead.
Add email for auth user
Adds one or more email addresses (which will be initially unverified) to the authenticated user's github account; use this to associate new emails, noting an email verified for another account will error, while an existing email for the current user is accepted.
Add app access restrictions
Replaces github app access restrictions for an existing protected branch; requires a json array of app slugs in the request body, where apps must be installed and have 'contents' write permissions.
Add a repository collaborator
Adds a github user as a repository collaborator, or updates their permission if already a collaborator; `permission` applies to organization-owned repositories (personal ones default to 'push' and ignore this field), and an invitation may be created or permissions updated directly.
Add a repository to an app installation
Adds a repository to a github app installation, granting the app access; requires authenticated user to have admin rights for the repository and access to the installation.
Connect any two apps with Notis in the middle.
Not just Nango and GitHub. Any 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 GitHub.