Recipe · Crypto, bounties and airdrops
Testnet faucet sweep
Opens each faucet in this profile's Testnet faucets rows and records whether it will pay out, is cooling down, or is showing something unexpected. It reads the page; it does not submit a claim.
On this page
What it does
Checks each faucet for a payout or a cooldown, pacing itself between rows.
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 10 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 this profile's faucetsLoad Testnet faucets into rowsevaluateStamp the sweepRun scriptloopEach faucetLoop forEachEach time
setVarStart this row as unknownSet verdictgotoOpen the faucetGo to {{loop.item.url}}on failure: continuewaitWaitevaluateRead the pageRun scripton failure: continuesaveRowsWrite the verdict backSave to Testnet faucetson failure: continuescreenshotScreenshoton failure: continuewaitWaitEach 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.
Testnet faucets
readswritesTestnet faucets and when each one last paid out. Faucets rate-limit hard, so the sweep records a cooldown rather than failing.
- faucet
- Faucet · text
- url
- URL · url
- network
- Network · select · Ethereum | Solana | Bitcoin | BNB Chain | Other
- profile
- Profile · profile
- status
- Status · select · Unchecked | Available | Claimed | Cooling down | Unknown page
- checked_at
- Checked at · datetime
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
Wallet hygiene check
Flags wallet rows that are missing a label, an address, a network or a profile of their own. Opens no page.
One profile · Opens no page · The Crypto wallets 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