Connect Airtop to Blocknative

When something happens in Airtop, Notis takes the next step in Blocknative. 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 Airtop to Blocknative

View example

Check Ethereum gas before checkout

Use an Airtop webhook to check current Ethereum gas estimates before completing a time-sensitive checkout.

View example

Get a daily mempool fee brief

Schedule a daily Blocknative gas distribution check and use the result as context for planned on-chain work.

View example

Track a transaction from a browser flow

When an Airtop workflow captures a transaction hash, call Notis to prepare a Blocknative subscription for its state changes.

View example

Review the next five blocks' base fees

Run a scheduled Blocknative base fee outlook to help plan upcoming Ethereum transactions.

View example

Prepare multichain transaction monitoring

Use transaction or address context captured by an Airtop browser flow to prepare Blocknative multichain subscription details.

View example

Configure a mempool watch from browser context

Use details captured by Airtop to prepare Blocknative mempool filters and ABI decoding after a websocket connection is established.

View example

Review supported Blocknative chains

Schedule a supported-chain metadata lookup to keep network discovery in a regular planning routine.

View example

Discover available gas oracles

Ask Blocknative for supported gas oracle metadata when an Airtop browser flow reaches a network planning checkpoint.

View example

Clean up a completed transaction subscription

Use a scheduled cleanup run to prepare an unsubscribe request for an Ethereum transaction hash you no longer need to monitor.

Supported Triggers and Actions

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

Airtop triggers

Blocknative actions

Recurring trigger

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

TriggerScheduled

Configure Mempool Filters

Configures filters and decoding for Ethereum mempool transactions.

ActionInstant

Webhook trigger

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

TriggerInstant

Get Gas Price Distribution

Retrieves the current breakdown of gas prices in the mempool.

ActionInstant

Get Gas Oracles

Lists supported gas oracles by blockchain network.

ActionInstant

Get Gas Prices

Retrieves gas price estimates for likely transaction inclusion.

ActionInstant

Get Supported Chains

Lists supported blockchain networks for gas services.

ActionInstant

Get Base Fee Estimates

Retrieves real-time estimates of Ethereum's base and transaction fees for the next five blocks.

ActionInstant

Subscribe Multichain

Prepares a subscription to real-time transaction or account events across supported chains.

ActionInstant

Subscribe Transaction Hash

Prepares a subscription to status changes for an Ethereum transaction.

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.