Keep new client billing from slipping through the cracks
Add a client in Notion and have Notis check Moonclerk subscriptions, so you can see whether recurring billing needs attention.
Trigger
New Page
Triggers when a new page is added to a Notion database.
Action
List Subscriptions
Tool to list subscriptions. use when you need to retrieve all subscriptions after authenticating.
Why this helps
You create a client record and then have to remember to open Moonclerk and check their billing separately.
- See subscription status while onboarding a client.
- Reduce the number of times you switch between tools.
- Spot records that may need a billing check.
Setup
Build it in a few focused steps.
- 1Connect Notion and Moonclerk to Notis once in the portal.
- 2Create an automation in the portal and name it for new client subscription checks.
- 3Write one plain-language prompt asking Notis to review Moonclerk subscriptions when a new client is added in Notion.
- 4Choose the Notion New Page trigger and a channel for run reports.
- 5Test with one real client record and confirm the subscription review is useful.
Questions about this workflow
Does this create a Moonclerk subscription?
No. The available Moonclerk action lists subscriptions for review; it does not create or change them.
Can I limit this to one Notion database?
Describe the intended client database in the automation prompt and select the New Page trigger. Notis interprets the instruction in plain language.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Moonclerk. A trigger fires from one place; an action lands in another.
Notion 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.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
List Payment Forms
Tool to retrieve a list of all payment forms. use after authenticating to inspect available payment forms.
Comment Created
Triggers when a new comment is created in Notion. Optional `page_id` filter scopes to comments on a specific page. When omitted, fires for any new comment in the workspace the integration has access to. Requires the 'Read comments' capability on the Notion integration. If a connection was authorized before that capability was enabled, the user must re-authorize the connection for comment events to flow.
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 Comment
Triggers when a new comment is added to a specified Notion block or page.
List Subscriptions
Tool to list subscriptions. use when you need to retrieve all subscriptions after authenticating.
Database Created
Triggers when a new Notion database (the container) is created. A database is the post-2025-09-03 container that holds one or more data sources. This trigger fires for the container's creation event (`database.created`), distinct from `NOTION_DATASOURCE_CREATED` which fires when a new data source is added to an existing database. Most customers calling Notion's `POST /v1/databases` (the legacy API) or creating a database via the Notion UI will see this event. Adding a new data source to an existing database fires `data_source.created` instead — use `NOTION_DATASOURCE_CREATED` for that. Notion's payload puts `entity.type: "block"` (the container is a `child_database` block in the content tree) and `entity.id` is the database id.
Data Source Created
Triggers when a new Notion data source is created. Fires workspace-wide. The payload's `data.parent` carries the data source's tree parent (typically the teamspace) for downstream filtering. A single template-based database creation can fire multiple `data_source.created` events at once — one per data source the template instantiates.
Data Source Schema Updated
Triggers when a Notion data source's schema is updated. Fires on column add / remove / rename. Payload includes `data.updated_properties: [{id, name, action}]` so consumers can discriminate the kind of change downstream. Optional `data_source_id` filter scopes to schema changes on a single data source. When omitted, fires for any schema change in the workspace the integration has access to. Note: adding a column also fires `page.properties_updated` once per existing row in the data source. Customers wanting a single structural-change signal should use this trigger.
Connect any two apps with Notis in the middle.
Notion 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.