docs: use Automation Blueprints instead of Recipes in guide
Rename the cookbook guide from automation-recipes to automation-blueprints so sidebar and copy match the product term. Co-authored-by: Cursor <cursoragent@cursor.com>
This commit is contained in:
+6
-6
@@ -1,16 +1,16 @@
|
||||
---
|
||||
sidebar_position: 15
|
||||
title: "Automation Recipes"
|
||||
description: "Ready-to-use automation recipes — scheduled tasks, GitHub event triggers, API webhooks, and multi-skill workflows"
|
||||
title: "Automation Blueprints"
|
||||
description: "Ready-to-use automation blueprints — scheduled tasks, GitHub event triggers, API webhooks, and multi-skill workflows"
|
||||
---
|
||||
|
||||
# Automation Recipes
|
||||
# Automation Blueprints
|
||||
|
||||
Copy-paste recipes for common automation patterns. Each recipe uses Hermes's built-in [cron scheduler](/user-guide/features/cron) for time-based triggers and [webhook platform](/user-guide/messaging/webhooks) for event-driven triggers.
|
||||
Copy-paste blueprints for common automation patterns. Each blueprint uses Hermes's built-in [cron scheduler](/user-guide/features/cron) for time-based triggers and [webhook platform](/user-guide/messaging/webhooks) for event-driven triggers.
|
||||
|
||||
Every recipe works with **any model** — not locked to a single provider.
|
||||
Every blueprint works with **any model** — not locked to a single provider.
|
||||
|
||||
For parameterized, ready-to-run automations with forms instead of cron syntax, see the [Automation Blueprints Catalog](/reference/automation-blueprints-catalog).
|
||||
For parameterized blueprints with forms instead of cron syntax, see the [Automation Blueprints Catalog](/reference/automation-blueprints-catalog).
|
||||
|
||||
:::tip Three Trigger Types
|
||||
| Trigger | How | Tool |
|
||||
Reference in New Issue
Block a user