Transactions and batches

Each transaction step executes from one organisation execution account and contains one or more transactions.

Add an ABI-backed call

Choose a saved contract and chain.
Select the canonical function signature.
Fill each argument with a literal or workflow variable.
Enter native value only when the function is payable and the call requires it.
Review the decoded call preview.

Arguments are stored structurally. A variable reference stays a reference until a run renders its concrete value.

Add a transfer

Confirm the asset, destination, chain, and amount unit. The editor displays native currency in human-readable units, while txcast preserves the exact wei value.

Build a batch

Transactions appear in execution order. Reorder them only after considering their state dependencies.

A Safe step can package its batch into the Safe transaction prepared by txcast.
An EOA step produces separately signed transaction requests with indices 0, 1, and so on.

Before saving

Confirm every target is on the selected chain.
Recheck token decimals and native value.
Verify overloaded function signatures.
Ensure variables have compatible types.
Use a separate step when later work should wait for verification of an earlier batch.