Anchor new forecast assumptions in historical rates
Add a forecast assumption and retrieve its historical rate context to make the underlying currency choice easier to evaluate.
Trigger
New Page
Triggers when a new page is added to a Notion database.
Action
Get Historical Exchange Rates
Tool to retrieve historical exchange rate data for past dates going back to 1996. Use when you need to access exchange rates for a specific historical date with a base currency.
Why this helps
New assumptions can be recorded without the background data that would help a founder judge whether they are reasonable.
- Give assumptions a relevant historical reference.
- Make forecast reviews easier to explain.
- Reduce repeat research when assumptions are revisited.
Setup
Build it in a few focused steps.
- 1Connect Notion and CurrencyScoop to Notis once.
- 2Create an automation via the portal or by asking Notis for a new-assumption lookup.
- 3In one plain-language instruction, describe which forecast assumptions qualify and which currency pair and historical date to use.
- 4Select Notion New Page for the forecast assumptions data source and choose a run-report channel.
- 5Test with a new assumption page that includes a currency pair and date.
Questions about this workflow
Can the lookup use a specific date?
Yes. The page or instruction should provide the historical date and base currency.
Does a historical rate predict future performance?
No. It provides past rate data for context, not a forecast.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to CurrencyScoop. A trigger fires from one place; an action lands in another.
Notion triggers
CurrencyScoop actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Convert Currency
Tool to perform a single currency conversion from one currency to another for a specified amount. Use when you need to convert a specific amount between two currencies using mid-market rates.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Currencies
Tool to retrieve all supported currencies including their names and countries. Use when you need information about available currencies, either fiat or crypto.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Get Historical Exchange Rates
Tool to retrieve historical exchange rate data for past dates going back to 1996. Use when you need to access exchange rates for a specific historical date with a base currency.
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 Latest Exchange Rates
Tool to get real-time exchange rates for all supported currencies with a specified base currency. Use when you need current exchange rates for currency conversions or financial calculations.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Get Timeseries Exchange Rates
Tool to retrieve historical exchange rates for a given time period between start and end dates. Use when you need exchange rates for multiple dates in a date range for trend analysis or historical comparisons.
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 CurrencyScoop, 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 CurrencyScoop.