Replace scattered payment checks with one weekly digest
A predictable weekly review can hold the payment context that otherwise gets lost between engineering tasks.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
List Payments
Tool to list payments. use when you need to retrieve all payments or filter by form, customer, date range, or status after authenticating.
Why this helps
Payment review competes with urgent work and often happens only when something feels wrong.
- Creates one predictable place to review payment activity.
- Reduces repeated context switching during the week.
- Helps founders spot changes before they become urgent.
Setup
Build it in a few focused steps.
- 1Connect GitHub and Moonclerk to Notis once through the portal.
- 2Create an automation in the portal or ask Notis to send a weekly payment review.
- 3Use this instruction: List recent Moonclerk payments and summarize the revenue context connected to recent GitHub work.
- 4Choose a weekly Notis schedule, select the channel for reports, and test with one immediate run.
Questions about this workflow
Does the digest modify GitHub or Moonclerk?
No. It gathers and summarizes payment data for review.
Can I choose the weekly day?
Yes. Set the recurring Notis schedule that fits your operating rhythm.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Moonclerk. A trigger fires from one place; an action lands in another.
GitHub triggers
Moonclerk actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
List Customers
Tool to list customers (plans) from moonclerk. use when you need to retrieve customer data with optional filters. use after authenticating api credentials.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
List Discounts
Tool to retrieve a list of all discounts applied to customers. use after authenticating api credentials.
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.
List Payment Forms
Tool to retrieve a list of all payment forms. use after authenticating to inspect available payment forms.
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.
List Payments
Tool to list payments. use when you need to retrieve all payments or filter by form, customer, date range, or status after authenticating.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
List Subscriptions
Tool to list subscriptions. use when you need to retrieve all subscriptions after authenticating.
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.
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.
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.
Connect any two apps with Notis in the middle.
GitHub and Moonclerk, 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 Moonclerk.