@celigo/api-specs 0.2.49 → 0.2.51

package/dist/export.yml

@@ -8455,60 +8455,33 @@ components:
               type:
                 - string
                 - 'null'
-              description: Salesforce formula expression that filters which events are processed; when omitted (stored as `null`), all events for the object are processed. Evaluated inside Salesforce before events are sent, which is more efficient than filtering in a later flow step. Reference only fields that exist on the monitored object; formula functions such as `ISCHANGED(Status__c)` are supported.
+              description: SOQL WHERE-clause condition that filters which record events the listener processes; when omitted (stored as `null`), every event for the object is processed. The Celigo Salesforce package evaluates it inside Salesforce as `SELECT Id FROM <sObjectType> WHERE (<qualifier>) AND Id IN :ids` before anything is sent, so only fields of the monitored object and SOQL comparison syntax apply — Salesforce formula functions are not part of this grammar. A deleted record is never returned by that query, so a listener with any qualifier receives no delete events; leave it unset when removals must trigger the flow.
               x-celigo-ai-guidance:
                 - |-
-                  ## FIELD BEHAVIOR
-
-                  This field provides server-side filtering:
-
-                  - OPTIONAL: If omitted, all events for the object are processed
-                  - Uses Salesforce formula syntax for filtering
-                  - Evaluated before events are sent to the integration platform
-                  - Can reference any field on the triggering record
+                  Write SOQL WHERE syntax only: `field = value`, `!=`, `<`, `>`, `<=`, `>=`, `LIKE`,
+                  `IN (...)`, `AND` / `OR`, parentheses for grouping, `NOT ( <comparison> )`, and
+                  lowercase `true` / `false` literals.
                 - |-
-                  ## IMPLEMENTATION PATTERNS
-
-                  ### Simple Field Comparisons
-                  ```
-                  "Status__c = 'Approved'"
-                  ```
-                  - Processes events only when specific field values match
-                  - Most efficient filtering approach
-                  - Can use =, !=, >, <, >=, <= operators
-
-                  ### Logical Conditions
-                  ```
-                  "Amount > 1000 AND Status__c = 'New'"
-                  ```
-                  - Combines multiple conditions with AND, OR operators
-                  - Can use parentheses for complex grouping
-                  - Allows precise control over which events trigger the integration
-
-                  ### Formula Functions
-                  ```
-                  "CONTAINS(Description, 'Priority') OR ISCHANGED(Status__c)"
-                  ```
-                  - Uses Salesforce formula functions
-                  - ISCHANGED detects specific field modifications
-                  - ISNEW, ISDELETED detect record lifecycle events
+                  Formula syntax is rejected at save with HTTP 422 `Either whereClause expression ...
+                  is invalid ... unexpected token` — observed for `AND(a, b)` argument lists,
+                  `NOT(field)` on a bare boolean, `NOT(ISNEW())`, `ISDELETED()`, and `ISBLANK(field)`;
+                  uppercase `= FALSE` has been rewritten to `NOT(field)` and rejected the same way.
                 - |-
-                  ## PERFORMANCE IMPACT
-
-                  The qualifier is evaluated in Salesforce before sending events:
-                  - Reduces network traffic and processing
-                  - Lowers integration platform load
-                  - More efficient than filtering in a subsequent flow step
-                  - No additional API calls required
-
-                  IMPORTANT: The qualifier is evaluated using the Salesforce formula engine.
-                  Use valid Salesforce formula syntax and reference only fields that exist
-                  on the primary object being monitored.
+                  The rejection surfaces on a real save (a create, or the user's Accept of a staged
+                  update) — dry-run validation does not run the Salesforce-side check, so a staged
+                  card carrying an invalid qualifier passes dry-run and fails at Accept.
+                - |-
+                  `IsDeleted = true` in a qualifier admits nothing — the query runs against the live
+                  record, which no longer exists after a delete, so any qualified listener stops
+                  receiving deletions. To keep deletes flowing, leave the qualifier unset and drop
+                  unwanted events with the export's output filter, accepting that those events still
+                  start a run.
               examples:
                 - Amount > 1000
                 - Status__c = 'Approved'
                 - LeadSource = 'Web' AND Competitor__c = 'Oracle'
