Verify Urgency With Current Node Health Data
Don't triage by assumption. Instantly check node health when issues are marked urgent.
Trigger
Public Team Issue Properties Updated
Fires when properties on a *public-team* Linear issue change (status, assignee, priority, labels, etc.). For private teams (lock icon in Linear's sidebar) use `LINEAR_PRIVATE_TEAM_ISSUE_PROPERTIES_UPDATED`.
Action
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.
Why this helps
You flag a validator issue as urgent to signal its importance, but you don't verify the node's actual health state to justify the urgency flag.
- Justify urgency flags with health data
- Prevent crying wolf on non-critical issues
- Triage decisions backed by infrastructure state
- Build credibility for urgent escalations
Setup
Build it in a few focused steps.
- 1Connect Linear and Beaconchain to Notis (one-time setup).
- 2Create automation: 'When a validator issue is marked urgent, immediately check the node health status.'
- 3Select the trigger: Public Team Issue Properties Updated (filter for priority/urgency changes).
- 4Choose your notification channel to receive health data with urgency notifications.
- 5Test by marking a validator issue as urgent and confirming health data arrives.
Questions about this workflow
What if the node health is good but I still think the issue is urgent?
You're the expert. The automation gives you data to make better decisions. Good health with high urgency means the issue is operational, not infrastructure-related.
Can this automation auto-downgrade issues if health is good?
Notis can be configured to send alerts and recommendations, but the final priority decision stays with you. This automation surfaces data, not makes decisions.
Will this spam me if I frequently update issue priority?
Only when issues transition to urgent will this check run. Set up the automation for critical urgency levels only if you want to reduce noise.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Linear to Beaconchain. A trigger fires from one place; an action lands in another.
Linear 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.
Comment Received Trigger
Triggered when a comment is received.
Issue Created Trigger
Triggered when a new issue is created.
Issue Updated Trigger
Triggered when an issue is updated. For example labels are changed, issue status is changed, etc.
Private Team Comment Created
Fires when a new comment is posted on an issue in a private Linear team (polled with the connected user's token).
Private Team Issue Created
Fires when a new issue appears in a private Linear team (polled with the connected user's token).
Private Team Issue Properties Updated
Fires when properties on an issue change in a private Linear team (polled with the connected user's token).
Connect any two apps with Notis in the middle.
Linear 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.