Keep Incident Discussions Grounded in Real Validator Data
Stop discussing incidents without data. Get validator state automatically when your team discusses problems.
Trigger
Public Team Comment Created
Fires when a new comment is posted on a *public-team* Linear issue. For private teams (lock icon in Linear's sidebar) use `LINEAR_PRIVATE_TEAM_COMMENT_CREATED`.
Action
Get Validator
Tool to retrieve information for a specific validator from beaconcha.in api.
Why this helps
Your team discusses an incident in Linear comments but validator state isn't visible, turning discussion into theory instead of data-driven problem-solving.
- Discussions grounded in current validator data
- Reduce speculation and guesswork
- All relevant data in one thread
- Faster incident resolution with data-driven discussion
Setup
Build it in a few focused steps.
- 1Connect Linear and Beaconchain to Notis (one-time setup).
- 2Create automation: 'When someone comments on an incident issue, fetch the current validator state.'
- 3Select the trigger: Public Team Comment Created (filter for incident-labeled issues).
- 4Choose your notification channel to receive validator state with incident comments.
- 5Test by commenting on an incident issue and verifying validator data arrives.
Questions about this workflow
How does Notis know which comments are incident-related?
Specify in the automation prompt. Filter by issue labels, projects, or keywords that mark incidents. This prevents unnecessary validator data on unrelated discussions.
What if the incident is resolved before someone comments?
Notis will still provide validator state at comment time. Current state is still useful for post-mortems and learning.
Can I get historical validator state from when the incident started?
Notis pulls current state. For historical analysis, you'd need a separate audit trail or monitoring archive.
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.