Look further ahead with a monthly crypto event sweep
Once a month, have Notis review CoinMarketCal events for your Notion watchlist and report dates that could affect longer-range plans.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
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.
Why this helps
Short daily checks can miss events far enough ahead to matter for launches, budgets, or founder availability.
- Supports a broader planning horizon than a daily digest.
- Creates a recurring moment to revisit all tracked coins.
- Can surface dates worth adding to longer-range plans.
Setup
Build it in a few focused steps.
- 1Connect Notion and CoinMarketCal to Notis once.
- 2Create a monthly scheduled automation in the portal or ask Notis conversationally.
- 3Tell Notis to read tracked coins from Notion, retrieve CoinMarketCal events across a longer date window, and summarize the dates that may matter for planning.
- 4Choose a monthly schedule and the channel for run reports.
- 5Test with the watchlist and agree on a useful look-ahead period.
Questions about this workflow
How far ahead should it look?
Choose a window that fits your planning cycle and state it in the instruction.
Can this replace a near-term daily check?
It serves a different purpose: a monthly run can focus on longer-range planning, while a separate routine can check near-term dates.
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.