Skip to content
Notis

Update Mempool Filters When Monitoring Scope Changes

Keep filter and decoding setup aligned with the latest monitoring requirements recorded in Jira.

Trigger

Updated Issue

Fires when an existing issue is changed in the Jira project you configure — for example its status, assignee, or any other field on the issue is updated. Only issues in that project produce an event. It does not fire on comment activity: adding, editing, or deleting a comment on an issue will not produce an event from this trigger.

Action

Configure Mempool Filters

Tool to configure filters and abi decoding for ethereum mempool transactions. use after establishing a blocknative websocket connection to set up event filters and decoding.

Why this helps

Changes to what the team wants to monitor can leave mempool filters and decoding setup behind.

  • Refresh filter configuration after monitoring requirements change.
  • Keep ABI decoding setup tied to the current issue details.
  • Reduce manual configuration drift during ongoing monitoring work.

Setup

Build it in a few focused steps.

  • 1Connect Jira and Blocknative once in the Notis portal.
  • 2Create an automation in the portal or tell Notis to create it from any channel.
  • 3In one instruction, ask Notis to configure mempool filters and ABI decoding from the updated monitoring request.
  • 4Pick Jira Updated Issue as the trigger and choose where run reports go.
  • 5Establish a Blocknative websocket connection and test with one real updated issue.

Questions about this workflow

Does this modify an existing websocket connection?

The action configures filters and ABI decoding after a websocket connection is established; it does not itself establish that connection.

Do issue comments refresh filters?

No. Comment activity does not fire the Jira Updated Issue event.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

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

Jira triggers

Blocknative actions

Recurring trigger

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

TriggerScheduled

Configure Mempool Filters

Tool to configure filters and abi decoding for ethereum mempool transactions. use after establishing a blocknative websocket connection to set up event filters and decoding.

ActionInstant

Webhook trigger

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

TriggerInstant

Get Gas Price Distribution

Tool to retrieve the current mempool gas price distribution breakdown. use when analyzing gas price trends or preparing fee strategies.

ActionInstant

New Issue

Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.

TriggerInstant

Get Gas Oracles

Tool to retrieve metadata on supported gas oracles per chain. use when you need to dynamically discover all available on-chain gas estimation oracles across networks.

ActionInstant

New Project

Triggered when a new project is added in Jira

TriggerInstant

Get Gas Prices

Tool to fetch gas price estimates for specific inclusion probabilities. use when you need gas price ranges for the next block or next ~10 seconds.

ActionInstant

Updated Issue

Fires when an existing issue is changed in the Jira project you configure — for example its status, assignee, or any other field on the issue is updated. Only issues in that project produce an event. It does not fire on comment activity: adding, editing, or deleting a comment on an issue will not produce an event from this trigger.

TriggerInstant

Get Supported Chains

Tool to retrieve supported chains metadata. use when discovering available networks for blocknative gas services.

ActionInstant

Get Base Fee Estimates

Tool to get real-time predictions for base fee and blob base fee for the next 5 blocks. use when you need both 99% and 50% confidence estimates for upcoming blocks.

ActionInstant

Subscribe Multichain

Tool to generate websocket subscription details for events across multiple chains. use when preparing to track a transaction hash or account address across chains via blocknative multichain sdk.

ActionInstant

Subscribe Transaction Hash

Tool to subscribe to transaction state change events of an ethereum transaction hash. use after establishing a blocknative websocket connection to prepare the subscription message.

ActionInstant

Connect any two apps with Notis in the middle.

Jira and Blocknative, 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 Blocknative.