Recipes

Quick mental model: If Chat is improvisation, Recipes are sheet music — the same great performance every time, with variables where the details change.

What Recipes Are

A Recipe is a reusable AI workflow template. You write a prompt once with placeholders like {{customer_name}} or {{topic}}, configure how it runs (model, mode, output type), and reuse it whenever the job repeats.

Recipes are ideal when you have done the same kind of AI task more than twice: follow-up emails, weekly reports, ticket triage, blog outlines, code reviews, meeting recaps.

Standard vs Agent Recipes

Agent Recipes declare required toolkits (apps) up front. Users must connect those apps and have Agent mode access before running.

Create a Recipe

1. Go to Recipes in the sidebar.
2. Click + Create Recipe (or Create Recipe).
3. Walk through the editor steps:

Step 1 — Write the prompt

Paste or write your prompt template. Use {{variable_name}} for parts that change each run.

Example:

You are a senior customer success manager.
Using {{customer_notes}} and the attached Support Knowledge Base,
draft a follow-up email for {{customer_name}} in a {{tone}} tone.
Include: brief recap, action items, open questions, one helpful resource.

Use Analyze or Optimize if you want AI help improving the prompt quality.

Step 2 — Variables

Springbase auto-detects {{placeholders}}. For each variable, set:

• Label — what the user sees
• Type — text, textarea, select, toggle, slider, date, image, file, project (Context), meeting, gallery, and more
• Required — whether the user must fill it in

The project type lets users pick a Context at run time. You can also bake specific Contexts into the Recipe so they always attach.

Step 3 — Review metadata

Set:

• Title and description
• Icon and color
• Category and tags
• Visibility — private, unlisted, public, enterprise, or team
• Model — or leave auto-select
• Mode — standard or agent
• Output type — chat, image, video, or audio (most Recipes use chat)

For Agent Recipes, select required toolkits (Gmail, Slack, Notion, etc.).

Step 4 — Done

Use Now opens the variable form and launches Chat with the resolved prompt. You can also Share, Schedule, or Edit from here.

Use a Recipe

1. Find the Recipe on Recipes or from the chat recipe picker.
2. Click Use Recipe.
3. Fill in variables in the form.
4. Submit — Chat opens with settings and prompt applied automatically.

From Chat, you can also save a working prompt as a new Recipe via Save as Recipe (when available on a message).

Variables Reference

Common variable types:

Template syntax in the prompt body: {{variableName}} matching the variable's name field.

Schedule a Recipe

Automate recurring runs from the Recipe card or Automations:

1. Open Schedule on a Recipe.
2. Describe the schedule in plain language or pick a preset (daily 9am, weekdays, etc.).
3. Set timezone and default variable values.
4. Save.

Limits: up to 10 active schedules per user across Recipes and legacy automations. Scheduling requires a paid plan; enterprise policies may gate the automations feature.

Share and Collaborate

Open Share on a Recipe to set:

• Visibility — who can discover or open it
• Collaborators — invite editors or viewers by email
• Fork settings — whether others can copy your Recipe

Premium Recipes can hide the prompt until purchased with credits. Creators set a credit price; buyers unlock full access.

Discovery and Collections

Browse Recipes with filters: category, favorites, trending, agentic-only, and search. Public and community Recipes appear when visibility allows. You can fork a public Recipe to customize a copy (unless the author disabled forking).

Recipe vs Plan Mode

Turn a Plan that worked well into a Recipe when the steps stabilize.

Example Recipes

Support reply draft

Variables: customer_name, ticket_body, tone (select: Professional / Friendly / Urgent)
Attached Context: Support Knowledge Base
Output: ready-to-send email

Weekly exec summary

Variables: week_ending, focus_areas (multiselect)
Attached Context: Company Wiki + Meeting Archive
Output: bullet memo with decisions and risks

Agent: post to Slack

Mode: Agent, required toolkit: Slack
Prompt: "Post a summary of {{meeting_notes}} to #customer-success with action items."

Limits and Billing

• Recipe use consumes credits like Chat (based on model and tokens).
• Agent Recipes add tool-call costs on top of base usage.
• Premium purchase uses credits once per buyer.
• Schedules count toward the 10 active schedule limit.

Troubleshooting

Related Guides

• Chat — where Recipes execute
• Contexts — ground Recipes in your docs
• Agents — Agent mode and connected apps
• Support Assistant — end-to-end support setup
• Artifacts & Canvas — turn Recipe output into editable documents