@celigo/api-specs 0.2.170 → 0.2.172

package/dist/ai-agent.yml

@@ -1232,7 +1232,7 @@ components:
                       x-enumDescriptions:
                         text: Free-form text response from the model.
                         json_schema: Structured JSON output conforming to a defined schema.
-                        blob: Binary data output for non-text content.
+                        blob: Image generation — the run calls the image generation tool and returns the stored image's `blobKey`, not `_text` or `_json`.
                       default: text
                       description: Output format type.
                     schemaMode:
@@ -1454,11 +1454,6 @@ components:
                               an object without a non-empty name fails with a
                               missing-required-field error. String entries are the
                               legacy form and stay valid.
-                      allowedPrompts:
-                        type: array
-                        description: Specific prompts to allow from the MCP server (used for MCP prompt entries; all if omitted).
-                        items:
-                          type: string
                   tool:
                     type: object
                     description: |
@@ -1601,7 +1596,7 @@ components:
                   x-enumDescriptions:
                     text: Free-form text response from the model.
                     json_schema: Structured JSON output conforming to a defined schema.
-                    blob: Binary data output for non-text content.
+                    blob: Image generation — the run returns the stored image's `blobKey`, not `_text` or `_json`.
                   default: text
                 schemaMode:
                   type: string
@@ -1770,11 +1765,6 @@ components:
                                       description: Display description shown for the tool.
                                   required:
                                     - name
-                              allowedPrompts:
-                                type: array
-                                description: Specific prompts to allow from the MCP server (used for MCP prompt entries; all if omitted).
-                                items:
-                                  type: string
                           tool:
                             type: object
                             description: Reference to a Celigo Tool resource, used when type is "tool".
@@ -2334,7 +2324,11 @@ components:
 
             **Simple Types (direct value mapping)**
             - `string`: Text values, converts other types to string representation
-            - `number`: Numeric values, attempts conversion from strings
+            - `number`: Numeric values. Converts a numeric string (`"24"` → `24`,
+              `"007"` → `7`) and leaves the field out for an empty string; a value
+              holding letters or a thousands separator (`"1,250.00"`) fails the
+              record with `non_parsable_string` (`<generate>: String contains alpha
+              characters`)
             - `boolean`: True/false values, converts truthy/falsy values
 
             Dates are represented as strings — use `string` for date fields and
@@ -2377,8 +2371,14 @@ components:
             - |-
               Missing `dataType` is rejected at save with validation error
               `[mandatory_destination_datatype] Destination datatype is a
-              required field.` When in doubt, use `"string"` — it accepts
-              any source value and the runtime will coerce it.
+              required field.`
+            - |-
+              Give each row the type the destination field expects; `"string"` is
+              not a safe default. It accepts any source value, but sends a numeric
+              source as text (`"24"`), which a destination that checks JSON types
+              refuses. Map numeric destination fields as `number`, which fails a
+              record (`non_parsable_string`) only when the value holds letters or a
+              thousands separator.
           enum:
             - string
             - number
@@ -2390,7 +2390,7 @@ components:
             - objectarray
           x-enumDescriptions:
             string: Text values; converts other types to their string representation.
-            number: Numeric values; attempts conversion from strings.
+            number: Numeric values; converts numeric strings, and fails the record (`non_parsable_string`) on letters or a thousands separator.
             boolean: True/false values; converts truthy/falsy values.
             object: Nested object built from child `mappings`, or copied whole with `extract` (not both).
             stringarray: Array of string values.
@@ -3418,7 +3418,11 @@ components:
 
               **Simple Types (direct value mapping)**
               - `string`: Text values, converts other types to string representation
-              - `number`: Numeric values, attempts conversion from strings
+              - `number`: Numeric values. Converts a numeric string (`"24"` → `24`,
+                `"007"` → `7`) and leaves the field out for an empty string; a value
+                holding letters or a thousands separator (`"1,250.00"`) fails the
+                record with `non_parsable_string` (`<generate>: String contains alpha
+                characters`)
               - `boolean`: True/false values, converts truthy/falsy values
 
               Dates are represented as strings — use `string` for date fields and
@@ -3461,8 +3465,14 @@ components:
               - |-
                 Missing `dataType` is rejected at save with validation error
                 `[mandatory_destination_datatype] Destination datatype is a
