Automation Patterns

Patterns are reusable shapes of automation. Claude knows about each one and uses the right pattern automatically when you describe a workflow that fits.

Pattern recognition is Claude's job, not yours. "Add a chatbot that can answer questions about my catalog" triggers the chat-widget pattern; "Pause this until the customer approves" triggers the human-moderation pattern. Each page below explains one pattern so you can follow along when Claude says it's applying one.

Available patterns

• Chat Widget — embedded chat with conversation memory and routing.
• CSV Mapping — batched CSV ingestion with per-row mapping and error reporting.
• Error Handling — retry, suppress, rewrite, or branch when an action fails.
• Execute Automation — chain or fan out from one automation to another.
• Forms — collect human input via a web form, as a trigger or mid-flow.
• Human Moderation — pause for human review before continuing.
• Keyvalue Storage — persistent key/value storage between runs.
• Latches — launch N children in parallel, then block until all finish.
• Scheduling — how automations get kicked off — polling, scheduled triggers, or webhooks.
• Snooze — defer for a specified delay, then resume.
• Subroutines — reusable named sub-flows.
• Two-Way Sync — paired triggers and actions kept in step across systems.