Turn new Drive review files into validator lookups
Drop a review file in Drive and let Notis retrieve Beaconchain information for the validator it identifies, so you can review the source and status together.
Trigger
File Created
Triggers when a new file is created in Google Drive.
Action
Get Validator
Tool to retrieve information for a specific validator from beaconcha.in api.
Why this helps
A new review document can sit unnoticed while someone separately searches for its validator details.
- Pair a newly created review file with a validator lookup.
- Reduce repeated searching across Drive and Beaconchain.
- Make review follow-up easier to start from the source document.
Setup
Build it in a few focused steps.
- 1Connect Google Drive and Beaconchain once in the Notis portal.
- 2Create an automation and describe how a new review file should lead to a validator lookup.
- 3Pick File Created as the trigger.
- 4Choose where Notis should send run reports.
- 5Test with one real review file that names a validator.
Questions about this workflow
Does the file need to identify one validator?
Yes, the automation needs a validator identifier in the file or in the instruction context to request a specific validator.
Can Notis infer details that are not in the file?
Notis can analyze the returned Beaconchain information, but it cannot supply a missing validator identifier or an undocumented baseline.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Google Drive to Beaconchain. A trigger fires from one place; an action lands in another.
Google Drive 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 Added (Docs/Sheets/Slides)
Triggers when a new comment is added to Google Docs, Sheets, or Slides.
File Created
Triggers when a new file is created in Google Drive.
File Deleted or Trashed
Triggers when a file is moved to trash or permanently deleted in Drive.
File Shared (Permissions Added)
Triggers when new sharing permissions are granted to a file or folder. Uses Drive's `changes.list` endpoint with inline `permissions` in the `fields` mask so each change carries the file's current permission set provider-atomically. We diff that against `seen_permission_keys` to identify newly added grants. Drive page tokens are the primary cursor; if Drive rejects a stored token, the trigger raises `PollingTriggerError` without clearing state rather than silently re-baselining and dropping events. Limitation: truly ephemeral permissions (added and revoked between two polls without any other file modification in between) are not detected. Drive Activity API would catch those but requires an additional OAuth scope and a different payload contract.
File Updated
Triggers when a file's metadata or content changes in Google Drive.
Google Drive Changes
Triggers when changes are detected in a Google Drive.
Connect any two apps with Notis in the middle.
Google Drive 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.