-                required field.` When in doubt, use `"string"` — it accepts
-                any source value and the runtime will coerce it.
+                required field.`
+              - |-
+                Give each row the type the destination field expects; `"string"` is
+                not a safe default. It accepts any source value, but sends a numeric
+                source as text (`"24"`), which a destination that checks JSON types
+                refuses. Map numeric destination fields as `number`, which fails a
+                record (`non_parsable_string`) only when the value holds letters or a
+                thousands separator.
             enum:
               - string
               - number
@@ -3474,7 +3484,7 @@ components:
               - objectarray
             x-enumDescriptions:
               string: Text values; converts other types to their string representation.
-              number: Numeric values; attempts conversion from strings.
+              number: Numeric values; converts numeric strings, and fails the record (`non_parsable_string`) on letters or a thousands separator.
               boolean: True/false values; converts truthy/falsy values.
               object: Nested object built from child `mappings`, or copied whole with `extract` (not both).
               stringarray: Array of string values.
@@ -4398,192 +4408,6 @@ components:
                   - lookupName
               - required:
                   - hardCodedValue
-    ResponseMapping:
-      type: object
-      description: |
-        Merges fields from a step's response back onto the in-flight record so
-        downstream steps can read them. Applies to both lookup steps
-        (`type: "export"`) and import steps (`type: "import"`); without it, the
-        step's response is discarded after the call.
-
-        `fields` and `lists` are plain arrays — exactly the shape GET returns.
-
-        Extract paths do NOT read the raw application response — the platform
-        wraps every response in a canonical per-record envelope first, and
-        extracts evaluate against that envelope:
-
-        - **Lookup steps**: `{"statusCode": 200, "data": [<result records>],
-          "errors": []}` — `data` holds the records the lookup step returns,
-          AFTER the export's own `transform` and output `filter` have run, so
-          extracts must start from it and name transformed fields by their
-          transformed name: `data[0].name` copies a field of the first result,
-          `data` copies the whole result array. A bare result-record field name
-          (e.g. `name`) resolves to nothing and merges nothing, and so does the
-          raw response path a transform consumed. A lookup that groups its
-          results returns each group as an array inside `data`
-          (`"data": [[<row>, <row>]]`): `data[0][0].name` (or `data.0.0.name`)
-          reads the first row of the first group, and `data[0]` copies the group.
-        - **Import steps**: `{"id": "<destination record id>", "statusCode": 200,
-          "ignored": false, "errors": [], "_json": <raw destination response>,
-          ...<response body fields flattened at the root>}` — use `id` for the
-          destination-assigned id and `_json.<path>` (or the flattened
-          `<path>`) for fields inside the destination's response body. The full
-          envelope (including `id`) is present on real runs and in flow-builder
-          previews; flow TEST runs never execute imports, and their envelope is
-          built from the import's saved `mockResponse`, or from the placeholder
-          `{"id": "1234567890", "mockResponse": "replace me"}` (numbered
-          `1234567890-1`, `1234567890-2`, … when a page holds several records)
-          — an `extract: "id"` in a test run merges that mock id, never a
-          destination record id.
-
-        An `extract` may also be a Handlebars expression. It evaluates against
-        the same envelope as a plain path, so every path inside `{{ }}` starts
-        where the plain paths start — `{{data.0.name}}`,
-        `{{#compare data.0.count "==" 1}}yes{{else}}no{{/compare}}`,
-        `{{#if data.length}}found{{/if}}` on a lookup; `{{_json.order.id}}` or
-        `{{id}}` on an import. Index arrays with dots inside Handlebars
-        (`data.0.name` or `data.[0].name`; `data[0].name` renders nothing), and
-        expect a string result (`"1"`, `"false"`). There is no `record` object in
-        this context: `{{record.<anything>}}` renders nothing. Prefer a plain
-        path when the value is simply copied.
-      x-celigo-ai-guidance:
-        - |-
-          Handlebars is allowed in `extract` but only rooted at the envelope —
-          `{{data.0.x}}` on a lookup, `{{_json.x}}` / `{{id}}` on an import. The
-          `record.` root belongs to import-mapping templates; here every
-          `{{record.…}}` form renders nothing, silently, and `{{data[0].x}}`
-          (bracket index inside Handlebars) renders nothing too. Use Handlebars
-          only for a derived value (a flag, a concatenation); copy values with a
-          plain path.
-        - |-
-          A lookup's `data[]` is the step's output after its `transform` and
-          `filter`, so author extracts against the transformed records — never
-          against the raw response the transform consumed, and never against a
-          saved `mockOutput` as stored (it is the raw response; the transform
-          runs on top of it in a test run).
-        - |-
-          Send `fields` and `lists` as bare arrays, exactly as GET returns them.
-          Never wrap either in an object (e.g. `"fields": {"type": [...]}`): the
-          API does not reject that shape — it returns 200 and silently persists
-          `fields: [null]` / `lists: [{"fields": []}]`, erasing the step's
-          response mappings.
-        - |-
-          responseMapping is fully replaced on PUT: omitting it resets the step
-          to empty `{"fields": [], "lists": []}`. Always send the complete
-          intended mapping for every step.
-        - |-
-          To carry several lookup results onto the record, use `extract: "data"`
-          (the whole result array) or a `lists` entry whose extracts use
-          `data[*].x` — never `data[*].x` in `fields[].extract`, which merges
-          nothing: the record simply never gains the field.
-      examples:
-        - fields:
-            - extract: id
-              generate: ContactId
-          lists: []
-        - fields:
-            - extract: data[0].customer.name
-              generate: customerName
-          lists:
-            - generate: matchedOrders
-              fields:
-                - extract: data[*].id
-                  generate: orderId
-                - extract: data[*].total
-                  generate: amount
-      properties:
-        fields:
-          type: array
-          description: |
-            Field mappings that copy individual values from the response
-            envelope onto the in-flight record.
-          items:
-            type: object
-            properties:
-              extract:
-                type: string
-                x-celigo-agent:
-                  - handlebars
-                description: |
-                  Path within the canonical response envelope to copy the value
-                  from, or a Handlebars expression over that same envelope. For
-                  lookup steps, paths start from the envelope's `data` array
-                  (`data[0].x` and `data.0.x` are equivalent; `data` alone
-                  copies every result) — a lookup result field written without
-                  the `data` prefix resolves to nothing. For import steps, use
-                  the envelope fields `id`, `statusCode`, `ignored`, `_json.<path>`
-                  for the raw response body, or the body field itself at the
-                  envelope root (`orderNumber` and `_json.orderNumber` read the
-                  same value). A `[*]` wildcard is not honored here — `data[*].x`
-                  merges nothing; iterate arrays with `lists` instead. Inside
-                  Handlebars, index with dots (`{{data.0.x}}`, never
-                  `{{data[0].x}}`) and never use a `record.` root.
-                examples:
-                  - data[0].customer.name
-                  - data.0.fields.Product Name
-                  - data
-                  - id
-                  - _json.orderNumber
-                  - '{{#if data.length}}found{{else}}missing{{/if}}'
-              generate:
-                type: string
-                description: |
-                  Field path on the in-flight record where the extracted value
-                  is stored, using dot notation for nesting. Downstream steps
-                  read the value at this path.
-                examples:
-                  - customerName
-                  - supplierDetails.supplierName
-                  - netsuite_order_id
-        lists:
-          type: array
-          description: |
-            Array mappings that build a target array on the in-flight record
-            from an array inside the response envelope — one output item per
-            element of the array the item extracts mark with `[*]` (`data[*].x`
-            for lookups, `_json.<arrayPath>[*].x` for imports); an empty source
-            array yields an empty target array. Not needed for one-to-many
-            (fan-out) merge-back, which uses plain field mappings.
-          items:
-            type: object
-            properties:
-              generate:
-                type: string
-                description: |
-                  Array field created on the in-flight record to hold the
-                  mapped items.
-                examples:
-                  - orderItems
-                  - addresses
-                  - contacts
-              fields:
-                type: array
-                description: |
-                  Field mappings applied to each item of the source array to
-                  produce the corresponding target-array item.
-                items:
-                  type: object
-                  properties:
-                    extract:
-                      type: string
-                      description: |
-                        Full envelope path to the source value, with `[*]`
-                        marking the array to iterate — `data[*].productId` for a
-                        lookup, `_json.items[*].sku` for an import. A path without
-                        `[*]` (e.g. `statusCode`) repeats the same envelope value
-                        on every item; an item-relative name (`productId`)
-                        resolves to nothing and produces empty objects.
-                      examples:
-                        - data[*].productId
-                        - data[*].quantity
-                        - _json.items[*].sku
-                    generate:
-                      type: string
-                      description: Target field within each mapped array item.
-                      examples:
-                        - itemId
-                        - qty
-                        - unitPrice
     Filter:
       type: object
       description: |
