Make a weekly sales check easier to finish
Update your weekly sales note and get a concise Gumroad sales summary for the period, ready to review in the workspace where you plan.
Trigger
Page Properties Updated
Triggers when properties of a Notion page are 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 property change in the workspace the integration has access to. Adding a column to a data source fires this trigger once per existing row. Customers can branch on `data.updated_properties` (array of property IDs) to filter downstream.
Action
Get Sales
Tool to retrieve all successful sales by the authenticated user. use when you need to list your gumroad sales, optionally filtering by email, date range, product, or pagination.
Why this helps
A weekly review can become a chore when you have to remember the date range, find sales, and write the recap from scratch.
- Make your weekly review more repeatable.
- Reduce the effort involved in writing a sales recap.
- Keep a summary near the rest of your weekly planning.
Setup
Build it in a few focused steps.
- 1Connect Notion and Gumroad to Notis once in the portal.
- 2Create an automation in the portal or ask Notis to summarize Gumroad sales when the weekly note changes.
- 3In one plain-language instruction, specify the successful sales and weekly period you want summarized.
- 4Select the Notion Page Properties Updated trigger and choose a reporting channel.
- 5Update a weekly note and check that the summary uses the correct dates.
Questions about this workflow
Does this trigger run on a schedule?
No. It runs when the Notion page properties change. For a scheduled check, use a recurring Notis trigger instead.
Can the note specify a different period?
Yes. State the desired reporting period in the instruction and check the first result.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Gumroad. A trigger fires from one place; an action lands in another.
Notion triggers
Gumroad actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Resource Subscriptions
Tool to show all active subscriptions of the user for the input resource. use when you need to review existing webhooks before adding a new one.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Sales
Tool to retrieve all successful sales by the authenticated user. use when you need to list your gumroad sales, optionally filtering by email, date range, product, or pagination.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Get User
Tool to retrieve the authenticated user's data. use when you need the current user's profile details after authentication.
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.
Subscribe to Resource
Tool to subscribe to a resource. use when you need to receive real-time event webhooks after creating your webhook endpoint.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Unsubscribe From Resource
Tool to unsubscribe from a resource. use after verifying the subscription id exists to remove webhook.
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 Gumroad, 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 Gumroad.