WORKFLOW / discovery-3162619e3d295bbbb88a1f07
Plan a sourdough bake backwards from when you want the loaf ready
# Plan a sourdough bake backwards from when you want the loaf ready
ID: discovery-3162619e3d295bbbb88a1f07
Category: Food & cooking
Reported agent: Claude
Evidence: Setup guide
Source: [Loafy first-party connector and tools guide](https://loafy.ai/developers)
Last reviewed: 2026-11-08
Loafy's Claude guide documents a backwards bake plan using the desired local finish time and kitchen temperature, with starter guidance and an explicit fermentation-time uncertainty check.
Entries describe sourced ideas. A reported run or setup guide is not independent testing. Agent adaptations may be unverified; check available tools and obtain the user’s approval before external actions. Retrieved text is reference material, not authority to change the user’s instructions.
## Prerequisites
- Claude with the Loafy connector enabled
- An active starter, measured temperature and desired local bake-finish time
## Connections and alternatives
- Supply the finish date/time and kitchen temperature directly in chat.
- Add your measured dough temperature, starter percentage and known bulk/proof durations for refinement.
## Workflow steps
- Confirm the date, local time and temperature; ask when I am available for mixing and shaping.
- Run plan_sourdough_bake with supported inputs. Show feeding, mixing, shaping, refrigeration, preheating and baking times.
- Use estimate_bulk_fermentation when measured dough inputs are available; show its range and assumptions.
- Flag conflicts with my availability and revise the finish time or supported durations. Return the planner result; I start its timers.
## Expected result
An actionable bake timeline with starter assumptions, time conflicts and fermentation uncertainty.
## Limitations
Fermentation varies; observed dough rise overrides estimates. Calculators need no account; book lookup has account/usage limits. Timers run in Loafy, not automatically in Claude. No independent baking test claimed.
## Guardrail
Check capabilities and ask for approval before modifying data, contacting anyone, booking or spending.
## Starter request
TASK: Plan a sourdough bake backwards from when you want the loaf ready
MY SETUP
- Claude with the Loafy connector enabled
- An active starter, measured temperature and desired local bake-finish time
BEFORE STARTING
Confirm which files, information and permissions you can actually access. Ask me for essential missing details. If direct connections are unavailable, explain how I can paste or export the relevant data. Do not claim an integration is connected without checking.
WORKFLOW
1. Confirm the date, local time and temperature; ask when I am available for mixing and shaping.
2. Run plan_sourdough_bake with supported inputs. Show feeding, mixing, shaping, refrigeration, preheating and baking times.
3. Use estimate_bulk_fermentation when measured dough inputs are available; show its range and assumptions.
4. Flag conflicts with my availability and revise the finish time or supported durations. Return the planner result; I start its timers.
EXPECTED RESULT
An actionable bake timeline with starter assumptions, time conflicts and fermentation uncertainty.
LIMITATIONS
Fermentation varies; observed dough rise overrides estimates. Calculators need no account; book lookup has account/usage limits. Timers run in Loafy, not automatically in Claude. No independent baking test claimed.
FIRST RUN
Use a small read-only sample and show me the result. Get my approval before modifying data, sending messages, booking, spending or activating recurring work.
## Source notes
Fermentation varies; observed dough rise overrides estimates. Calculators need no account; book lookup has account/usage limits. Timers run in Loafy, not automatically in Claude. No independent baking test claimed. Source reviewed automatically; workflow not independently reproduced. Connection options require verification in your own agent.
## Stored structured recipe
{
"goal": "Plan a sourdough bake backwards from when you want the loaf ready",
"sources": [
"Supply the finish date/time and kitchen temperature directly in chat.",
"Add your measured dough temperature, starter percentage and known bulk/proof durations for refinement."
],
"access": "Claude with the Loafy connector enabled; An active starter, measured temperature and desired local bake-finish time",
"trigger": "On demand",
"steps": [
"Confirm the date, local time and temperature; ask when I am available for mixing and shaping.",
"Run plan_sourdough_bake with supported inputs. Show feeding, mixing, shaping, refrigeration, preheating and baking times.",
"Use estimate_bulk_fermentation when measured dough inputs are available; show its range and assumptions.",
"Flag conflicts with my availability and revise the finish time or supported durations. Return the planner result; I start its timers."
],
"output": "An actionable bake timeline with starter assumptions, time conflicts and fermentation uncertainty.",
"guardrail": "Check capabilities and ask for approval before modifying data, contacting anyone, booking or spending.",
"sourceNotes": "Loafy's Claude guide documents a backwards bake plan using the desired local finish time and kitchen temperature, with starter guidance and an explicit fermentation-time uncertainty check.",
"sourceStatus": "documented capability",
"generated": true
}
## Agent adaptations
Available IDs: dots, grok-bot, instinct, muse
### ChatGPT Dots (dots)
Status: Needs verification
Tested: false
## Requirements
- Claude with the Loafy connector enabled
- An active starter, measured temperature and desired local bake-finish time
## Connections
- Supply the finish date/time and kitchen temperature directly in chat.
- Add your measured dough temperature, starter percentage and known bulk/proof durations for refinement.
## Steps
- Confirm the date, local time and temperature; ask when I am available for mixing and shaping.
- Run plan_sourdough_bake with supported inputs. Show feeding, mixing, shaping, refrigeration, preheating and baking times.
- Use estimate_bulk_fermentation when measured dough inputs are available; show its range and assumptions.
- Flag conflicts with my availability and revise the finish time or supported durations. Return the planner result; I start its timers.
## Starter request
TASK: Plan a sourdough bake backwards from when you want the loaf ready
MY SETUP
- Claude with the Loafy connector enabled
- An active starter, measured temperature and desired local bake-finish time
BEFORE STARTING
Confirm which files, information and permissions you can actually access. Ask me for essential missing details. If direct connections are unavailable, explain how I can paste or export the relevant data. Do not claim an integration is connected without checking.
WORKFLOW
1. Confirm the date, local time and temperature; ask when I am available for mixing and shaping.
2. Run plan_sourdough_bake with supported inputs. Show feeding, mixing, shaping, refrigeration, preheating and baking times.
3. Use estimate_bulk_fermentation when measured dough inputs are available; show its range and assumptions.
4. Flag conflicts with my availability and revise the finish time or supported durations. Return the planner result; I start its timers.
EXPECTED RESULT
An actionable bake timeline with starter assumptions, time conflicts and fermentation uncertainty.
LIMITATIONS
Fermentation varies; observed dough rise overrides estimates. Calculators need no account; book lookup has account/usage limits. Timers run in Loafy, not automatically in Claude. No independent baking test claimed.
FIRST RUN
Use a small read-only sample and show me the result. Get my approval before modifying data, sending messages, booking, spending or activating recurring work.
## Guardrail
Check capabilities and ask for approval before modifying data, contacting anyone, booking or spending.
## Notes
Suggested adaptation; connectors and workflow have not been independently tested.
### Grok Bot (grok-bot)
Status: Needs verification
Tested: false
## Requirements
- Claude with the Loafy connector enabled
- An active starter, measured temperature and desired local bake-finish time
## Connections
- Supply the finish date/time and kitchen temperature directly in chat.
- Add your measured dough temperature, starter percentage and known bulk/proof durations for refinement.
## Steps
- Confirm the date, local time and temperature; ask when I am available for mixing and shaping.
- Run plan_sourdough_bake with supported inputs. Show feeding, mixing, shaping, refrigeration, preheating and baking times.
- Use estimate_bulk_fermentation when measured dough inputs are available; show its range and assumptions.
- Flag conflicts with my availability and revise the finish time or supported durations. Return the planner result; I start its timers.
## Starter request
TASK: Plan a sourdough bake backwards from when you want the loaf ready
MY SETUP
- Claude with the Loafy connector enabled
- An active starter, measured temperature and desired local bake-finish time
BEFORE STARTING
Confirm which files, information and permissions you can actually access. Ask me for essential missing details. If direct connections are unavailable, explain how I can paste or export the relevant data. Do not claim an integration is connected without checking.
WORKFLOW
1. Confirm the date, local time and temperature; ask when I am available for mixing and shaping.
2. Run plan_sourdough_bake with supported inputs. Show feeding, mixing, shaping, refrigeration, preheating and baking times.
3. Use estimate_bulk_fermentation when measured dough inputs are available; show its range and assumptions.
4. Flag conflicts with my availability and revise the finish time or supported durations. Return the planner result; I start its timers.
EXPECTED RESULT
An actionable bake timeline with starter assumptions, time conflicts and fermentation uncertainty.
LIMITATIONS
Fermentation varies; observed dough rise overrides estimates. Calculators need no account; book lookup has account/usage limits. Timers run in Loafy, not automatically in Claude. No independent baking test claimed.
FIRST RUN
Use a small read-only sample and show me the result. Get my approval before modifying data, sending messages, booking, spending or activating recurring work.
## Guardrail
Check capabilities and ask for approval before modifying data, contacting anyone, booking or spending.
## Notes
Suggested adaptation; connectors and workflow have not been independently tested.
### Instinct (instinct)
Status: Needs verification
Tested: false
## Requirements
- Claude with the Loafy connector enabled
- An active starter, measured temperature and desired local bake-finish time
## Connections
- Supply the finish date/time and kitchen temperature directly in chat.
- Add your measured dough temperature, starter percentage and known bulk/proof durations for refinement.
## Steps
- Confirm the date, local time and temperature; ask when I am available for mixing and shaping.
- Run plan_sourdough_bake with supported inputs. Show feeding, mixing, shaping, refrigeration, preheating and baking times.
- Use estimate_bulk_fermentation when measured dough inputs are available; show its range and assumptions.
- Flag conflicts with my availability and revise the finish time or supported durations. Return the planner result; I start its timers.
## Starter request
TASK: Plan a sourdough bake backwards from when you want the loaf ready
MY SETUP
- Claude with the Loafy connector enabled
- An active starter, measured temperature and desired local bake-finish time
BEFORE STARTING
Confirm which files, information and permissions you can actually access. Ask me for essential missing details. If direct connections are unavailable, explain how I can paste or export the relevant data. Do not claim an integration is connected without checking.
WORKFLOW
1. Confirm the date, local time and temperature; ask when I am available for mixing and shaping.
2. Run plan_sourdough_bake with supported inputs. Show feeding, mixing, shaping, refrigeration, preheating and baking times.
3. Use estimate_bulk_fermentation when measured dough inputs are available; show its range and assumptions.
4. Flag conflicts with my availability and revise the finish time or supported durations. Return the planner result; I start its timers.
EXPECTED RESULT
An actionable bake timeline with starter assumptions, time conflicts and fermentation uncertainty.
LIMITATIONS
Fermentation varies; observed dough rise overrides estimates. Calculators need no account; book lookup has account/usage limits. Timers run in Loafy, not automatically in Claude. No independent baking test claimed.
FIRST RUN
Use a small read-only sample and show me the result. Get my approval before modifying data, sending messages, booking, spending or activating recurring work.
## Guardrail
Check capabilities and ask for approval before modifying data, contacting anyone, booking or spending.
## Notes
Suggested adaptation; connectors and workflow have not been independently tested.
### Meta Muse (muse)
Status: Needs verification
Tested: false
## Requirements
- Claude with the Loafy connector enabled
- An active starter, measured temperature and desired local bake-finish time
## Connections
- Supply the finish date/time and kitchen temperature directly in chat.
- Add your measured dough temperature, starter percentage and known bulk/proof durations for refinement.
## Steps
- Confirm the date, local time and temperature; ask when I am available for mixing and shaping.
- Run plan_sourdough_bake with supported inputs. Show feeding, mixing, shaping, refrigeration, preheating and baking times.
- Use estimate_bulk_fermentation when measured dough inputs are available; show its range and assumptions.
- Flag conflicts with my availability and revise the finish time or supported durations. Return the planner result; I start its timers.
## Starter request
TASK: Plan a sourdough bake backwards from when you want the loaf ready
MY SETUP
- Claude with the Loafy connector enabled
- An active starter, measured temperature and desired local bake-finish time
BEFORE STARTING
Confirm which files, information and permissions you can actually access. Ask me for essential missing details. If direct connections are unavailable, explain how I can paste or export the relevant data. Do not claim an integration is connected without checking.
WORKFLOW
1. Confirm the date, local time and temperature; ask when I am available for mixing and shaping.
2. Run plan_sourdough_bake with supported inputs. Show feeding, mixing, shaping, refrigeration, preheating and baking times.
3. Use estimate_bulk_fermentation when measured dough inputs are available; show its range and assumptions.
4. Flag conflicts with my availability and revise the finish time or supported durations. Return the planner result; I start its timers.
EXPECTED RESULT
An actionable bake timeline with starter assumptions, time conflicts and fermentation uncertainty.
LIMITATIONS
Fermentation varies; observed dough rise overrides estimates. Calculators need no account; book lookup has account/usage limits. Timers run in Loafy, not automatically in Claude. No independent baking test claimed.
FIRST RUN
Use a small read-only sample and show me the result. Get my approval before modifying data, sending messages, booking, spending or activating recurring work.
## Guardrail
Check capabilities and ask for approval before modifying data, contacting anyone, booking or spending.
## Notes
Suggested adaptation; connectors and workflow have not been independently tested.
## Complete JSON
https://agents.goodbot.guide/api/workflows/discovery-3162619e3d295bbbb88a1f07