@@ -4723,15 +4547,30 @@ components:
                 - `"lessthan"`: Value is less than specified value (is less than)
                 - `"lessthanequals"`: Value is less than or equal to specified value (is less than or equals)
                 - `"startswith"`: String starts with specified prefix (starts with)
+                - `"notstartswith"`: String does not start with specified prefix (does not start with)
                 - `"endswith"`: String ends with specified suffix (ends with)
+                - `"notendswith"`: String does not end with specified suffix (does not end with)
                 - `"contains"`: String contains specified substring (contains)
                 - `"doesnotcontain"`: String does not contain specified substring (does not contain)
                 - `"empty"`: Field is missing or empty (is empty)
                 - `"notempty"`: Field contains a value (is not empty)
-                - `"matches"`: Matches a regular expression (matches)
-
-                `isempty`, `isnotempty` and `anyof` are not operators: they are refused with 422
-                "Invalid operation: <name>".
+                - `"matches"`: Matches a regular expression, ignoring case (matches)
+
+                Operator names are case-insensitive: `NOTEMPTY` and `endsWith` work and are stored
+                as sent. `isempty`, `isnotempty`, `anyof`, `notcontains`, `doesnotstartwith`,
+                `doesnotendwith`, `notmatches`, `doesnotmatch` and `notequal` are not operators:
+                they are refused with 422 "Invalid operation: <name>", with the name in lowercase,
+                both when the filter is saved and by `POST /v1/processors/filter`. To negate a
+                condition, wrap it in `not`.
+
+                The string comparisons (`equals`, `contains`, `startswith`, `endswith` and their
+                negations) are case-sensitive; wrap the field in `lowercase` to compare without case.
+                `matches` is not: every pattern is compiled with the flags `gi`, so `^paid$` also
+                matches `PAID` and `[a-z]` matches capital letters. An inline flag such as `(?i)`
+                makes the pattern invalid. The filter still saves, but in a run every record fails
+                with `FILTER_EVALUATION_FAILED` ("Invalid regular expression: /(?i)…/gi: Invalid
+                group"), and `POST /v1/processors/filter` refuses the call with 422 (live-verified
+                2026-10-22).
 
                 **Logical Operators**
                 - `"and"`: All conditions must be true
