Start each week with payment follow-up already sorted
A weekly review can turn scattered billing concerns into a short, visible queue.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
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
Payment follow-up gets postponed because it competes with product work and is easy to lose in a separate dashboard.
- Create a predictable review rhythm.
- Make overdue attention visible in GitHub.
- Lower the mental cost of remembering follow-ups.
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 set it up.
- 3Write one plain-language instruction to review relevant Moonclerk payment context and label matching GitHub issues needing follow-up.
- 4Choose a weekly recurring schedule and a channel for run reports.
- 5Test it against one known payment case.
Questions about this workflow
How often does it run?
You choose the recurring schedule when creating the automation.
Can it review only selected customer work?
Describe the relevant scope in the 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.