Recipe · Crypto, bounties and airdrops
Wallet hygiene check
Reads the Crypto wallets table and marks every row that is still missing a label, an address, a network or a profile of its own. Opens no page and touches no wallet — the hygiene practice itself is in the runbook.
On this page
What it does
Flags wallet rows that are missing a label, an address, a network or a profile of their own. Opens no page.
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 opens no page at all, which means it can be run against a profile whose session you would rather not disturb.
The 4 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.
loadRowsLoad the wallet rowsLoad Crypto wallets into rowsloopEach walletLoop forEachEach time
evaluateIs this row complete?Run scriptsaveRowsMark the rowSave to Crypto walletson failure: continueEach 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.
The tables it uses
These load with the recipe. A dataset is a typed table your workspace owns — the columns are named and typed up front so the steps can address them, and every one of them is yours to rename, extend or fill from a file afterwards.
Crypto wallets
readswritesOne row per wallet: which profile holds it, what it is for, and whether its entry is complete.
- label
- Label · text
- address
- Address · text
- network
- Network · select · Ethereum | Solana | Bitcoin | BNB Chain | Other
- purpose
- Purpose · text
- profile
- Profile · profile
- status
- Status · select · Complete | Incomplete | Retired
- notes
- Notes · longText
Re-running updates the row it already wrote rather than adding a second one. That is what the match column in the save step is for, and it is the difference between a status check and a table that doubles in size every pass.
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.
The rest of the crypto, bounties and airdrops pack
They load together, share the tables above, and land in one Crypto Ops project.
Airdrop sweep
Walks this profile's airdrop rows and records what each campaign page says.
One profile · Its own proxy and cookies · The Airdrops table
Testnet faucet sweep
Checks each faucet for a payout or a cooldown, pacing itself between rows.
One profile · Its own proxy and cookies · The Testnet faucets table
Exchange balance report
Reads an exchange's portfolio page in this profile's session and files the balances.
One profile · Its own proxy and cookies · The Balances table · 3 settings on the run
Exchange withdrawal (review before running)
Moves money. Read it before the first run — it fills the form and hands the confirmation back to you, and it never types a 2FA code.
One profile · Its own proxy and cookies · 7 settings on the run