Recheck macro inputs when a brief evolves
Revise the body of a research brief and have Notis retrieve the macro data for its updated scope.
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 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
Research assumptions evolve, but the supporting indicator lookup may be forgotten during a busy workday.
- Links a content revision to a fresh data retrieval step.
- Helps prevent outdated macro context from lingering in a changing brief.
- Keeps the workflow centered on the existing Notion page.
Setup
Build it in a few focused steps.
- 1Connect Notion and Eodhd apis to Notis once through the portal.
- 2Create an automation in the portal or ask Notis to create it in plain language.
- 3In one instruction, tell Notis to read the updated brief and retrieve indicators for its current country and date range.
- 4Pick the Notion Page Content Updated trigger, scoped to the brief if useful, and select a run-report channel.
- 5Test with one real brief edit that changes its stated research scope.
Questions about this workflow
Can I scope this to one brief?
Yes. The Page Content Updated trigger can be scoped to a specific page.
Why use a content trigger?
It is suitable when the country or period is described in the brief body rather than stored in page properties.
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.