Track pending payment transactions from Notion
Add a pending payment and its hash to Notion, then let Blocknative monitor its Ethereum transaction state.
Trigger
New Page
Triggers when a new page is added to a Notion database.
Action
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.
Why this helps
Pending payments create uncertainty and repeated manual checks when there is no clear status follow-up.
- Turn a pending payment record into a monitoring request.
- Keep the payment follow-up list actionable.
- Reduce repeated status polling.
Setup
Build it in a few focused steps.
- 1Connect Notion and Blocknative to Notis once in the portal.
- 2Create an automation in the portal, or ask Notis conversationally to subscribe to hashes on new pending payment records.
- 3Give Notis a single plain-language instruction describing the payment record and Ethereum hash monitoring outcome.
- 4Select the Notion new database page trigger and choose a channel for run reports.
- 5Test with one real pending payment record containing a transaction hash.
Questions about this workflow
What is needed in the record?
Include a transaction hash and enough context for Notis to recognize that it needs follow-up.
Which Blocknative action is used?
Subscribe Transaction Hash prepares a subscription to transaction state changes for an Ethereum hash.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Blocknative. A trigger fires from one place; an action lands in another.
Notion triggers
Blocknative actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
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.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Gas Price Distribution
Tool to retrieve the current mempool gas price distribution breakdown. use when analyzing gas price trends or preparing fee strategies.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
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.
Comment Created
Triggers when a new comment is created in Notion. Optional `page_id` filter scopes to comments on a specific page. When omitted, fires for any new comment in the workspace the integration has access to. Requires the 'Read comments' capability on the Notion integration. If a connection was authorized before that capability was enabled, the user must re-authorize the connection for comment events to flow.
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.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Get Supported Chains
Tool to retrieve supported chains metadata. use when discovering available networks for blocknative gas services.
Database Created
Triggers when a new Notion database (the container) is created. A database is the post-2025-09-03 container that holds one or more data sources. This trigger fires for the container's creation event (`database.created`), distinct from `NOTION_DATASOURCE_CREATED` which fires when a new data source is added to an existing database. Most customers calling Notion's `POST /v1/databases` (the legacy API) or creating a database via the Notion UI will see this event. Adding a new data source to an existing database fires `data_source.created` instead — use `NOTION_DATASOURCE_CREATED` for that. Notion's payload puts `entity.type: "block"` (the container is a `child_database` block in the content tree) and `entity.id` is the database id.
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.
Data Source Created
Triggers when a new Notion data source is created. Fires workspace-wide. The payload's `data.parent` carries the data source's tree parent (typically the teamspace) for downstream filtering. A single template-based database creation can fire multiple `data_source.created` events at once — one per data source the template instantiates.
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.
Data Source Schema Updated
Triggers when a Notion data source's schema is updated. Fires on column add / remove / rename. Payload includes `data.updated_properties: [{id, name, action}]` so consumers can discriminate the kind of change downstream. Optional `data_source_id` filter scopes to schema changes on a single data source. When omitted, fires for any schema change in the workspace the integration has access to. Note: adding a column also fires `page.properties_updated` once per existing row in the data source. Customers wanting a single structural-change signal should use this trigger.
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.
Connect any two apps with Notis in the middle.
Notion 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.