@@ -5280,7 +5119,7 @@ components:
 
               This value is used as a fallback when:
               1. The source value doesn't match any key in the map
-              2. allowFailures is set to true
+              2. allowFailures is true or omitted
 
               Setting an appropriate default helps prevent flow failures due to unexpected
               values and provides predictable behavior for edge cases.
@@ -5290,8 +5129,10 @@ components:
               - Original value indicators: "{Original Value}", "No mapping found"
               - Neutral values: "Other", "N/A", "Miscellaneous"
 
-              If allowFailures is false, a record whose value is unmapped fails and the default
-              is ignored.
+              A save refuses a default together with an explicit `allowFailures: false`
+              (422 `Lookups with default set can not have allowFailures explicitly set to
+              false.`): a lookup either fails a miss (`allowFailures: false`, no default) or
+              falls back to its default.
             examples:
               - Unknown
               - Other
@@ -5299,7 +5140,8 @@ components:
               - Unmapped Value
               - '{Original Value}'
             x-celigo-ai-guidance:
-              - 'Omit this field entirely when no fallback value is intended: a miss the lookup lets through then leaves the mapped field out, and with `allowFailures: false` a miss fails the record whatever the default. An empty string is a value, not "no default" — the save accepts `default: ""`, and an allowed miss writes `""`.'
+              - 'Omit this field entirely when no fallback value is intended: a miss the lookup lets through then leaves the mapped field out, and `allowFailures: false` (which a save refuses alongside a default) fails it. An empty string is a value, not "no default" — the save accepts `default: ""`, and an allowed miss writes `""`.'
+              - A default sends every unmapped value with no error, so add the missing key to the map when the destination needs the real value; keys match the extracted value exactly (case, spacing and suffixes count), and a save replaces the whole map.
           allowFailures:
             type:
               - boolean
