Keep documented Ko-fi payments easier to reconcile
Record a Ko-fi webhook example in Notion and let Notis review the payment details, so you can focus on the next supporter follow-up.
Trigger
Page Content Updated
Triggers when the body content of a Notion page is updated. Customer optionally scopes with at most one of: - data_source_id: any row in this data source - page_id: this specific page - parent_page_id: any page whose immediate parent is this page With none set, fires for any page content edit in the workspace the integration has access to. Notion aggregates content edits within a short window (~60s typical).
Action
Receive Ko-fi payment webhook
Receives and validates Ko-fi payment webhook events. Use this to process real-time notifications for donations, subscriptions, commissions, and shop orders from Ko-fi. The webhook includes payment details, supporter information, and transaction metadata. Returns validated payment data to confirm receipt (Ko-fi expects 200 OK to prevent retries).
Why this helps
Payment details recorded in project notes can be easy to overlook when switching between supporter work and business admin.
- Bring payment review into the Notion context where you documented the event.
- Get validated payment details returned for reconciliation.
- Reduce the mental effort of switching between notes and supporter administration.
Setup
Build it in a few focused steps.
- 1Connect Notion and Ko-fi to Notis once through the portal.
- 2Create an automation in the portal, or ask Notis conversationally to review a Ko-fi payment webhook example documented in Notion.
- 3Use one plain-language instruction asking Notis to review the documented payment event and return validated details for reconciliation.
- 4Choose the Notion Page Content Updated trigger and a channel for run reports.
- 5Test with one real, non-sensitive webhook example documented in a Notion page.
Questions about this workflow
What starts this automation?
A content update to a Notion page in the scope you choose for the Page Content Updated trigger.
What does the Ko-fi action do?
It receives and validates Ko-fi payment webhook events, then returns validated payment data. This action does not create or edit Ko-fi supporter records.
Will this send a thank-you message to a supporter?
No. The available Ko-fi action only receives and validates payment webhooks; it does not send messages.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Ko fi. A trigger fires from one place; an action lands in another.
Notion triggers
Ko fi actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Receive Ko-fi payment webhook
Receives and validates Ko-fi payment webhook events. Use this to process real-time notifications for donations, subscriptions, commissions, and shop orders from Ko-fi. The webhook includes payment details, supporter information, and transaction metadata. Returns validated payment data to confirm receipt (Ko-fi expects 200 OK to prevent retries).
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
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.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
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 Ko fi, 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 Ko fi.