Review vendor currency changes with current rates
Update a vendor record in Notion and get a current-rate check for its currency details.
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 Latest Exchange Rates
Tool to get real-time exchange rate data for all available or specified currencies. use when you need current forex rates before performing currency conversions.
Why this helps
Changed vendor pricing can slip past review when currency checks are separate from vendor updates.
- Bring rate review alongside a vendor update.
- Check the current market context for a changed currency.
- Make supplier follow-up easier to resume.
Setup
Build it in a few focused steps.
- 1Connect Notion and Fixer to Notis once through the portal.
- 2Create an automation and write one plain-language prompt asking Notis to fetch current rates for currency codes in updated vendor records and report the change context.
- 3Choose the Notion Page Properties Updated trigger and a channel for run reports.
- 4Test by updating one vendor record's currency or quote details.
Questions about this workflow
Will every property edit cause a lookup?
The trigger fires on page property updates. In the prompt, ask Notis to act only when the update is relevant to currency or pricing.
Does Fixer provide vendor-specific pricing?
No. Fixer provides exchange rates; vendor terms still need to be reviewed in Notion.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Fixer. A trigger fires from one place; an action lands in another.
Notion triggers
Fixer actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Historical Rates
Tool to get historical exchange rate data for a specific date. use when you need past currency rates for all or selected currencies.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Latest Exchange Rates
Tool to get real-time exchange rate data for all available or specified currencies. use when you need current forex rates before performing currency conversions.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Get Supported Symbols
Tool to retrieve all supported currency symbols and their full names. use when you need to display or validate available currencies before performing 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.
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 Fixer, 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 Fixer.