Standard Automation Library

W11 draft / unreleased: This library describes reviewable catalog recipes and their V1 baseline. A recipe is cloned into a draft and is not active, enrolled, or provider-connected until the coordinated app integration is completed and an authorized teammate activates it.

V1 catalog

The 14 V1 graph recipes are available from Workflow Templates:

The gallery keeps the V1 order. The five legacy linear template keys remain accepted for existing links and saved drafts, but do not create duplicate gallery cards.

Review a recipe

1. Open Automations > Templates and choose Use template.
2. Review the cloned trigger, subject, conditions, merge fields, and action

order in Guided Editor.

1. Choose Open Visual Builder on a desktop screen when a branch or graph

view is useful.

1. Save the draft and use Preview or Test before activation.

Templates are scoped to the current organization and location context. Cloning creates new graph identifiers and preserves the source template. Requirements, topology, payload bounds, and manage permission are checked again when saving or activating.

V1 baseline and W11 limits

The V1 baseline emphasizes a trigger, customer-safe merge fields, waits, messages, representative tasks, tags, and reply or lifecycle stops. W11 keeps that workflow shape while using immutable revisions, compare-and-swap saves, organization and location scope checks, graph DAG validation, and provider-free testing.

W11 excludes V1 split and recurring-schedule nodes. Guided Editor exposes the 16 bounded action cards described in Actions; a saved card still depends on its matching adapter and executor in the build being reviewed. Templates do not authorize provider sends, call actions, webhooks, or XP awards by themselves. The post-job review recipe's review.left condition is fenced to the enrolled run, and its award_xp action stays skipped until the organization's default-off XP setting is explicitly enabled.