Make retainer renewals easier to bill
Keep recurring client work from relying on a calendar reminder alone. A confirmed renewal in Notion can prompt Notis to create the matching Finmei invoice.
Trigger
New Page
Triggers when a new page is added to a Notion database.
Action
Create Invoice
Tool to create a new invoice. Use when you have all invoice details ready and need to record it. Example: "Create an invoice for customer X with two items.
Why this helps
Retainer renewals are easy to overlook when the renewal decision and the invoice live in different tools.
- Use the renewal record as a billing cue.
- Reduce manual re-entry for confirmed retainer work.
- See a report if a renewal is not ready to invoice.
Setup
Build it in a few focused steps.
- 1Connect Notion and Finmei to Notis once through the portal.
- 2Create a prompt asking Notis to invoice confirmed retainer renewals with complete billing information.
- 3Choose the Notion New Page trigger for the renewals database.
- 4Select a channel for run reports and test using one confirmed renewal.
Questions about this workflow
Can this invoice every renewal record?
Tell Notis to proceed only when the renewal is confirmed and has the details needed for an invoice.
Can it handle a renewal that is still under discussion?
Ask Notis to report that the record is not confirmed and leave it for your review.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Finmei. A trigger fires from one place; an action lands in another.
Notion triggers
Finmei actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Invoice
Tool to create a new invoice. Use when you have all invoice details ready and need to record it. Example: "Create an invoice for customer X with two items.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Delete Customer
Tool to delete a specific customer by their ID. Use after confirming the correct customer_id to remove the record.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Delete Invoice
Tool to delete an invoice. Use when you need to remove an existing invoice by its ID.
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.
Delete Payment
Tool to delete a payment. Use when you need to remove a payment by its ID after confirming it's obsolete.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Delete Product
Tool to delete a product by its ID. Use when you need to permanently remove a product from the catalog.
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.
Get Payment
Tool to retrieve details of a specific payment by its ID. Use after creating a payment or when you need to confirm payment details.
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.
Get Product by ID
Tool to retrieve a product by its ID. Use when you need detailed information about a single product.
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.
List Currencies
Tool to list all currencies supported by Finmei. Use when you need to retrieve available currency codes before creating transactions.
Connect any two apps with Notis in the middle.
Notion and Finmei, 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 Finmei.