Exchange withdrawal (review before running)

What it does

Fills a withdrawal form and stops, so you complete the confirmation screen yourself.

It runs against one profile, through that profile's own proxy and with its own cookies — so the pages load the way that account's owner would see them. It navigates, so give it a profile whose session you are happy to have in use.

The 18 steps

The real tree, read out of the pack the launcher ships. Indentation is nesting: the steps under a loop run once per row, and the ones under a branch run only when the condition above them holds. Every {{…}} is a value filled in at run time — from the row being walked, from a setting on the run, or from the profile itself.

Each of those is one of the step types on the automation reference, with the same fields the editor shows and the same fields an agent is handed over the local API.

What it asks you for

Settings are filled in when the run starts, and every profile can hold its own values — which is how one workflow serves a whole folder of accounts.

phase

Phase · select · required

Run "prepare" first. Complete the confirmation screen yourself. Then run "verify" to record what happened.

exchange_url

Exchange main page · text · required

The exchange's home page — not a deep link. The run opens it first so the session check happens on a page the exchange expects a person to land on.

withdrawal_url

Withdrawal page · text · required

The withdrawal form, as you reach it while signed in.

history_url

Withdrawal history page · text

Used by the "verify" phase only.

amount

Amount · text

Typed into the form and nothing else. A value that is not a positive number stops the run before anything is typed.

amount_selector

Amount field selector · text

Illustrative. Every exchange names this field differently — open the form and check yours before the first real run.

network_selector

Network chooser selector · text

Optional. If the form has a chain picker and you want the run to open it, put its selector here. Leave empty to pick the network yourself.

Loading it

In the launcher, open Automations, choose Load a starter pack, and pick Crypto, bounties and airdrops. Untick anything you do not want. The tables land first, then the workflows, then a project called Crypto Ops that links them together.

What arrives is an ordinary automation row. Open it in the editor, change a step, rename it, delete it — nothing in the app treats it as special afterwards, and loading the pack a second time makes a fresh copy rather than overwriting the one you edited. Tables are the opposite: an existing table of the same name is reused and keeps its rows.