Review new validators without a separate lookup
Add a validator to your Notion tracker and let Notis retrieve its Beaconchain details for you.
Trigger
New Page
Triggers when a new page is added to a Notion database.
Action
Get Validator
Tool to retrieve information for a specific validator from beaconcha.in api.
Why this helps
A new validator entry can get buried while you switch tools to look up its current details.
- Get validator information when a new tracker entry arrives.
- Keep the lookup attached to the moment you capture the work.
- Receive the result in the channel you use for run reports.
Setup
Build it in a few focused steps.
- 1Connect Notion and Beaconchain to Notis once through the portal.
- 2Create an automation in the portal, or tell Notis in any connected channel what result you want.
- 3Use one plain-language instruction asking Notis to retrieve Beaconchain information for the validator in each new Notion record and report it.
- 4Select the Notion New Page trigger and choose a channel for run reports.
- 5Test it by adding one real validator record to the database.
Questions about this workflow
Does this update the Notion record?
The Beaconchain action retrieves validator information. Ask Notis to report the result in your chosen channel; this action does not write back to Notion.
What should the Notion record contain?
Include enough identifying information for Notis to determine which validator to look up, such as its validator index or public key.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Beaconchain. A trigger fires from one place; an action lands in another.
Notion triggers
Beaconchain actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Node Health
Tool to get the health status of the node. use when you need to check if the node is ready, syncing, or in an error state.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Validator
Tool to retrieve information for a specific validator from beaconcha.in api.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
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 Beaconchain, 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 Beaconchain.