Recipes

A recipe is a saved extraction configuration — URLs, selectors, steps, and timing — with a name. Once something works, save it and re-run it anytime instead of setting it up again.

📸The Recipes manager listing saved recipes with Run buttonsScreenshot coming soon

Which tools support recipes

Saving and running

• Save: each supported tool has a "Save as recipe" button in its header and in the completion overlay. Name it (a name is pre-suggested from the page title) and optionally describe it.
• Run: open the Recipes manager from the side panel home screen and hit Run — the tool opens prefilled and ready. List Extractor recipes also auto-navigate your tab to the saved source URL.
• Manage: rename, edit the underlying JSON (validated as you type), or delete.

Sharing recipes

Recipes export and import as JSON files — a single recipe or all of them as one bundle. That's the mechanism for sharing a working setup with a teammate or moving it to another machine.

Imports never overwrite: if an imported recipe collides with an existing one, it gets a fresh identity and an "(imported)" suffix instead of replacing anything.

Compatibility

Recipes are versioned. A recipe saved by a newer extension version, or containing actions that can't run, shows an "Outdated" or incompatible badge with the reason instead of a Run button — it stays editable and exportable, so nothing is lost.

Storage

Recipes are stored locally in your browser (no cloud sync); session-specific settings like concurrency are stripped on save, so a shared recipe runs cleanly for anyone.

Recipes vs. cloud scheduling

A recipe re-runs on demand, on your machine. To run an extraction on a schedule without your computer, send it to the Cloud Platform instead.

Related