Connect Addresszen to Blocknative

When something happens in Addresszen, 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 Addresszen to Blocknative

View example

Check gas before confirming an address-sensitive checkout

When a delivery flow sends a webhook, fetch current gas estimates so you can review transaction costs before confirming an address-sensitive order.

View example

Get a scheduled snapshot of mempool gas prices

On a schedule, retrieve Blocknative's current gas price distribution and review the fee landscape before handling address-sensitive deliveries.

View example

Check the next-block base fee outlook for a delivery request

When an external checkout system sends a webhook, retrieve Blocknative's next-five-block base fee and blob base fee predictions for a focused review.

View example

Review available gas oracles across supported chains

Run on a schedule to retrieve Blocknative's gas oracle metadata and keep a current reference for delivery-related transaction planning.

View example

Check supported chains for a delivery transaction request

Use a webhook to retrieve Blocknative's supported chain metadata when a delivery-related request needs a network availability check.

View example

Review gas estimates at your chosen planning time

At a recurring planning time, fetch Blocknative gas price estimates for specified inclusion probabilities and review them alongside Addresszen delivery work.

View example

Prepare multichain monitoring for a delivery-related address

When an HTTP request arrives, generate Blocknative multichain subscription details for an address that needs monitoring across chains.

View example

Prepare a transaction hash subscription for follow-up

When a delivery-related webhook includes an Ethereum transaction hash, prepare Blocknative's transaction state subscription message for follow-up monitoring.

View example

Prepare cleanup for stopped multichain address monitoring

Use an HTTP request to generate Blocknative's multichain unsubscribe operation when monitoring of a delivery-related address should stop.

Supported Triggers and Actions

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

Addresszen 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.