Command Claude Code
This page provides detailed documentation on the record.search command used in Cerb automations. It explains how to configure the command to return record dictionaries based on a search query, specifying the syntax for inputs, outputs, and handling different events like simulation, success, and error. Key elements…
Command Claude Code
This page provides detailed information on the "record.update" command in Cerb automations, which is used to update existing records with specified fields. It outlines the syntax and parameters required for the command, including inputs such as record type, record ID, and fields to update. The page also explains…
Command Claude Code
This page provides detailed information on the "record.upsert" command in Cerb automations, which is used to create or update records with specified fields. It outlines the syntax and parameters required for the command, including inputs like recordtype, recordquery, and fields, as well as options to handle events and…
Command Claude Code
This page provides a detailed explanation of the "repeat" command in Cerb automations, which is used to iterate over an array and execute a sequence of commands for each element. It includes a practical example where numbers from 1 to 10 are summed, resulting in a total of 55. The page also outlines the syntax for…
Command Claude Code
This page provides information on the "return" command in Cerb automations, which is used to successfully terminate an automation in the return state and return a dictionary. It includes syntax examples, demonstrating how to use the command to output a message with dynamic content. The specific structure of the…
Command Claude Code
This page provides an overview of the "set" command in Cerb automations, which is used to associate values with placeholder keys. It explains the syntax for setting one or more key/value pairs and demonstrates how sequential keys can reference previously set values. The page also covers the use of dictionaries as…
Command Claude Code
This page covers the "simulate.error" command, which is used inside an "onsimulate" event handler to provide mock error output and trigger the "onerror" event of the enclosing command during automation simulation. It explains the optional output keys, usage examples, and how it relates to the simulation framework in…
Command Claude Code
This page covers the "simulate.success" command, which is used inside an "onsimulate" event handler to provide mock output and trigger the "onsuccess" event of the enclosing command during automation simulation. It explains the optional output keys, usage examples, and how it relates to the simulation framework in…
Command Claude Code
This page provides detailed information on the "storage.delete" command used in Cerb automations to remove a value from long-term storage. It includes a practical example demonstrating how to set, delete, and attempt to retrieve a storage value, resulting in a null output after deletion. The page outlines the syntax…
Command Claude Code
This page provides detailed information on the "storage.get" command used in Cerb automations to retrieve previously saved values from long-term storage. It explains how this key/value system can be shared between different automations and invocations. The page outlines the syntax for using "storage.get," including…
Command Claude Code
This page provides detailed information on the "storage.set" command used in Cerb automations to save a value to long-term storage. It explains how this key/value pair can be shared between different automations and invocations. The page outlines the syntax for using "storage.set," including required inputs such as…
Command Claude Code
This page provides detailed information on the var.expand command used in Cerb automations. It explains how to expand nested keys at a specified dictionary path within automation scripts. The page includes syntax details for the command, outlining required and optional keys such as key and paths, and describes how to…
Command Claude Code
This page provides detailed information on the "var.push" command used in Cerb automations, which appends a value to an array. It includes a practical example demonstrating how to append a value to an existing array and the resulting output. The page outlines the syntax for using "var.push," including required inputs…
Command Claude Code
This page provides detailed information on the "var.set" command used in Cerb automations, which allows setting a value using a specified key path. It includes a practical example demonstrating how to set and retrieve values using key paths, resulting in the output "Kina Halpue." The page outlines the syntax for the…
Command Claude Code
This page provides detailed information on the "var.unset" command used in Cerb automations to remove a placeholder using a specified key path. It includes an example demonstrating how to unset a phone number from a nested data structure. The page outlines the syntax for using "var.unset," including required inputs…
Command Claude Code
This page provides an overview of the "while" command in Cerb automations, which is used to conditionally repeat a sequence of actions, effectively creating controlled loops for various interactions and timers. It includes a sample script demonstrating how to increment a counter until a condition is met. The page…
Command Claude Code
This page describes the llm.router automation command in Cerb, which resolves one or more agent model searches to the list of models that llm.agent:, llm.chat:, and the agentPrompt element already consume. Nothing names a model and nothing names a router record -- the caller states what the work needs as a search, an…
Command Claude Code
This page documents the "records.update" command in Cerb automations, which updates a batch of records of one type in a single action rather than one at a time in a loop. It covers the inputs -- the record type, the list of record IDs, the fields to set, and the optional disableevents toggle -- along with the output…
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: