Ground thesis edits in historical price data
Revise a coin thesis and have Notis retrieve historical prices, making it easier to compare your reasoning with past performance.
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
Get Coin History
Tool to retrieve historical price data for a specific coin over a time period. use when you need to analyze past performance of a coin; call after confirming its uuid.
Why this helps
Thesis revisions can drift away from the evidence that originally shaped them.
- Bring historical context into a thesis review.
- Lower the effort of revisiting supporting data.
- Encourage evidence-based note updates.
Setup
Build it in a few focused steps.
- 1Connect Notion and Coinranking to Notis once.
- 2In one plain-language instruction, tell Notis to fetch historical prices for the identified coin when a thesis page's content changes.
- 3Select the Notion Page Content Updated trigger and scope it to the thesis page or data source.
- 4Pick a report channel and test with one real thesis edit.
Questions about this workflow
Can the workflow infer any coin from a page?
The prompt should identify the coin clearly, and Coinranking needs its uuid confirmed before a history lookup.
Will it change the thesis?
No. It retrieves price history for review; the workflow does not make an investment decision.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Coinranking. A trigger fires from one place; an action lands in another.
Notion triggers
Coinranking actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Coin History
Tool to retrieve historical price data for a specific coin over a time period. use when you need to analyze past performance of a coin; call after confirming its uuid.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Coins
Tool to retrieve a list of all coins with optional filters and pagination. use when you need to fetch coins matching specific criteria and paginate through results.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Get Reference Currencies
Tool to retrieve a list of all reference currencies with optional pagination. use when you need supported fiat or crypto denominators for price conversions.
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.
Get Global Crypto Market Stats
Tool to retrieve global cryptocurrency market statistics. use when you need an overview of the entire crypto market.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Get Tags
Tool to fetch all coin tags. use when you need the canonical list of tags after authenticating.
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 Trending Coins
Tool to retrieve a list of trending coins ranked by user engagement and popularity. use when you need up-to-date trending coin data for analysis or display.
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 Coinranking, 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 Coinranking.