
Two steps on the signed-in Workbench. Numbered steps, Run at the foot, rail on the left.
Start on the Workbench
Drop files, paste a URL, or open:- a Vault asset with
?asset= - a recipe with
?recipe= - a shared community recipe with
?community= - a Queue job with
?job= - a trend with
?trend=
mp4 to gif, ocr, or remove bg all match), and switch between Tiles and List from the toggle on the chip row. List shows each step’s price; tiles without a photograph show the in → out format pair. Your layout choice is remembered per browser.
A skill’s preset (Karaoke maker, Photo to anime, MP4 to GIF) has its own card in the picker. Picking it adds the skill with the option already set, and the Workbench labels the step by its skill and setting — for example Monster restyle · Anime. Format conversion presets have no picker card because Save as is a section that is always on the Workbench rather than a step you add. The language presets (Dub into Spanish, Spanish subtitles, Doc to Spanish) aren’t in the drawers either — search for the language and they appear; the language is also a setting on the skill’s own card.
Search results are ranked the same way the Skills catalogue ranks them: a step you have named beats one where the words sit inside its one-line description. The bench-fit order still comes first, so steps the file on the bench can feed rank above steps it can’t. If nothing matches every word you typed, the picker widens to the closest matches and says so with Nothing matches all of that — closest first.

