Actions
Actions are the most atomic, monolithic tasks in Brixel. They represent a single, well-defined operation such as “Extract Excel Text,” “Send an email,” or “Add a new row.”
Key characteristics
- Single-purpose: one action = one operation.
- Schema-driven: every action has a clear input schema, internal parameters, and an output schema.
- Reusable: actions can be chained inside Tools, referenced by Plan Generators, and used across Builders.
- Standalone execution: an action can be run on its own without being embedded in a larger Tool.
How actions are used
Actions are ideal building blocks:
- Compose them into higher‑level Tools.
- Let a Plan Generator select the right action dynamically based on a user request.
- Run a single action standalone when you need a direct, immediate operation.
tip
You can integrate your own actions by creating a variant of the API call action.