Review Validator Details from a Release Webhook
Add a validator context check to the release signal you already send.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Get Validator
Tool to retrieve information for a specific validator from beaconcha.in api.
Why this helps
Release workflows can finish without a quick look at the validator information relevant to the change.
- Add validator context to release reports
- Keep release follow-up in one place
- Reduce manual Beaconchain lookups
Setup
Build it in a few focused steps.
- 1Connect Beaconchain in Notis once.
- 2Create a named automation using Automations, New Automation.
- 3Tell Notis to retrieve validator information using the release webhook context and summarize any review points.
- 4Choose a webhook trigger and select the report destination.
- 5Test with one real release webhook.
Questions about this workflow
What release data can it use?
It can use the context included in the webhook request and any validator identifier supplied in your instruction.
Does it change the release?
No. It only retrieves validator information and reports it.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Google Docs to Beaconchain. A trigger fires from one place; an action lands in another.
Google Docs 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 Document Created
Triggers when a new Google Doc is created. This trigger monitors Google Docs and fires when new documents are detected. Uses timestamp filtering to efficiently poll for new documents.
Document Deleted
Triggers when an existing Google Doc is deleted (moved to trash). This trigger monitors Google Docs and fires when documents are trashed.
Document Placeholder Filled
Triggers when a Google Doc's plain text changes such that a configured placeholder token/pattern is no longer present (i.e., the document has been filled in). This trigger monitors a specific Google Doc and fires when a placeholder pattern that was previously present is no longer found in the document's plain text.
Document Search Update
Triggers when a Google Doc matching a user-defined search query is newly created or updated since the last poll. This trigger uses timestamp filtering to efficiently monitor documents.
Document Structure Changed
Triggers when a Google Doc's structure changes (headers/footers added/removed, tables/images count changes). This trigger monitors a specific document for structural changes like: - Headers added or removed - Footers added or removed - Tables added or removed - Images (inline objects) added or removed - Positioned objects added or removed - Footnotes added or removed
Document Updated
Triggers when an existing Google Doc is updated or modified. This trigger monitors Google Docs and fires when documents are updated.
Connect any two apps with Notis in the middle.
Google Docs 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.