Review live worker details when tracking structure changes
When your worker tracking schema changes, have Notis retrieve live worker data to support a focused review of the updated process.
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 Worker Data
Retrieve detailed real-time data for a specific mining worker. This tool fetches comprehensive information about a worker including: - Current status (online/offline/idle) - Hardware info (GPUs/ASICs with temperatures, fans, power) - Mining info (coin, pool, client software) - Hashrate data (current hashrates for main/dual/CPU mining) - Share statistics (accepted, rejected, stale) - Revenue estimates Use this when you need detailed metrics for a specific worker. The worker name must exactly match a worker configured in the minerstat dashboard. Returns found=False if the worker doesn't exist.
Why this helps
A revised tracking structure can leave uncertainty about whether the information being captured still supports operational checks.
- Prompt a live worker check when tracking structure changes.
- Support a practical review of the operational fields you rely on.
- Reduce the effort of remembering a separate validation lookup.
Setup
Build it in a few focused steps.
- 1Connect Notion and Minerstat to Notis once through the portal.
- 2Create an automation with a prompt to review specified workers when the tracking schema changes.
- 3Choose Data Source Schema Updated and scope it to the relevant data source if needed.
- 4Select a report channel and test with one real schema update.
Questions about this workflow
What changes activate this trigger?
The trigger fires when columns are added, removed, or renamed in a Notion data source.
Can it be restricted to one data source?
Yes. The trigger supports an optional data_source_id scope.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Minerstat. A trigger fires from one place; an action lands in another.
Notion triggers
Minerstat actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Coins Data
Retrieves mining coin data from minerstat API including hashrates, difficulty, rewards, and prices. Use this tool to get current mining statistics for cryptocurrencies. You can filter results by specific coin tickers (e.g., 'BTC,ETH') or by mining algorithms (e.g., 'SHA-256,Ethash'). Returns data such as network hashrate, difficulty, estimated mining rewards, current price, and trading volume for each coin. Note: `difficulty` and network hashrate fields may be null for some coins; validate their presence before using in calculations.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Hardware Data
Retrieve mining hardware data from minerstat including hashrates, power consumption, and specifications. Use this tool to get benchmark data for GPUs and ASIC miners to compare mining performance across different hardware. Filter by type (gpu/asic) or brand to narrow results. Combine both filters together to avoid mixed variants with differing hashrate and power draw values.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Get Pools Data
Retrieve mining pool data from minerstat. Requires an authenticated minerstat connection. Returns a list of mining pools with their supported coins, fees, payout thresholds, and other details. Use to discover pools for a specific coin or explore all available mining pools.
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 Worker Activity
Retrieve activity logs for a specific worker for the last 3 days. Returns online/offline events, errors, and other activity for troubleshooting worker uptime issues or auditing worker behavior. The API key is automatically extracted from the Authorization header.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Get Worker Data
Retrieve detailed real-time data for a specific mining worker. This tool fetches comprehensive information about a worker including: - Current status (online/offline/idle) - Hardware info (GPUs/ASICs with temperatures, fans, power) - Mining info (coin, pool, client software) - Hashrate data (current hashrates for main/dual/CPU mining) - Share statistics (accepted, rejected, stale) - Revenue estimates Use this when you need detailed metrics for a specific worker. The worker name must exactly match a worker configured in the minerstat dashboard. Returns found=False if the worker doesn't exist.
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 Minerstat, 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 Minerstat.