Recipe · E-commerce
Store account audit
Reads the Store accounts table and marks every row that is still missing a label, a sign-in address, a region or a profile of its own. Opens no page and signs into nothing — the practice itself is in the runbooks.
On this page
What it does
Flags account rows that are missing a label, an address, a region 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 every store accountLoad Store accounts into rowsloopEach accountLoop forEachEach time
evaluateIs this row complete?Run scriptsaveRowsMark the rowSave to Store accountson 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.
Store accounts
readswritesOne row per seller or store account: which profile holds it, which market it is registered in, and whether its session is still good.
- label
- Label · text
- url
- URL · url
- marketplace
- Marketplace · select · Marketplace | Own store | Wholesale portal | Other
- region
- Region · text
- profile
- Profile · profile
- status
- Status · select · Unchecked | Signed in | Signed out | Needs attention | Unknown page | Incomplete | Retired
- checked_at
- Checked at · datetime
- 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 E-commerce. Untick anything you do not want. The tables land first, then the workflows, then a project called E-commerce 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 e-commerce pack
They load together, share the tables above, and land in one E-commerce Ops project.
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
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