Your first run, start to finish
Pick a template, add a few rows, point it at a pool, press Run — about five minutes, and you can rehearse the whole thing for free first.
In this article (8)
By the end of this you will have generated real output for several items in parallel and seen exactly what it cost. Five minutes, and the only prerequisite is one provider key in a pool.
1. Make sure there is a pool to run through
Open Pools. If it is empty, an admin needs to add a key under API keys and put it in a pool — API keys and Pools walk through it. A pool is just a named group of keys; you will pick it by name and never handle the key itself.
No key yet? You can still do everything below using the built-in free test mode, which produces placeholder output at $0. Read Mock runs for what that does and does not prove.
2. Start from a template
Open Workflows and choose a template from Start from a template. For a first run, Product listing pack (text only, cheap) or Product staging (the flagship image batch) are the two to try. The Builder opens with the whole flow already wired.
3. Fill in a few rows
In Simple view you get a table: one row per item. Type two or three rows — for an image flow, drop a product photo into the row's image cell as well. Three rows is plenty; the point is to watch them run at once.
4. Point the AI step at your pool
Each AI step has a Pool selector. Pick your pool and, if you want, a different model. The template already carries a sensible model and a written instruction — edit the instruction to taste; anything in braces like {product_name} is filled in per row from your table.
5. Rehearse it for nothing
Before spending, open the Data tab on the step (Map view) to see exactly what each item will send, with your values substituted in. This is a $0 dry run of the inputs — the single best habit to build, because it catches an empty column or a mangled prompt before a provider bills you for it.
6. Run it
Press Run. Items go out in parallel across the pool's keys. You will see each row move through queued → running → done, results appearing as they land.
7. Read the results
- Results show inline: text as formatted text, images as a grid with a full-size viewer (← / → to move, Esc to close).
- Keep the good ones, then Regenerate unapproved to redo only the rest — with the cost shown before you confirm. Kept items are never re-paid for.
- Download one, or Download all.
- Every item's estimated cost is visible, and the run total sits in Runs with a lane per key showing how the work was spread.
Then what
- Save the flow (top bar) so it appears in Workflows with its own run, schedule, trigger and share actions.
- Feed it a real list instead of typing rows: batch import from a sheet.
- Have it run itself on a timetable: schedules. Or let another system start it: triggers.
- Before anyone else joins, set a daily spend limit.