Keep macro research aligned with schema changes
Change the research data source structure and have Notis retrieve indicators when country coverage is affected.
Trigger
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.
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 schema adjustment can change what the research tracks without prompting anyone to revisit its macro inputs.
- Ties structural research changes to a potential context refresh.
- Helps maintain alignment between tracked coverage and supporting indicators.
- Avoids relying on someone to remember each follow-up.
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.
- 3Use a single instruction asking Notis to review schema changes and retrieve indicators only when country or date coverage has changed.
- 4Select the Notion Data Source Schema Updated trigger and choose a channel for reports.
- 5Test with one real schema update that adds or renames a country or period property.
Questions about this workflow
Will every column change request macro data?
The prompt can ask Notis to act only when a change affects the country or date coverage.
Can this trigger monitor one data source?
Yes. The trigger supports an optional data source filter.
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.