Route paid customer support work automatically
Payment context can help the right person pick up customer work faster.
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
Support requests lose momentum when payment status and issue ownership must be checked separately.
- Prioritize work for active customers.
- Reduce triage decisions.
- Make ownership obvious to the team.
Setup
Build it in a few focused steps.
- 1Connect Moonclerk and GitHub to Notis once through the portal.
- 2Create an automation in the portal or ask Notis to build it.
- 3Describe in one plain-language instruction how to assign the matching GitHub support issue when the relevant Moonclerk event arrives.
- 4Pick an incoming webhook trigger and a channel for run reports.
- 5Test with one real customer case.
Questions about this workflow
Can the owner differ by customer segment?
Yes. Explain the routing rule in the instruction.
What if no matching issue exists?
Tell Notis how to handle that case in the same plain-language instruction.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Moonclerk to GitHub. A trigger fires from one place; an action lands in another.
Moonclerk 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 Moonclerk 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.