A generator must be the first step. Voice and music take no file. Image generation can start from a prompt alone.
How steps work
The steps on the Workbench carry one file. Every step is handed what the step above made. Whether a skill can sit under another is computed from the catalogue — not from the drawer they share. A step that hands back pictures can’t feed a skill that needs speech. A document step needs a document. Some skills keep the kind of file they were given (captions, clean-audio, remove-silences). Read that as “the steps still carry a video if you handed them a video.”
Sets
These skills hand back several files:- Clips
- Video splitter
- YouTube thumbnail
- Video Multiplier
- Graphic Multiplier
- Cut it into tiles
- Split a PDF
- PDF to pictures
- Pull the pictures out
Indents
Where the order of the steps doesn’t already make it clear, a step says beside its name what it’s handed: “Makes its own video. Doesn’t use Kling 3 Pro’s” for a generation beside another, “Gets each video from Clips” for a step that runs on every file of a set. A step that takes what the step directly above it made says nothing. When the steps open with more than one generation, a later step can be indented so it runs only on what one generation made, not on every file above it. A picture generation directly under another picture generation can be indented too. Not indented, it makes a picture of its own, so you get two to compare. Indented, it starts from the picture above and your prompt changes it. A video generation under a picture always starts from the picture, so it has no indent button. On the API, send"nested": true (or "indent": true) on that step. See Run a recipe.
Batching
Plan batch sizes are a browser ceiling. Each file is its own run. Credits bound the bill, not the batch control.What runs where
A run that includes a skill, or that generates its own file, runs on the server. It finishes if you close the tab. A browser-only run — compose, resize, adjust, Save as on images — stays in the tab. Poll ceilings: about 6 minutes for an ordinary run, 20 minutes for a set, a slow skill, or a per-minute skill.Credits on the bench
Credits come off before the provider is called and are refunded if that step fails. The plan’s AI steps per run counts only steps that spend credits. Free tools don’t count. An empty prompt is refused before a credit moves, if the skill needs one. Prompts are capped at 2,000 characters. See Credits and plans and Limits.The Run gate
A run that needs more credits than the workspace has opens the Run gate. It leads with **Run once · X** — a [run pass](/getting-started/credits-and-plans#run-pass) sized to the steps on the Workbench, from 2 — beside the top-up slider and a plan. Signed-out visitors get the same offer: pay for the run, or create a free account. The bench is kept in this browser and comes back whole after the trip to Stripe. When the browser can’t keep it — a private window, a full disk, a batch too big — the gate says so before the money moves.Inputs
Write{{name}} in a step’s prompt or an option and the bench grows an Inputs section with a field for it. Fill it in and press Run. Run waits until every required one is filled in. The settings button beside a field sets its label, its kind (text, long text, number, link or choice), a default and whether it has to be filled in. Save as a recipe keeps those settings, and an automation keeps the values. With rows on the bench, a batch fills the same names from its columns instead. See Recipes: Inputs.
Save as a recipe
Save as a recipe keeps the steps (not a backdrop from your own files). Plan caps: Cyclops 3, Minotaur 25, Kraken and Behemoth unlimited. Manage saved recipes at/my-recipes.
Run it on its own
When it runs is the last part of the Workbench: two sections, Trigger and Schedule, that decide what the button under them does.- Neither set, and Schedule on Now, the default: the button is Run, as it always was. Drop files, press it, and the results land beside the steps.
- A time under Schedule: the button is Schedule, and saves an automation that runs on the clock.
- Anything under Trigger: the button is Turn on, and saves an automation that runs when its trigger goes off.
Schedule
- Once, on a day on the calendar, at a time on the clock.
- Hourly: every 1, 2, 3, 4, 6, 8 or 12 hours from midnight, at :00, :15, :30 or :45.
- Daily, weekly on the days you tick, or monthly on a day from the 1st to the 28th, at a time you pick.
- Files on the Workbench are kept in your Vault, in a folder beside where the results go, and every run goes through the same files again — five photos re-made every Monday.
- Nothing on it, and steps that take a file: pick a Vault folder under Takes new files from. Every file that landed in it, or a folder inside it, since the last run is run through the steps, one run each, up to Most files a run. Files an automation made are left alone.
- Nothing on it, and a first step that makes its own file, such as a generator with its prompt written in: nothing is needed.
Trigger
A trigger starts an automation when something happens. Each file it brings is one run through the steps.
Podcast, YouTube and RSS feed are checked every 10 minutes. Turning one on runs what comes out next, not what’s already there. The feed is read when you press Turn on, so a wrong address is said then. YouTube only shows where video downloads are set up. Email only shows where incoming mail is.
Webhook
Pick Webhook under Trigger and press Turn on. The automation gets a private link, shown in its Trigger section with Copy and New link. Post files to it from Zapier, Make, n8n or your own script, and each file is run through the steps, one run each:-F file=@shoe.jpg, one link as {"url": "…"}, or up to 20 as {"urls": […]}. No key is needed: the link is the key, so anyone who has it can run the automation on your credits. Keep it private, and press New link if it gets out; the old one stops working at once. A first step that makes its own file needs nothing posted at all.
Upload page and email
An Upload page gets a link too, to a page anyone can drop files on: send it to a client or a freelancer, and what they drop runs in your workspace. An Email trigger gets its own address; each attachment of mail sent to it runs, and images inline in a signature are left alone. Anyone with the page’s link, or the address, can run the automation on your credits. An upload page asks for the steps’ inputs too: each one you leave blank under Inputs is a field above the drop area, sent with every file. The ones you fill in stay yours and don’t appear on the page. When the first step makes its own file, the page is only its fields and a Send button. Largest file, MB caps what the page takes, up to 100 MB. Put it on your site gives you the code to embed the page on your own site in a frame. Most runs a day is optional: set it to cap what the link starts in any 24 hours. Past it, the link answers429 and runs nothing until older runs fall out of the window. A link also takes 120 posts from one network in 10 minutes.
The files on the Workbench aren’t part of the automation. Test run puts them through the steps now, so you can see what a post will make before you hand the link out. Once it’s on, Send a test file on the automation’s page posts a file of yours to the real link, the way Zapier would, and the run shows up below.
Save to
Save to, under Save as, says where results go besides the results panel.- Vault. Pressing Run, tick Keep results in the Vault to keep this bench’s results, in the folder you pick; your default is under Settings → Workbench. On its own, an automation always keeps every run’s results in its Vault folder, tagged
schedule:and the automation’s name. - Webhook, for an automation: optional. Each run’s outcome, with download links for what it made, is posted to this https address, signed the same way as a run’s own
webhook_url(see Webhooks). A Slack, Discord or Google Chat webhook link gets a chat message instead (how). Each run on the automation’s page says whether the webhook took it, and links to the delivery log on the Keys page.
/automations, with what it made lately and a switch to turn it off. An automation pauses itself, and emails you, when the workspace runs out of credits, when its recipe or file is deleted, or when you leave the workspace. Switch it back on once that is sorted.
Owners, admins and members can set up automations. Viewers see them; guests don’t. Creating, changing, running, pausing and deleting one, and making it a new link, are written to the workspace’s activity.
