OdyCust/ GUIDE
УКР

Visual automation rules

Edit connected blocks, simulate a saved revision and inspect actual running jobs.

Step by step

  1. Open Automations and choose New rule or an existing rule. Give it a name and choose its event. A saved draft is not active financial authority.
  2. Use Steps to read the rule as if / then / else block rows, or Diagram for the canvas. Both views edit the same graph and preserve the selected block and unsaved values. Switching views does not save, simulate or execute. Reused branches point to their existing step; unreachable blocks remain visible for repair.
  3. Select a block to edit it. Amount conditions use an exact asset and decimal amount; the editor preserves the asset’s smallest units. Combine conditions with All, Any or Not, or configure a time window and timezone.
  4. In an Approval block, set the required count and select specific active members, for example 2 from 5. Add members from the paged list; selected IDs remain saved across pages. Duplicate members and a quorum larger than the selected roster block saving. An empty roster is an inactive draft only. Selection does not prove current approval eligibility: the backend rechecks it at publication and voting.
  5. In Diagram, use the plus control on a connection to insert a block between steps. Condition branches are labelled Yes and No. In either view, select a block to edit its links. Choose a starting block and connect every path to its intended outcome. Diagram arrow keys move focus between blocks.
  6. Correct every highlighted missing field, broken link, unreachable block or cycle before saving. Existing rules create a new revision using the displayed version; a conflict requires reading the current rule again.
  7. For a saved revision, enter a hypothetical asset, amount and UTC time, then simulate. Highlighted blocks show the actual returned trace. Simulation does not sign, send, activate or reserve money.
  8. Under Where rules apply, bind the saved revision to a specific Node, wallet or address. A binding does not publish rules. Select it from the list; older bindings show their own pinned revision.
  9. For withdrawal rules, open the saved graph and review its conditions, selected approvers and target. Publication applies that exact revision, independently of unsaved editor changes. Unsupported blocks and empty approval rosters cannot be published.
  10. For automatic actions, add a separate permit for each exact asset, up to 32. Each permit selects its API client, network, up to 32 distinct recipients, principal and fee caps, lifetime budgets and validity. The same asset cannot appear twice, even for different clients. Date inputs use local time. Every applicable rule still evaluates normally; a token permit never bypasses another asset condition.
  11. Confirm the review and publish with the current platform confirmation. Publication does not start a transfer itself. After a lost reply, read the state or resume the original publication: its identifier and bounds remain unchanged.
  12. Revoking publication or removing a binding requires typed DELETE and current rights. A revoked publication cannot be reactivated; create a new binding for new rules. Already admitted, signed or uncertain operations retain their original recovery path.
  13. Running jobs show their frozen rule revision, current state and retained children. Open an original child transfer to inspect its outcome. Incoming evidence, gas funding and sweep remain distinct stages.
  14. Where permitted, pause or resume an existing job after reviewing the change. Pausing stops new eligible work; it does not erase, cancel or release a signed or uncertain child. A new draft does not replace a running revision.
  15. For a single token + native automation, choose Token + native refill. The draft contains two connected refill blocks. Choose each exact enabled asset, its own donor and one shared recipient/network. Set a minimum and fixed amount to add for every block: for example, token below 10,000 → add 5,000 and native below 0.1 → add 0.1. Select the actual token contract; symbols are not interchangeable. Each rule has separate daily principal/native-fee budgets and a cooldown of 60–86400 seconds. Add or remove blocks for 1–8 distinct assets. Sources must have the same economic owner, checked by the backend.
  16. Save the graph, then enter a hypothetical balance for every refill block and one UTC time under Test a hypothetical balance. Each card shows its own fixed ADD or zero. Time/boolean branches retain their paths; a later deny or hold blocks that path. A threshold no-op does not skip a following rule. Multi-refill graphs cannot use ambiguous amount-condition blocks. Preview reads no RPC, activates nothing and sends no transfer.
  17. Choose Activate saved rule for the saved automation. Select one API client and, in each rule card, its donor HD wallet, exact admitted address and active signer association. Sources and signers are selected separately even when reused. Review all thresholds, fixed amounts, fee limits and published permissions; confirm once for the whole automation. The browser never runs the machine loop.
  18. If activation loses its response, the original terms and automation ID remain saved. Read the job pages and open the matching original result. Explicit continuation uses only the same ID and terms; it cannot replace the runner, source, signer or revision.
  19. Gas funding and fixed refills offer only assets supported by the backend executor and enabled in your organization. Deposit activation uses its own asset list. An older draft can retain another asset for simulation, but it cannot activate a job. Settings are checked again before activation.
  20. Active or paused is the state of the entire automation, not a combined transfer result. Inspect each rule’s original transfer separately. Pausing prevents new work while preserving admitted or uncertain transfers; after a lost pause/resume response, read the original result before any further action.

Related reading

OdyCust · User documentation2026-10-13

Search documentation

Search stays within this guide. It does not request console data.