Turn refund events into a clear follow-up queue
A refund should trigger an explicit next step instead of lingering as an unresolved mental note.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Add labels to an issue
Adds labels (provided in the request body) to a repository issue; labels that do not already exist are created.
Why this helps
Refunds often require product, support, or delivery follow-up that gets lost between finance and project tools.
- Keep refund work visible.
- Reduce finance-to-support handoffs.
- Create a consistent response cue.
Setup
Build it in a few focused steps.
- 1Connect Moonclerk and GitHub to Notis once through the portal.
- 2Create the automation in the portal or ask Notis conversationally.
- 3Write one instruction to add a refund-follow-up label to the matching GitHub issue when a Moonclerk refund event arrives.
- 4Choose an incoming webhook trigger and a reporting channel.
- 5Test with one historical or test refund.
Questions about this workflow
Can this cover partial refunds?
Yes. State how partial refunds should be treated in the instruction.
Can it use an existing issue?
Yes. Describe how the matching GitHub issue should be recognized.
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
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Accept a repository invitation
Accepts a pending repository invitation that has been issued to the authenticated user.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
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.
Moonclerk and GitHub, 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 GitHub.