Run safely
Wallets and transaction safety
Review networks, signing access, and transaction intent before execution.
A blockchain read and a signed transaction have different consequences. Reading a public balance needs an address and RPC access. Sending assets or interacting with a protocol also needs signing authority and can change real balances.
Start with a read#
Confirm the chain, selected network, and RPC settings using a read node before adding a write. Inspect addresses and returned units carefully. A number expressed in a token’s smallest unit is different from its displayed token amount.
Configure the wallet locally#
Use the wallet vault and the app’s authorization flow for signing. Do not paste a private key or recovery phrase into a Variable, Global, HTTP field, Code node, article, or workflow file.
Public addresses can be part of a reusable workflow, but verify that every recipient, owner, mint, contract, and protocol address has the intended role. An imported graph is something to review before granting signing access.
Review the whole path#
Inspect every node downstream of a trigger, including branches and repeated item paths. Check amounts, recipients, slippage or limits where available, and how many times the operation can execute.
A successful node may already have submitted an external action even if a later node fails. Check the resulting transaction or external system before rerunning a write. Retrying the entire workflow can repeat completed actions.
Use Test mode deliberately#
Test mode selects configured blockchain test networks. It is not a simulation of every integration, and it does not turn HTTP requests or messages into pretend actions.
Before enabling a schedule with signing nodes, complete a controlled manual run and review both the workflow output and the resulting chain activity.