Recipes

What a recipe is

A recipe is a saved, reusable playbook that runs a proven process for you in one click. Cowork is the freeform surface where you ask Slate to do anything from scratch. A recipe is that same power written down as a repeatable, expert process, so it runs the same way every single time. Recipes are built for the tasks you do over and over, like refreshing a page or finding citation gaps, where you want a consistent result without spelling out the steps each time.

Slate ships with a library of ready-made recipes covering the work SEO and content teams do most, and you can create your own.

What is inside a recipe

Every recipe is transparent and editable. Open one and you will see it is made of a few clear parts:

• Inputs: what you give it to start, such as a page URL or a target keyword.
• Tools: the Slate capabilities it is allowed to use, such as pulling page metrics, scraping a page, or running an AI search.
• Artifacts: what it produces for you at the end.
• Steps: the actual process, written in plain English, the same instructions an expert would follow.
• Trigger (optional): a schedule, so the recipe can run automatically.

‍

Each recipe also has a status (Draft or Published) and its own Run History, so nothing is hidden and every run is on record.

How you use it

Running a recipe

1. Open the recipe library. From Cowork, click Browse all on the "Start with a Recipe" row.
2. Pick a recipe and read its description to confirm it does what you want.
3. Click Run and give it the inputs it asks for, like a page URL or a keyword.
4. Slate works through the steps using your real workspace data, just like Cowork does, and hands back the finished artifacts.
5. Find any past result later in the recipe's Run History.

Building your own

There are three ways to create a recipe:

• Save a Cowork task as a recipe. This is the easiest path. Any time you run something in Cowork that you will want again, save it as a recipe on the spot.
• New Recipe. Build one from scratch.
• Import. Bring an existing recipe in.

Once you have one, refine its steps, set its inputs, choose the tools it may use and the artifacts it should produce, and optionally add a trigger to run it on a schedule. When it is ready, Publish it so your whole team can run it. That is the real value: your best processes stop living in one person's head and become something anyone can run.

When to use what

Cowork, recipes, and workflows are a ladder from flexible to structured. A simple rule:

In short: ask in Cowork, standardize with a recipe, and scale with a workflow.

Getting started

1. Open Browse all and run a built-in recipe, for example Refresh an Existing Page, giving it a real page URL.
2. Review the result, then open the recipe's Run History to see it saved.
3. Think of a task you repeat in Cowork, run it once, and save it as a recipe.
4. Publish that recipe for your team, and add a trigger if it should run on a schedule.

Summary (quick recap)

In short, a recipe is a transparent, one-click playbook: you give it inputs, it uses Slate's tools to work through a set process, and it returns finished artifacts, every time the same way.

The workflow: run a built-in recipe to see the value, save your repeat tasks as recipes, publish the ones your team should share, and reach for a full workflow when you need automation at scale.