Skip to content
Notis

Connect GitHub to Moonclerk

When something happens in GitHub, Notis takes the next step in Moonclerk. Describe what you want in plain English, or start from one of the examples below.

When this happens · Trigger

Do this · Action

Examples

Ways Notis can move work from GitHub to Moonclerk

View example

Check subscriptions when a launch PR opens

Review Moonclerk subscriptions automatically when a launch pull request is created, so billing readiness does not get buried in code work.

View example

Verify payments after a pull request approval

When a pull request is approved, review recent Moonclerk payments so the next release is not based on stale revenue assumptions.

View example

Check customer plans when a customer issue is created

When a GitHub issue captures a customer concern, retrieve Moonclerk customers so support and product decisions have billing context.

View example

Reconcile payments when a revenue issue closes

When a GitHub issue tracking a revenue or billing problem changes state, review Moonclerk payments to confirm the operational impact is understood.

View example

Review subscriptions after a deployment is created

When a GitHub deployment is created, retrieve Moonclerk subscriptions to keep production changes aligned with current customer billing state.

View example

Review payments after a failed deployment status

When a deployment status reports failure, list Moonclerk payments so you can quickly assess whether customers may have been affected.

View example

Check subscriptions when a pull request gets a new commit

When a pull request changes, review subscriptions to keep billing-sensitive code work connected to the customers it may affect.

View example

Review customers after a code scanning alert

When GitHub creates a code scanning alert, retrieve Moonclerk customers to help assess the potential customer exposure without a separate manual search.

View example

Check customers when a secret scanning alert appears

When GitHub detects a secret scanning alert, retrieve Moonclerk customers to support a fast, organized assessment of possible exposure.

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.

TriggerScheduled

List Customers

List customers and their plans.

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

List Discounts

List discounts applied to customers.

ActionInstant

New Workflow Artifact Created

Triggers when a new workflow artifact is created in a repository.

TriggerPolling

List Payment Forms

List available payment forms.

ActionInstant

Branch Changed

Triggers when a branch receives commits or its protection settings change.

TriggerPolling

List Payments

List payments, optionally filtered by form, customer, date, or status.

ActionInstant

New Branch Created

Triggers when a new branch is created in a repository.

TriggerPolling

List Subscriptions

List subscriptions.

ActionInstant

Check Run Status / Conclusion Changed

Triggers when a check run’s status or conclusion changes.

TriggerPolling

Check Suite Status / Conclusion Changed

Triggers when a check suite’s status or conclusion changes for a reference.

TriggerPolling

New Code Scanning Alert Created

Triggers when a new code scanning alert is created in a repository.

TriggerPolling
Trigger Types

Four ways to start an automation.

A trigger is the event that kicks a workflow off. Notis supports four kinds: an event in a connected app, an inbound webhook, a schedule (recurring or one-time), and a change in one of your Notis databases.

Integration triggers

Fire when something happens inside a connected app. New Notion page, Stripe charge, Linear issue: any of 1,500+ apps can start a workflow.

New Notion pageStripe chargeCalendar event

Webhook triggers

A unique URL per workflow. Anything that can send an HTTP POST can start an automation, including no-code tools that speak webhooks.

Any HTTP POSTCustom backendIoT event
Works with
ZapierPipedream
Most used

Scheduled triggers

Run a workflow on the clock, on a recurring schedule or once at a set date and time. Daily standups, hourly syncs, a one-off launch reminder: the workhorse of Notis.

Daily · 8:00Weekdays onlyOnce · Dec 13
Beta

Database triggers

Fire when a row in one of your Notis databases is added or edited, with optional filters on its properties. New lead added, status changed, value crosses a limit.

Row addedProperty editedValue > limit
Why AI automation

Classic automation breaks. AI adapts.

Same triggers and actions, smarter middle. AI handles the fuzziness that breaks traditional Zapier-style workflows the moment a field gets renamed.

Classic automationAI automation
Cost
$ · pay per run
$$ · AI models per run
Reliability
Breaks on schema change
Adapts to format changes
Setup
Click 8 dropdowns
Describe it in English
Handles fuzzy
Hard-coded fields only
Reads intent, summarises
Human in loop
Bolted on
Built in · approval inbox
Maintenance
You own every break
Self-heals · we own it
Ease of use

Describe it. Notis builds it.

Skip the visual builder. Tell Notis what you want, in plain English. It writes the workflow, you review and deploy.

Notis

You · in the Notis Builder

NEW

“When a row gets added to the Q4 OKRs Notion database and the status is Blocked, send a Telegram message to the owner with a summary of what's blocking, and ping me if there's no reply within 24 hours.”

Notis built this automation:

TriggerRow added to "Q4 OKRs"
Condition✦Status = "Blocked"
AI step✦Summarise the blocker in plain English
ActionDM the row owner with summary
Timeout✦No reply in 24h → ping you
Observability

Watch every run.

Notis Desktop is Mission Control for your AI automations. See every run, replay, edit, or rewind. Set approval gates so Notis pauses before destructive actions.

  • Full run history with inputs, outputs and traces
  • Replay any run with edited inputs
  • Approval inbox, confirm via chat in one tap
  • Audit logs for compliance teams

Automations

Inbox

All12Manager5Telegram1Messages0Whatsapp2Email4Slack8

Migrate background jobs to a durable queue You can cancel it through Stripe

3 days

Notis v3 release update This one’s v3: Notis Manager (desktop app with …

8 days

Add multi-tenant RBAC User initiates a voice call

13 days

Draft pricing v (tiers, limits, overages) and sanity-check margins

2 weeks

Verify analytics events for new features That’s a really interesting automat…

1 month

Everything in the box.

Whatever starts the workflow, the platform underneath is the same: a thinking brain, full visibility, and you in control.

AI in the middle

Every step can include an LLM call: summarise, classify, extract, rewrite.

Full observability

Every run, every step, every input, all replay-able from Mission Control.

Human in the loop

Pause for approval. Notis pings you in chat with one-tap approve.

Self-healing

When an API changes shape, Notis adapts the parser. Less midnight fire-fighting.

Related pairs

More ways to connect GitHub and Moonclerk

Connect any two apps with Notis in the middle.

GitHub and Moonclerk, or any other combination from 1,500+ 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.