@@ -5956,8 +5798,14 @@ components:
         mappings:
           allOf:
             - $ref: '#/components/schemas/Mappings'
-        responseMapping:
-          $ref: '#/components/schemas/ResponseMapping'
+          x-celigo-ai-guidance:
+            - |-
+              The mapped record is the agent's input: its `text` is sent as text, `record` as
+              its JSON, and `files` (`[{name, blobKey}]`, blob keys from earlier in the same
+              flow) as attachments. `conversationHistoryId` (at most 200
+              characters) keeps one conversation per agent and id across runs. A record with
+              none of `text`, `record` or `files` is sent whole, as JSON, so with no mappings a
+              record's own top-level `text`, `record` or `files` field is its only input.
         inputContext:
           type: string
           enum:
@@ -5968,7 +5816,9 @@ components:
             envelope: The agent receives records wrapped in an envelope with metadata.
           description: |-
             Selects the data context that `mappings[].extract` evaluates against. With no
-            mappings the agent receives the entire record and `inputContext` is moot. `record`
+            mappings the agent receives the entire record as JSON (or only the record's own
+            top-level `text`, `record` or `files` fields, when it has any) and `inputContext`
+            is moot. `record`
             (the default) extracts against the flat record; `envelope` extracts against the
             runtime envelope, which exposes the record alongside job, settings, and other
             run-time metadata (`$.record.field`, `$.settings.field`, etc.). Same contract as
@@ -6068,6 +5918,13 @@ components:
               _headers:
                 type: object
                 description: Mock response headers.
+              blobKey:
+                type: string
+                description: |-
+                  Mock output of an agent with `blob` output (image generation:
+                  `openai.output.format.type` or `litellm.responseFormat.type` set to `blob`),
+                  which returns the stored image's key here. Unrelated to the import-level `blob`
+                  flag, which agents refuse.
     ResourceResponse:
       type: object
       description: Response

package/dist/asynchelper.yml

@@ -543,7 +543,11 @@ components:
 
             **Simple Types (direct value mapping)**
             - `string`: Text values, converts other types to string representation
-            - `number`: Numeric values, attempts conversion from strings
+            - `number`: Numeric values. Converts a numeric string (`"24"` → `24`,
+              `"007"` → `7`) and leaves the field out for an empty string; a value
+              holding letters or a thousands separator (`"1,250.00"`) fails the
+              record with `non_parsable_string` (`<generate>: String contains alpha
+              characters`)
             - `boolean`: True/false values, converts truthy/falsy values
 
             Dates are represented as strings — use `string` for date fields and
