Connect Adrapid to Beaconchain

When something happens in Adrapid, Notis takes the next step in Beaconchain. Describe what you want in plain English, or start from one of the examples below.

When this happens · Trigger

Do this · Action

Build an automation Browse examples

Examples

Ways Notis can move work from Adrapid to Beaconchain

View example

Look up the validator named in an Adrapid asset brief

Use an Adrapid asset webhook carrying a validator index or public key to retrieve its current Beaconchain record.

View example

Check the Beaconchain epoch referenced by an Adrapid brief

Pass an epoch number or supported epoch keyword from an Adrapid webhook payload to Beaconchain for aggregate metrics.

View example

Add live Ethereum state to an Adrapid staking asset

Use an Adrapid webhook payload containing an ETH or network-state reference to retrieve Beaconchain's latest state and price context.

View example

Review daily validator stats named in an Adrapid report

Read a validator index from an Adrapid export and retrieve its daily balance and duty statistics.

View example

Review network performance for a supplied Adrapid export

On a schedule, analyze the network-performance request and time window contained in the Adrapid export you provide for that run.

View example

Check validator queues for a supplied Adrapid staking brief

At a chosen cadence, use the validator-queue request in a supplied Adrapid export to retrieve activation, exit, and withdrawal sweep metrics.

View example

Track consensus rewards for validators in an Adrapid export

On a schedule, read validator identifiers from a supplied Adrapid export and retrieve Beaconchain consensus rewards over supported windows.

View example

Resolve an ENS reference included in an Adrapid brief

Use an ENS name or Ethereum address present in an Adrapid webhook payload to resolve its counterpart through Beaconchain.

Supported Triggers and Actions

Notis builds workflows that link Adrapid to Beaconchain. A trigger fires from one place; an action lands in another.

Adrapid triggers

Beaconchain actions

Recurring trigger

Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.

TriggerScheduled

Get Node Health

Checks the health status of the explorer service.

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

Get Chart

Retrieves Ethereum Beacon Chain chart images.

ActionInstant

Get Validator

Retrieves details and status information for an Ethereum validator.

ActionInstant

Get Epoch

Retrieves aggregate metrics and status for a Beacon Chain epoch.

ActionInstant

Get ETH1 Deposits by Transaction Hash

Retrieve all validator deposit events for one execution-layer transaction; the result is empty if none exist.

ActionInstant

Get ETH.Store Daily Aggregates

Retrieves daily validator return, reward and balance metrics.

ActionInstant

Get ERC-20 Token Balances

Retrieves a paginated list of ERC-20 token balances for an Ethereum address.

ActionInstant

Get Execution Block

Retrieves execution-layer blocks by number; blocks not found are omitted.

ActionInstant

Trigger Types

Four ways to start an automation.

A trigger is the event that kicks a workflow off. Notis supports four kinds: an event in a connected app, an inbound webhook, a recurring schedule, and soon, your own database.

Integration triggers

Fire when something happens inside a connected app. New Notion page, Stripe charge, Linear issue: any of 1,000+ apps can start a workflow.

New Notion pageStripe chargeCalendar event

Webhook triggers

A unique URL per workflow. Anything that can send an HTTP POST can start an automation, including no-code tools that speak webhooks.

Any HTTP POSTCustom backendIoT event

Works with

ZapierPipedream

Most used

Recurring triggers

Cron-style schedules run a workflow on the clock. Daily standups, hourly syncs, business-hours-only digests: the workhorse of Notis.

Daily · 8:00HourlyWeekdays only

Coming soon

Database triggers

Watch a row, query, or threshold in your own database and fire the moment the data changes. Row inserted, value crosses a limit, query starts matching.

Row insertedValue > limitQuery match

Why AI automation

Classic automation breaks. AI adapts.

Same triggers and actions, smarter middle. AI handles the fuzziness that breaks traditional Zapier-style workflows the moment a field gets renamed.

Classic automationAI automation

Cost

$ · pay per run

$$ · AI models per run

Reliability

Breaks on schema change

Adapts to format changes

Setup

Click 8 dropdowns

Describe it in English

Handles fuzzy

Hard-coded fields only

Reads intent, summarises

Human in loop

Bolted on

Built in · approval inbox

Maintenance

You own every break

Self-heals · we own it

Ease of use

Describe it. Notis builds it.

Skip the visual builder. Tell Notis what you want, in plain English. It writes the workflow, you review and deploy.

You · in the Notis Builder

NEW

“When a row gets added to the Q4 OKRs Notion database and the status is Blocked, send a Telegram message to the owner with a summary of what's blocking, and ping me if there's no reply within 24 hours.”

Notis built this automation:

TriggerRow added to "Q4 OKRs"

Condition✦Status = "Blocked"

AI step✦Summarise the blocker in plain English

ActionDM the row owner with summary

Timeout✦No reply in 24h → ping you

Observability

Watch every run.

Notis Desktop is Mission Control for your AI automations. See every run, replay, edit, or rewind. Set approval gates so Notis pauses before destructive actions.