Library
Recipes
21 working automations, grouped by the job they belong to. Each one arrives with the tables it reads and writes, loads into your workspace as ordinary rows, and is yours to edit from the moment it lands.
On this page
What a recipe is
A recipe is an automation we wrote for you: a tree of steps run top to bottom against one profile, through that profile's own proxy and with its own cookies. The steps that touch a page run inside the browser session you already have, so a site sees the identity rather than a harness bolted to it.
Most of them are the same shape, and it is worth learning once. The work list lives in a dataset — a typed table your workspace owns. One parameterised automation loads its own profile's rows, walks them, reads each page, and writes a verdict back into the row it came from. Re-running updates rows rather than adding them, so a table that doubles in size is a bug and not a habit.
Which means the addresses come from your rows, never from us. No recipe on this page contains a link to somebody else's site, an API key, a password or a wallet address, and the launcher's own tests refuse to ship one that does.
The 5 packs
A pack is one vertical's worth of it: three to five automations, the tables they use, and a project that holds them together with the written practice that a step engine cannot do for you.
E-commerce
Storefronts and seller accounts run from separated profiles: an account register that says which profile holds what, a session check, a price sweep and a listing export that files what your own dashboard shows.
Project: E-commerce Ops · 3 tables · 4 recipes
Store session check
Opens this profile's store accounts and records which sessions are still signed in and which are showing a banner.
One profile · Its own proxy and cookies · The Store accounts table
Store account audit
Flags account rows that are missing a label, an address, a region or a profile of their own. Opens no page.
One profile · Opens no page · The Store accounts table
Price watch
Walks this profile's watched product pages and writes back the price and whether the page says it is in stock.
One profile · Its own proxy and cookies · The Product watch table · 2 settings on the run
Listing export
Reads your seller dashboard's listings page in this profile's session and files one row per listing.
One profile · Its own proxy and cookies · The Listings table · 3 settings on the run
Affiliate marketing and media buying
Paid traffic run from separated profiles: an ad account health check, offer and landing-page checks that record where a click really lands, and a spend report read out of the platform's own page.
Project: Media Buying Ops · 4 tables · 4 recipes
Ad account health check
Opens each of this profile's ad accounts and records whether it is active, in review, restricted or just signed out.
One profile · Its own proxy and cookies · The Ad accounts table
Offer link check
Follows each offer link in this profile's session and records where the click actually landed, plus whether the offer is still live.
One profile · Its own proxy and cookies · The Offers table
Landing page check
Loads each landing page through this profile's own proxy, so the page renders the way a visitor in that market sees it. Keeps a full-page shot.
One profile · Its own proxy and cookies · The Landing pages table
Campaign spend report
Reads numbers off a page, not an API. Check the first run against the platform's own total before anyone reports or bills from this table — the default row selector is a guess and every platform draws its report differently.
One profile · Its own proxy and cookies · The Campaign spend table · 3 settings on the run
Web scraping
Collection from a real browser session: a table of sources with their own selectors, a harvest that walks them at a readable pace, a pager for one long list, and a warm-up that opens pages and collects nothing.
Project: Collection · 2 tables · 4 recipes
Target audit
Flags target rows that are missing a label, a URL, a row selector or a profile of their own. Opens no page.
One profile · Opens no page · The Scrape targets table
Warm up a session
Opens this profile's sources and reads them like a person — scroll, pause, scroll back — without collecting anything.
One profile · Its own proxy and cookies · The Scrape targets table
List harvest
Walks this profile's sources, reads each list page with the row's own selector, and files the items.
One profile · Its own proxy and cookies · 2 tables
Paged harvest
Walks one list through its "next page" control, filing every page into the same keyed table.
One profile · Its own proxy and cookies · The Collected items table · 4 settings on the run
Creators
Several channels, each in its own profile: a register of which is which, a session check that says who is still signed in, a queue review that catches the post whose slot passed, and a metrics sweep that reads the platform's own page.
Project: Creator Ops · 3 tables · 4 recipes
Channel session check
Opens this profile's channel rows and records which sessions are still signed in — and which page is asking for a person.
One profile · Its own proxy and cookies · The Channels table
Channel register audit
Flags channel rows that are missing a label, a URL, a platform or a profile of their own. Opens no page.
One profile · Opens no page · The Channels table
Queue review
Marks every queued post whose publish slot passed while it was still only scheduled. Opens no page.
One profile · Opens no page · The Content queue table
Post metrics sweep
Reads a channel's own analytics page in this profile's session and files the per-post numbers.
One profile · Its own proxy and cookies · The Post metrics table · 3 settings on the run
Crypto, bounties and airdrops
Web3 accounts run from separated profiles: airdrop and faucet sweeps, a wallet register, a balance report, and a withdrawal flow that stops and hands the confirmation back to you.
Project: Crypto Ops · 4 tables · 5 recipes
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
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
Loading one
In the launcher, open Automations and choose Load a starter pack. Pick the vertical, untick anything you do not want, and load. The tables are written first, then the automations, then a project linking them — in that order, because an automation finds its table by name at run time and a workflow loaded without its table fails on its first run.
Loading again makes a fresh copy of each automation, the way the built-in example does. Tables are the opposite: a table that already exists under that name is reused and keeps every row it holds, because two tables with one name would leave every workflow in the workspace unable to tell them apart.
The project's runbooks are written to that computer only. Teammates see the project and everything linked into it, but not those notes — which reads as a sync failure if nobody says so first.
Everything that lands is an ordinary row. Rename it, rewrite a step, delete it, put it on the calendar — with the one caveat that a schedule entry fires only while the launcher is open, and a slot it was closed for is marked missed rather than caught up later.
What they do not do
A recipe is a starting point, not a finished integration, and two things about that are worth reading before the first run.
The selectors are guesses.Where a recipe reads a table off somebody else's page, the row selector arrives as a parameter with a default that fits an ordinary table and will not fit every site. Open the page, check it, and expect to set it once. A template that pretended to know a particular platform's markup would be wrong for everyone else and, within a month, for that platform too.
Nothing acts on your behalf at the point that matters. The workflows read pages and file what they find. Where one fills a form that moves money, it stops at the confirmation screen and hands it back to you — no step in any pack types a two-factor code, and that is not a limitation waiting to be lifted.
They also stay inside the rules of whatever you are running. Argus separates accounts you are entitled to hold — a second account a platform permits, separate brands, separate clients, separate regions. It does not make an account you are not allowed to hold into one you are.
Start from one
The packs ship inside the launcher. Nothing to install, nothing to import — open Automations and pick one.