Connect AimTell to Blocknative

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

View example

Check Gas Before an AimTell Campaign

Use a webhook before a time-sensitive push campaign to check current gas prices and give you a concise fee snapshot before you proceed.

View example

Review Mempool Gas Before Subscriber Sends

On a recurring schedule, get Blocknative's current gas price distribution as context for planning upcoming AimTell sends tied to on-chain activity.

View example

Check Base Fee Outlook for a Push Launch

Trigger a Blocknative five-block base fee outlook before an AimTell launch tied to an Ethereum transaction, then review the estimates in a Notis report.

View example

Review Supported Gas Oracles for Campaign Networks

On a schedule, discover Blocknative's supported gas oracles per chain and receive a compact reference for the networks relevant to your AimTell campaign planning.

View example

Confirm Supported Chains Before Launch Planning

Use a pre-launch webhook to retrieve Blocknative's supported chain metadata and check whether your planned network is listed before preparing an AimTell campaign.

View example

Prepare a Multichain Wallet Watch for Campaign Context

When a campaign plan references a wallet, ask Notis to prepare Blocknative multichain subscription details for tracking that address across chains.

View example

Prepare a Transaction Status Watch Before a Push Update

When an AimTell launch process includes an Ethereum transaction hash, have Notis prepare Blocknative's transaction status subscription message for your monitoring setup.

View example

Prepare Transaction Watch Cleanup After a Campaign

Trigger a cleanup step when campaign follow-up is complete to prepare Blocknative's unsubscribe message for an Ethereum transaction hash.

View example

Prepare Multichain Watch Cleanup After Campaign Review

When a campaign review no longer needs address or transaction monitoring, trigger a Notis report with Blocknative multichain unsubscribe details for the supplied chain and id.

Supported Triggers and Actions

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

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