Wallet Balance Change Monitor to Notion
Periodically checks token balances for a wallet on a given chain; when a change is detected, it appends a row to a Notion database and then stops. Useful for on-chain monitoring and audit logs.
Config
-
Notion API (required): Notion integration credentials. The workflow uses the API key to create records in the specified database.
-
Notion database name (required, default: "Wallet Balance Change Log"): The name of the Notion database where balance-change rows will be created. The database should exist in your Notion workspace; the workflow creates records with fields such as Name, Token, PreviousBalance, NewBalance, Change, Address, Chain, and Timestamp.
-
Wallet address (required): The wallet address to monitor (EVM or Sui depending on chain).
-
Chain (optional, default: sui): The chain to query. Supported values include sui, eth, bsc.
-
Token symbol to monitor (optional, default: SUI): The token to watch. If empty, the first token in the balance list is used. When the balance of this token changes, a record is written to Notion.
-
Check interval (seconds) (optional, default: 300): How often to poll the chain for balances. Minimum 60 seconds.
Logic
- Read the configured address, chain, token symbol, Notion database name, and interval.
- Fetch token balances for the address on the selected chain.
- Determine the balance for the configured token (or the first token if none specified). On the first run, store it as the previous balance and schedule the next run.
- On subsequent runs, compare the current balance to the previous one. If there is a change, create one new record in the Notion database with previous balance, new balance, change amount, address, chain, and timestamp; then the workflow stops.
- If there is no change, schedule the next run after the configured interval and repeat from step 2.
When it stops: After the first balance change is detected and the Notion record is created. Until then, it keeps running at the given interval.
If something fails: Errors are logged and the next run is still scheduled so monitoring continues until a change is detected or the user stops the workflow.
Tip: This executable workflow was automatically generated by SeamFlux Bot. To use it, create an execution and test it with your data to ensure it meets your needs.
Ready to get started?
to run this template or create a scheduled task, and ask AI about detailed node execution steps.
Run Locally — download this workflow as a ZIP or run it via Seamflux CLI in your terminal; use the "Run Locally" button above to choose.
Build a workflow from scratch using AI chat. No complex parameter configuration or flowchart dragging needed.
