false, the handler function is not called.
Condition functions are registered with
registerFunction / register_function like any other function. They receive the same event data as the handler and must return a boolean.HTTP trigger condition
The condition function receives the full API request. If it returnsfalse, the engine responds with 422 Unprocessable Entity and the handler function is not called.
- Node / TypeScript
- Python
- Rust
Queue trigger condition
The condition function receives the queue message data. If it returnsfalse, the handler function is not called — no error is raised.
- Node / TypeScript
- Python
- Rust
State trigger condition
The condition receives the full state event, including the event type (created, updated, deleted), scope, key, and both old and new values.
- Node / TypeScript
- Python
- Rust
Key concepts
- Condition functions are registered with
registerFunction/register_functionlike any other function. They receive the same event data as the handler and must returntrueorfalse. - Add
condition_function_idto the trigger config with the condition function’s ID. This key is the same for all trigger types. - When a condition returns
false:- HTTP — the engine responds with
422 Unprocessable Entity; the handler function is not called. - Queue / Cron — the handler function is not called; no error is surfaced.
- State / Stream — the handler function is not called.
- HTTP — the engine responds with
- If a condition function errors, the engine logs the error and does not call the handler (HTTP returns
500 Internal Server Error). - A single condition function can be shared across multiple triggers.