@@ -586,8 +590,14 @@ components:
             - |-
               Missing `dataType` is rejected at save with validation error
               `[mandatory_destination_datatype] Destination datatype is a
-              required field.` When in doubt, use `"string"` — it accepts
-              any source value and the runtime will coerce it.
+              required field.`
+            - |-
+              Give each row the type the destination field expects; `"string"` is
+              not a safe default. It accepts any source value, but sends a numeric
+              source as text (`"24"`), which a destination that checks JSON types
+              refuses. Map numeric destination fields as `number`, which fails a
+              record (`non_parsable_string`) only when the value holds letters or a
+              thousands separator.
           enum:
             - string
             - number
@@ -599,7 +609,7 @@ components:
             - objectarray
           x-enumDescriptions:
             string: Text values; converts other types to their string representation.
-            number: Numeric values; attempts conversion from strings.
+            number: Numeric values; converts numeric strings, and fails the record (`non_parsable_string`) on letters or a thousands separator.
             boolean: True/false values; converts truthy/falsy values.
             object: Nested object built from child `mappings`, or copied whole with `extract` (not both).
             stringarray: Array of string values.
@@ -1627,7 +1637,11 @@ components:
 
               **Simple Types (direct value mapping)**
               - `string`: Text values, converts other types to string representation
-              - `number`: Numeric values, attempts conversion from strings
+              - `number`: Numeric values. Converts a numeric string (`"24"` → `24`,
+                `"007"` → `7`) and leaves the field out for an empty string; a value
+                holding letters or a thousands separator (`"1,250.00"`) fails the
+                record with `non_parsable_string` (`<generate>: String contains alpha
+                characters`)
               - `boolean`: True/false values, converts truthy/falsy values
 
               Dates are represented as strings — use `string` for date fields and
@@ -1670,8 +1684,14 @@ components:
               - |-
                 Missing `dataType` is rejected at save with validation error
                 `[mandatory_destination_datatype] Destination datatype is a
-                required field.` When in doubt, use `"string"` — it accepts
-                any source value and the runtime will coerce it.
+                required field.`
+              - |-
+                Give each row the type the destination field expects; `"string"` is
+                not a safe default. It accepts any source value, but sends a numeric
+                source as text (`"24"`), which a destination that checks JSON types
+                refuses. Map numeric destination fields as `number`, which fails a
+                record (`non_parsable_string`) only when the value holds letters or a
+                thousands separator.
             enum:
               - string
               - number
@@ -1683,7 +1703,7 @@ components:
               - objectarray
             x-enumDescriptions:
               string: Text values; converts other types to their string representation.
-              number: Numeric values; attempts conversion from strings.
+              number: Numeric values; converts numeric strings, and fails the record (`non_parsable_string`) on letters or a thousands separator.
               boolean: True/false values; converts truthy/falsy values.
               object: Nested object built from child `mappings`, or copied whole with `extract` (not both).
               stringarray: Array of string values.
@@ -2825,7 +2845,7 @@ components:
 
               This value is used as a fallback when:
               1. The source value doesn't match any key in the map
-              2. allowFailures is set to true
+              2. allowFailures is true or omitted
 
               Setting an appropriate default helps prevent flow failures due to unexpected
               values and provides predictable behavior for edge cases.
@@ -2835,8 +2855,10 @@ components:
               - Original value indicators: "{Original Value}", "No mapping found"
               - Neutral values: "Other", "N/A", "Miscellaneous"
 
-              If allowFailures is false, a record whose value is unmapped fails and the default
-              is ignored.
+              A save refuses a default together with an explicit `allowFailures: false`
+              (422 `Lookups with default set can not have allowFailures explicitly set to
+              false.`): a lookup either fails a miss (`allowFailures: false`, no default) or
+              falls back to its default.
             examples:
               - Unknown
               - Other
@@ -2844,7 +2866,8 @@ components:
               - Unmapped Value
               - '{Original Value}'
             x-celigo-ai-guidance:
-              - 'Omit this field entirely when no fallback value is intended: a miss the lookup lets through then leaves the mapped field out, and with `allowFailures: false` a miss fails the record whatever the default. An empty string is a value, not "no default" — the save accepts `default: ""`, and an allowed miss writes `""`.'
+              - 'Omit this field entirely when no fallback value is intended: a miss the lookup lets through then leaves the mapped field out, and `allowFailures: false` (which a save refuses alongside a default) fails it. An empty string is a value, not "no default" — the save accepts `default: ""`, and an allowed miss writes `""`.'
+              - A default sends every unmapped value with no error, so add the missing key to the map when the destination needs the real value; keys match the extracted value exactly (case, spacing and suffixes count), and a save replaces the whole map.
           allowFailures:
             type:
               - boolean