-                - ISCHANGED(Status__c) AND NOT(ISNEW())
+                - IsDirect = false
+                - StageName = 'Won' AND ( NOT ( Unresolved_Errors__c >= 1 ) )
             batchSize:
               type:
                 - integer

package/dist/subscription.yml

@@ -1062,31 +1062,43 @@ components:
                     example: POC – HubSpot → Snowflake
     EndpointUsage:
       type: object
-      description: Endpoint entitlement usage.
+      description: |-
+        Endpoint entitlement usage for the requesting environment. An endpoint is a connected
+        application, not a connection record: connections that share a Celigo-managed application
+        profile (`assistant`) are one endpoint, generic HTTP connections without one are grouped by
+        `baseURI`, databases by `rdbms` engine and host, and other adaptor types by their own connection
+        identity (for example host and port). Each `endpoints[]` entry carries the fields it was grouped by.
       properties:
         numConsumed:
           type: integer
-          description: Number of endpoints currently consumed.
+          description: |-
+            Endpoints counted against the entitlement in the requesting environment, one per distinct
+            endpoint (see `endpoints`). Which flows bring an endpoint into the count follows the account's
+            pricing model, as for `flowUsage.numEnabled`: flows that are enabled on plans that meter
+            enabled resources, flows that ran in the billing period on plans that meter runs.
+          x-celigo-ai-guidance:
+            - Read the account license before interpreting this number. On run-metered plans an endpoint whose flows are enabled but have not run this period is not counted, and one used by a flow that ran even once counts for the whole period; on enabled-metered plans it is counted while any enabled flow references one of its connections, run or not.
+            - Connections referenced by no flow are never counted, and connections to the platform's own API (`api.integrator.io`) never count. On enabled-metered plans a connection referenced only by disabled flows is not counted; on run-metered plans an endpoint used by a flow that ran this period stays counted for the period even if that flow is disabled afterwards.
           example: 8
         endpoints:
           type: array
-          description: Detailed breakdown of endpoints by type.
+          description: The endpoints being counted, each with the connections that roll up into it.
+          x-celigo-ai-guidance:
+            - Two generic HTTP connections to the same application through different base URIs (a second store, a different API version in the path) are two endpoints; to explain an unexpected count, read each entry's `connections` and name the connection that carries the extra endpoint.
           items:
             type: object
             properties:
               type:
                 type: string
                 description: Endpoint adaptor type (e.g., `http`, `rdbms`, `ftp`).
-                x-celigo-ai-guidance:
-                  - Endpoint type/category.
                 example: http
               assistant:
                 type: string
-                description: Application assistant identifier, if the connection uses a Celigo-managed application profile (e.g., `hubspot`, `netsuite`).
+                description: Application assistant identifier, if the connection uses a Celigo-managed application profile (e.g., `hubspot`, `netsuite`). Connections sharing an assistant are one endpoint.
                 example: hubspot
               baseURI:
                 type: string
-                description: Base URI of the connection, if applicable.
+                description: Base URI that identifies this endpoint for generic HTTP connections (those without an `assistant`); connections whose base URIs differ are separate endpoints.
                 example: https://api.hubspot.com
               rdbms:
                 type: object

package/dist/tool.yml

@@ -31411,60 +31411,33 @@ components:
               type:
                 - string
                 - 'null'
-              description: Salesforce formula expression that filters which events are processed; when omitted (stored as `null`), all events for the object are processed. Evaluated inside Salesforce before events are sent, which is more efficient than filtering in a later flow step. Reference only fields that exist on the monitored object; formula functions such as `ISCHANGED(Status__c)` are supported.
+              description: SOQL WHERE-clause condition that filters which record events the listener processes; when omitted (stored as `null`), every event for the object is processed. The Celigo Salesforce package evaluates it inside Salesforce as `SELECT Id FROM <sObjectType> WHERE (<qualifier>) AND Id IN :ids` before anything is sent, so only fields of the monitored object and SOQL comparison syntax apply — Salesforce formula functions are not part of this grammar. A deleted record is never returned by that query, so a listener with any qualifier receives no delete events; leave it unset when removals must trigger the flow.
               x-celigo-ai-guidance:
                 - |-
