refactor: standardize condition_function_id across all trigger types (#1280)

Author: ytallo

docs/content/architecture/trigger-types.mdx

@@ -139,7 +139,7 @@ json!({
 
 **Output**: `ApiResponse` with status_code, body, headers
 
-**Conditions**: Optional. Add `_condition_path` to config with a function ID. The engine invokes it before the handler; if it returns `false`, the handler function is not called. See [Trigger Conditions](#trigger-conditions).
+**Conditions**: Optional. Add `condition_function_id` to config with a function ID. The engine invokes it before the handler; if it returns `false`, the handler function is not called. See [Trigger Conditions](#trigger-conditions).
 
 **Path Parameters**: Extract values from URL
 
@@ -546,7 +546,7 @@ json!({
 
 **Output**: Function result (optional, fire-and-forget pattern supported)
 
-**Conditions**: Optional. Add `_condition_path` to config. See [Trigger Conditions](#trigger-conditions).
+**Conditions**: Optional. Add `condition_function_id` to config. See [Trigger Conditions](#trigger-conditions).
 
 **Multiple Topics**: Register separate triggers for each topic.
 
@@ -604,7 +604,7 @@ json!({
 
 **Output**: Function result
 
-**Conditions**: Optional. Add `_condition_path` to config. See [Trigger Conditions](#trigger-conditions).
+**Conditions**: Optional. Add `condition_function_id` to config. See [Trigger Conditions](#trigger-conditions).
 
 **Cron Expression**: Standard 5-field format (minute hour day month weekday)
 
@@ -906,7 +906,7 @@ Triggers can optionally use a **condition function** to decide whether the handl
 ### How It Works
 
 1. Register a condition function that receives the same input as the handler and returns a boolean.
-2. Add `_condition_path` to the trigger config for http, queue, and cron; use `condition_function_id` for state and stream triggers.
+2. Add `condition_function_id` to the trigger config with the condition function's ID.
 3. When the trigger fires, the engine calls the condition first. Only if it returns truthy does the handler run.
 
 ### Example: HTTP Trigger with Condition
@@ -930,7 +930,7 @@ iii.registerTrigger({
   config: {
     api_path: '/verified',
     http_method: 'POST',
-    _condition_path: conditionFn.id,
+    condition_function_id: conditionFn.id,
   },
 })
 ```
@@ -953,7 +953,7 @@ iii.register_trigger(
     config={
         'api_path': '/verified',
         'http_method': 'POST',
-        '_condition_path': condition_fn.id,
+        'condition_function_id': condition_fn.id,
     },
 )
 ```
@@ -972,7 +972,7 @@ iii.register_function("api::verifiedOnly", |_req: Value| async move {
 iii.register_trigger("http", "api::verifiedOnly", json!({
     "api_path": "/verified",
     "http_method": "POST",
-    "_condition_path": "conditions::requireVerified"
+    "condition_function_id": "conditions::requireVerified"
 }))?;
 ```
 </Tab>
@@ -998,7 +998,7 @@ iii.registerTrigger({
   function_id: fn.id,
   config: {
     topic: 'order.placed',
-    _condition_path: conditionFn.id,
+    condition_function_id: conditionFn.id,
   },
 })
 ```
@@ -1021,7 +1021,7 @@ iii.register_trigger(
     function_id=fn.id,
     config={
         'topic': 'order.placed',
-        '_condition_path': condition_fn.id,
+        'condition_function_id': condition_fn.id,
     },
 )
 ```
@@ -1040,7 +1040,7 @@ iii.register_function("orders::processHighValue", |order: Value| async move {
 
 iii.register_trigger("queue", "orders::processHighValue", json!({
     "topic": "order.placed",
-    "_condition_path": "conditions::highValue"
+    "condition_function_id": "conditions::highValue"
 }))?;
 ```
 </Tab>
@@ -1115,15 +1115,9 @@ iii.register_trigger("state", "state::onProfileUpdate", json!({
 </Tab>
 </Tabs>
 
-### Config Keys by Trigger Type
+### Config Key
 
-| Trigger Type | Condition Config Key |
-|--------------|----------------------|
-| http | `_condition_path` |
-| queue | `_condition_path` |
-| cron | `_condition_path` |
-| stream | `condition_function_id` |
-| state | `condition_function_id` |
+All trigger types use `condition_function_id` in the trigger config to reference the condition function.
 
 ## Trigger Lifecycle
 

docs/content/examples/conditions.mdx

@@ -51,7 +51,7 @@ iii.registerTrigger({
   config: {
     api_path: 'orders/premium',
     http_method: 'POST',
-    _condition_path: 'conditions::is_premium',
+    condition_function_id: 'conditions::is_premium',
   },
 })
 ```
@@ -88,7 +88,7 @@ iii.register_trigger(
     config={
         "api_path": "orders/premium",
         "http_method": "POST",
-        "_condition_path": "conditions::is_premium",
+        "condition_function_id": "conditions::is_premium",
     },
 )
 ```
@@ -120,7 +120,7 @@ async fn main() -> Result<(), Box<dyn std::error::Error>> {
     iii.register_trigger("http", "orders::premium", json!({
         "api_path": "orders/premium",
         "http_method": "POST",
-        "_condition_path": "conditions::is_premium",
+        "condition_function_id": "conditions::is_premium",
     }))?;
 
     loop { tokio::time::sleep(std::time::Duration::from_secs(60)).await; }
@@ -161,7 +161,7 @@ iii.registerFunction(
 iii.registerTrigger({
   type: 'queue',
   function_id: 'orders::high_value',
-  config: { topic: 'order.created', _condition_path: 'conditions::is_high_value' },
+  config: { topic: 'order.created', condition_function_id: 'conditions::is_high_value' },
 })
 ```
 
@@ -200,7 +200,7 @@ iii.register_function("orders::high_value", lambda data: orders_high_value(data,
 iii.register_trigger(
     type="queue",
     function_id="orders::high_value",
-    config={"topic": "order.created", "_condition_path": "conditions::is_high_value"},
+    config={"topic": "order.created", "condition_function_id": "conditions::is_high_value"},
 )
 ```
 
@@ -228,7 +228,7 @@ iii.register_function("orders::high_value", |input| async move {
 
 iii.register_trigger("queue", "orders::high_value", json!({
     "topic": "order.created",
-    "_condition_path": "conditions::is_high_value",
+    "condition_function_id": "conditions::is_high_value",
 }))?;
 ```
 
@@ -237,7 +237,7 @@ iii.register_trigger("queue", "orders::high_value", json!({
 
 ## State trigger condition
 
-State and stream triggers use `condition_function_id` in the config instead of `_condition_path`. The condition receives the full state event, including the event type (`created`, `updated`, `deleted`), scope, key, and both old and new values.
+The condition receives the full state event, including the event type (`created`, `updated`, `deleted`), scope, key, and both old and new values.
 
 <Tabs groupId="language" persist items={['Node / TypeScript', 'Python', 'Rust']}>
   <Tab value="Node / TypeScript">
@@ -319,8 +319,7 @@ iii.register_trigger("state", "orders::on_update", json!({
 ## Key concepts
 
 - Condition functions are registered with `registerFunction` / `register_function` like any other function. They receive the same event data as the handler and must return `true` or `false`.
-- For HTTP, queue, and cron triggers, add `_condition_path` to the trigger config with the condition function's ID.
-- For state and stream triggers, use `condition_function_id` in the trigger config instead.
+- Add `condition_function_id` to 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.

docs/content/how-to/use-trigger-conditions.mdx

@@ -101,12 +101,6 @@ async fn main() -> Result<(), Box<dyn std::error::Error>> {
 
 Create a Trigger and specify its condition with `condition_function_id`.
 
-<Callout title="Condition differences" type="info">
-Use `_condition_path` for `http`, `queue`, and `cron`. Use `condition_function_id` for `state` and `stream`. This disparity will be fixed soon.
-</Callout>
-
-{/* TODO: Replace `_condition_path` with `condition_function_id` once SDKs are updated. */}
-
 Example (`state` trigger):
 
 <Tabs groupId="language" persist items={["Node / TypeScript", "Python", "Rust"]}>

docs/content/modules/module-cron.mdx

@@ -88,13 +88,13 @@ This Module adds a new Trigger Type: `cron`.
     ```
 
   </ResponseField>
-  <ResponseField name="_condition_path" type="string">
+  <ResponseField name="condition_function_id" type="string">
     Function ID for conditional execution. The engine invokes it with the cron event; if it returns `false`, the handler function is not called.
   </ResponseField>
 </Expandable>
 
 <Expandable title="Trigger Event Payload">
-  The following fields are passed to the handler function (and to `_condition_path` if set) each time the trigger fires.
+  The following fields are passed to the handler function (and to `condition_function_id` if set) each time the trigger fires.
 
   <ResponseField name="trigger" type="string">
     Always `"cron"`.

docs/content/modules/module-http.mdx

@@ -90,7 +90,7 @@ This module adds a new Trigger Type: `http`.
   <ResponseField name="http_method" type="string" required>
     The HTTP method of the API.
   </ResponseField>
-  <ResponseField name="_condition_path" type="string">
+  <ResponseField name="condition_function_id" type="string">
     Function ID for conditional execution. The engine invokes it with the request; if it returns `false`, the handler function is not called.
   </ResponseField>
 </Expandable>

docs/content/modules/module-queue.mdx

@@ -145,7 +145,7 @@ This Module adds a new Trigger Type: `queue`.
   <ResponseField name="topic" type="string" required>
     The topic to subscribe to. The function will be invoked whenever a message is enqueued to this topic.
   </ResponseField>
-  <ResponseField name="_condition_path" type="string">
+  <ResponseField name="condition_function_id" type="string">
     Function ID for conditional execution. The engine invokes it with the message payload; if it returns `false`, the handler function is not called.
   </ResponseField>
   <ResponseField name="queue" type="object">

engine/src/modules/cron/cron.rs

@@ -108,7 +108,7 @@ impl TriggerRegistrator for CronCoreModule {
 
             let condition_function_id = trigger
                 .config
-                .get("_condition_path")
+                .get("condition_function_id")
                 .and_then(|v| v.as_str())
                 .map(|v| v.to_string());
 
@@ -324,15 +324,15 @@ mod tests {
     }
 
     #[tokio::test]
-    async fn register_trigger_with_condition_path() {
+    async fn register_trigger_with_condition_function_id() {
         let (_engine, module) = setup_cron_module();
         let trigger = crate::trigger::Trigger {
             id: "cron-trig-cond".to_string(),
             trigger_type: "cron".to_string(),
             function_id: "test::handler".to_string(),
             config: json!({
                 "expression": "0 30 * * * *",
-                "_condition_path": "test::condition_fn"
+                "condition_function_id": "test::condition_fn"
             }),
             worker_id: None,
         };

engine/src/modules/queue/queue.rs

@@ -107,7 +107,7 @@ impl TriggerRegistrator for QueueCoreModule {
             if !topic.is_empty() {
                 let condition_function_id = trigger
                     .config
-                    .get("_condition_path")
+                    .get("condition_function_id")
                     .and_then(|v| v.as_str())
                     .map(|v| v.to_string());
 
@@ -574,15 +574,15 @@ mod tests {
     }
 
     #[tokio::test]
-    async fn register_trigger_with_condition_path_subscribes() {
+    async fn register_trigger_with_condition_function_id_subscribes() {
         let (_engine, module, adapter) = setup_queue_module();
         let trigger = crate::trigger::Trigger {
             id: "trig-cond".to_string(),
             trigger_type: "queue".to_string(),
             function_id: "test::handler".to_string(),
             config: json!({
                 "topic": "conditioned-topic",
-                "_condition_path": "test::condition_fn"
+                "condition_function_id": "test::condition_fn"
             }),
             worker_id: None,
         };

engine/src/modules/rest_api/api_core.rs

@@ -396,7 +396,7 @@ impl TriggerRegistrator for RestApiCoreModule {
 
             let condition_function_id = trigger
                 .config
-                .get("_condition_path")
+                .get("condition_function_id")
                 .and_then(|v| v.as_str())
                 .map(|v| v.to_string());
 
@@ -933,7 +933,7 @@ mod tests {
             config: json!({
                 "api_path": "users/:id",
                 "http_method": "post",
-                "_condition_path": "fn::condition"
+                "condition_function_id": "fn::condition"
             }),
             worker_id: None,
         };

frameworks/motia/motia-js/packages/motia/__tests__/integration/queue.integration.test.ts

@@ -143,7 +143,7 @@ describe('queue integration', () => {
       function_id: functionId,
       config: {
         topic,
-        _condition_path: conditionPath,
+        condition_function_id: conditionPath,
       },
     })