Keep macro coverage aligned with research changes
Update a page's country or coverage period and have Notis refresh the related macro indicator lookup.
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 Macro Indicators
Tool to retrieve macroeconomic indicators data. use when you need country-level economic indicators across a date range. use after confirming the api token is set.
Why this helps
A changed country or research period can leave the data in a brief out of date unless someone remembers to rerun the lookup.
- Responds to changes in the research scope recorded in Notion.
- Reduces the chance that an old lookup is mistaken for current coverage.
- Keeps the follow-up attached to the working page.
Setup
Build it in a few focused steps.
- 1Connect Notion and Eodhd apis to Notis once in the portal.
- 2Create an automation in the portal or ask Notis conversationally.
- 3Give Notis one plain-language instruction to review changed research properties and retrieve macro indicators when the country or date range differs.
- 4Select the Notion Page Properties Updated trigger and choose a reporting channel.
- 5Test by changing the coverage details on one real research page.
Questions about this workflow
Will every property edit run a lookup?
The prompt can tell Notis to retrieve data only when the country or date coverage relevant to the request changes.
What does Eodhd apis retrieve?
The selected action retrieves country-level macroeconomic indicators across a date range.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Eodhd apis. A trigger fires from one place; an action lands in another.
Notion triggers
Eodhd apis actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Macro Indicators
Tool to retrieve macroeconomic indicators data. use when you need country-level economic indicators across a date range. use after confirming the api token is set.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Mutual Funds Data
Tool to retrieve mutual funds data for a specified symbol. use after confirming the mutual fund ticker symbol.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Get Real-Time FOREX WebSocket Stream
Tool to retrieve real-time data for forex via websocket. use when you need live price updates for specific currency pairs.
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 Real-time WebSocket US Trades
Tool to retrieve real-time trade data for the us market via websocket. use when live updates for specific us symbols are required. example: subscribe to ['aapl', 'goog'].
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 Eodhd apis, 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 Eodhd apis.