-                  ## FIELD BEHAVIOR
-
-                  This field provides server-side filtering:
-
-                  - OPTIONAL: If omitted, all events for the object are processed
-                  - Uses Salesforce formula syntax for filtering
-                  - Evaluated before events are sent to the integration platform
-                  - Can reference any field on the triggering record
+                  Write SOQL WHERE syntax only: `field = value`, `!=`, `<`, `>`, `<=`, `>=`, `LIKE`,
+                  `IN (...)`, `AND` / `OR`, parentheses for grouping, `NOT ( <comparison> )`, and
+                  lowercase `true` / `false` literals.
                 - |-
-                  ## IMPLEMENTATION PATTERNS
-
-                  ### Simple Field Comparisons
-                  ```
-                  "Status__c = 'Approved'"
-                  ```
-                  - Processes events only when specific field values match
-                  - Most efficient filtering approach
-                  - Can use =, !=, >, <, >=, <= operators
-
-                  ### Logical Conditions
-                  ```
-                  "Amount > 1000 AND Status__c = 'New'"
-                  ```
-                  - Combines multiple conditions with AND, OR operators
-                  - Can use parentheses for complex grouping
-                  - Allows precise control over which events trigger the integration
-
-                  ### Formula Functions
-                  ```
-                  "CONTAINS(Description, 'Priority') OR ISCHANGED(Status__c)"
-                  ```
-                  - Uses Salesforce formula functions
-                  - ISCHANGED detects specific field modifications
-                  - ISNEW, ISDELETED detect record lifecycle events
+                  Formula syntax is rejected at save with HTTP 422 `Either whereClause expression ...
+                  is invalid ... unexpected token` — observed for `AND(a, b)` argument lists,
+                  `NOT(field)` on a bare boolean, `NOT(ISNEW())`, `ISDELETED()`, and `ISBLANK(field)`;
+                  uppercase `= FALSE` has been rewritten to `NOT(field)` and rejected the same way.
                 - |-
-                  ## PERFORMANCE IMPACT
-
-                  The qualifier is evaluated in Salesforce before sending events:
-                  - Reduces network traffic and processing
-                  - Lowers integration platform load
-                  - More efficient than filtering in a subsequent flow step
-                  - No additional API calls required
-
-                  IMPORTANT: The qualifier is evaluated using the Salesforce formula engine.
-                  Use valid Salesforce formula syntax and reference only fields that exist
-                  on the primary object being monitored.
+                  The rejection surfaces on a real save (a create, or the user's Accept of a staged
+                  update) — dry-run validation does not run the Salesforce-side check, so a staged
+                  card carrying an invalid qualifier passes dry-run and fails at Accept.
+                - |-
+                  `IsDeleted = true` in a qualifier admits nothing — the query runs against the live
+                  record, which no longer exists after a delete, so any qualified listener stops
+                  receiving deletions. To keep deletes flowing, leave the qualifier unset and drop
+                  unwanted events with the export's output filter, accepting that those events still
+                  start a run.
               examples:
                 - Amount > 1000
                 - Status__c = 'Approved'
                 - LeadSource = 'Web' AND Competitor__c = 'Oracle'
-                - ISCHANGED(Status__c) AND NOT(ISNEW())
+                - IsDirect = false
+                - StageName = 'Won' AND ( NOT ( Unresolved_Errors__c >= 1 ) )
             batchSize:
               type:
                 - integer

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@celigo/api-specs",
-  "version": "0.2.49",
+  "version": "0.2.51",
   "private": false,
   "description": "Public OpenAPI bundles (dist/) and the celigo-cli lint schema pack (schemas.json).",
   "keywords": [

package/schemas.json

@@ -1,7 +1,7 @@
 {
 	"provenance": {
 		"repo": "celigo/integrator-api-specs",
-		"iasCommit": "f1b9b36",
+		"iasCommit": "f59fb30",
 		"generatedAt": "2026-09-24"
 	},
 	"roots": {