Nano Trigger icon

Nano Trigger

Receive Nano block confirmations via HTTP callback

Nano Trigger

AI-generated

Summary

Receive Nano block confirmation callbacks through an HTTP POST webhook, apply optional account, subtype, and amount filters, and emit matching confirmations as workflow items. Configure the Nano node to send callbacks to the webhook URL; if a webhook secret is set in the required Nano API credentials, callbacks must include a valid signature.

Inputs

  • Filter Options — Optionally filter by a comma-separated account list, selected block subtypes (send, receive, change, epoch), and minimum or maximum amount in NANO. Amount limits are decimal strings with up to 30 decimal places.
  • Advanced Options — Include block contents (default true), validate the block signature and reported hash (default false), fetch account balance and representative details through RPC (default false), and deduplicate block hashes (default true).

Output shape

One workflow item for each accepted confirmation, containing topic, receivedAt, account, hash, subtype, amountRaw, and amountNano; it may also include block, signatureValid, and accountInfo.

The block field is omitted when Include Block Contents is disabled. Account info is null if its RPC request fails. Invalid block JSON or a configured secret with a missing or invalid callback signature raises an error. Filtered events and duplicate hashes produce no workflow data. Hash deduplication uses node workflow static data and removes entries older than 24 hours when cleanup runs.

Links

Discussion