Explore event categories when creating a tracker
Start a new Notion tracker and have Notis retrieve CoinMarketCal's available categories so you can decide what kinds of events to follow.
Trigger
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.
Action
List Event Categories
Tool to list all event categories. Use when you need to fetch available event categories.
Why this helps
A new tracker can become an unstructured catch-all if its owner has not reviewed the available event types first.
- Makes the available category options visible during tracker setup.
- Gives the founder a concrete starting point for defining review scope.
- Reduces uncertainty about how to organize event research.
Setup
Build it in a few focused steps.
- 1Connect Notion and CoinMarketCal to Notis once.
- 2Create an automation in the portal or ask Notis conversationally.
- 3Tell Notis to retrieve CoinMarketCal event categories when a new tracking data source is created and summarize the options in its run report.
- 4Choose the Notion Data Source Created trigger and a run-report channel.
- 5Test by creating one real tracking data source and reviewing the category list.
Questions about this workflow
Does this create categories in Notion?
No. It retrieves CoinMarketCal's available categories and reports them for you to use when planning the tracker.
Why use a data source trigger?
It runs when a new data source is created, which can signal that you are setting up a new structured tracker.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Coinmarketcal. A trigger fires from one place; an action lands in another.
Notion triggers
Coinmarketcal actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
List Coins
Tool to retrieve list of all available coins/cryptocurrencies in CoinMarketCal database. Use when you need to fetch coin information including IDs, names, symbols, and event counts.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
List Event Categories
Tool to list all event categories. Use when you need to fetch available event categories.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
List Cryptocurrency Events
Tool to retrieve list of cryptocurrency events. Use when you need to fetch upcoming or past crypto events filtered by date range, coins, categories, or other criteria. Note: Cannot retrieve events before 25/11/2017. The can_occur_before field is important as some events may happen before their stated date.
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 Coinmarketcal, 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 Coinmarketcal.