Refresh validator details when a Jira issue changes
Keep a validator review moving when its Jira issue changes by retrieving the specified validator information for a fresh run report.
Trigger
Updated Issue
Fires when an existing issue is changed in the Jira project you configure — for example its status, assignee, or any other field on the issue is updated. Only issues in that project produce an event. It does not fire on comment activity: adding, editing, or deleting a comment on an issue will not produce an event from this trigger.
Action
Get Validator
Tool to retrieve information for a specific validator from beaconcha.in api.
Why this helps
A changed ticket can leave a validator review stale if someone has to remember to rerun the lookup separately.
- Rerun a specified validator lookup after a Jira issue change.
- Make returned validator information available in the run report.
- Reduce manual reminders to repeat a check after ticket updates.
Setup
Build it in a few focused steps.
- 1Connect Jira and Beaconchain once in the Notis portal.
- 2Create an automation in the portal under Automations, New Automation, and give it a name.
- 3Describe in one instruction that an updated Jira issue should trigger a lookup for its specified validator and a concise report.
- 4Choose the Jira Updated Issue trigger and select where run reports should go.
- 5Test with one real issue update that includes the validator identifier.
Questions about this workflow
What counts as an issue change?
The Jira Updated Issue event fires when an existing issue in the configured project is changed, such as its status, assignee, or another issue field.
Do comments trigger this workflow?
No. The listed Jira Updated Issue event does not fire on comment activity.
Where does the validator identifier come from?
Provide it in the issue details or the automation instruction so Notis knows which specific validator to retrieve.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Jira to Beaconchain. A trigger fires from one place; an action lands in another.
Jira 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.
New Issue
Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.
New Project
Triggered when a new project is added in Jira
Updated Issue
Fires when an existing issue is changed in the Jira project you configure — for example its status, assignee, or any other field on the issue is updated. Only issues in that project produce an event. It does not fire on comment activity: adding, editing, or deleting a comment on an issue will not produce an event from this trigger.
Connect any two apps with Notis in the middle.
Jira 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.