Verify Node Health Every Time an Incident Is Reported
Stop repeating manual health checks across multiple incident tickets. Get verified node status automatically for every report.
Trigger
Public Team Issue Created
Fires when a new issue is created in a Linear *public* team. For private teams (lock icon in Linear's sidebar) use `LINEAR_PRIVATE_TEAM_ISSUE_CREATED`.
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
Your team reports validator incidents in Linear, but you end up doing the same manual Beaconchain checks multiple times across different tickets.
- Eliminate redundant manual health checks across tickets
- Ensure every incident has baseline health data
- Reduce investigation time per incident
- Build consistent incident response with health data
Setup
Build it in a few focused steps.
- 1Connect your Linear workspace and Beaconchain account to Notis (one-time setup).
- 2Create automation: 'When a team member creates an incident issue in Linear, check the current node health status.'
- 3Select the trigger: Public Team Issue Created in Linear.
- 4Set your notification channel to alert the team when incidents come in with health data.
- 5Test by having a team member create a test incident and verify health status is included.
Questions about this workflow
How does Notis know which issues are incidents?
You tell it. In the automation prompt, specify the issue label, project, or keyword that marks something as an incident. This prevents false positives.
Will health checks happen for every issue or just incidents?
You control scope. You can limit triggers to issues with an 'incident' label, or run on specific projects. Start with your critical projects.
What if multiple team members report the same incident?
Each report will trigger a health check. You'll have consistent data across tickets, making it easy to compare reports and consolidate if needed.
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.