Keep Box validator reviews moving on a schedule
A recurring check can gather Beaconchain information from your Box review files and flag records that need attention.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Get Validator
Tool to retrieve information for a specific validator from beaconcha.in api.
Why this helps
Validator details spread across review files are easy to overlook when nobody owns the next manual lookup.
- Gather available validator information on a recurring schedule
- Identify review files that lack a usable validator ID
- Get one report instead of reopening files individually
Setup
Build it in a few focused steps.
- 1Connect Box and Beaconchain once in the Notis portal.
- 2Create an automation in Automations, New Automation, and name it for the recurring validator review.
- 3Tell Notis to review the relevant accessible Box files, identify validator IDs where present, call Beaconchain Get Validator for each, and report results and missing IDs.
- 4Choose a recurring schedule, select where run reports go, and test with one real review file.
Questions about this workflow
Can the schedule find every file in Box?
The automation can only use files available to its connected Box access and the instruction provided. Specify which review files or location it should use in the prompt.
What happens when a file does not identify a validator?
The report should list that file as needing a validator ID. Notis should not guess the validator.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Box to Beaconchain. A trigger fires from one place; an action lands in another.
Box 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.
Collaboration Details Changed
Triggers when a collaboration's details change (e.g., role, status, expiration). This trigger monitors a specific collaboration and detects when any meaningful field changes, such as role, status, expiration date, access type, or acknowledgment status.
Comment Changed
Triggers when a comment's content or details change in Box. This trigger monitors a specific Box comment and detects when any meaningful field changes, such as message text edits, tagged message changes, or modification timestamp updates.
New File Comment Added
Triggers when a new comment is added to a file in Box. This trigger monitors a specific Box file and fires when new comments are detected.
File Metadata Changed
Triggers when a file's metadata or properties change in Box. This trigger monitors a specific Box file and fires when changes are detected in key fields like name, description, size, modification time, parent folder, or status.
File Shared Link Changed
Triggers when a file's shared link settings change in Box. This trigger monitors a specific Box file's shared link and fires when changes are detected in the shared link configuration, such as access level, permissions, password protection, expiration date, or vanity URL.
New File Version Uploaded
Triggers when a new file version is uploaded to a file in Box. This trigger monitors a specific Box file and fires when new versions are detected.
Connect any two apps with Notis in the middle.
Box 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.