@celigo/api-specs 0.2.21 → 0.2.23

package/dist/ai-agent.yml

@@ -4951,13 +4951,26 @@ components:
         are re-joined into the record's original shape — the object with its array, or the array of rows —
         carrying any response-mapping enrichment, and that re-joined record is what the next step
         receives. Not for locating records in an export's HTTP response; use
-        `http.response.resourcePath` for that.
+        `http.response.resourcePath` for that. Applies to steps that receive a record — imports and
+        lookups (an export referenced as a page processor of a flow, API, or Tool). A standalone export
+        (a flow's page generator) has no incoming record, so the fields are saved but have no effect on
+        the records it produces; to emit one record per array element from a standalone export, use a
+        `hooks.preSavePage` script, or for a file-definition export make the repeating segment the
+        record boundary in the definition's rules.
       x-celigo-ai-guidance:
         - |-
           Two modes, decided by the SHAPE of the record entering the step. Object record with a child
           array under a field → set ``pathToMany`` to that field. Array record (a ``groupByFields``
           export, a CSV/file group, a script that returns an array) → leave ``pathToMany`` blank; each
           element becomes one record. Live-verified 2026-09-10 on flows, Tools, and APIs.
+        - |-
+          Only imports and lookups (exports placed as page processors) fan out. On a standalone export
+          (a flow's page generator) the API saves ``oneToMany`` / ``pathToMany`` and applies neither:
+          the records reach the next step unchanged and no error is raised. Live-verified 2026-09-18 on
+          a flow test run — an order record with three ``lines`` reached the import as ONE record with
+          the setting on the export, and as THREE child records with the same setting on the import.
+          Never propose these fields as the way to split a standalone export's records; that is
+          ``hooks.preSavePage`` work (or, for a file definition, the definition's record boundary).
         - |-
           Blank ``pathToMany`` on an OBJECT record fails every record with code ``oneToMany_error``:
           "Failed to extract child records from oneToMany import data. Record at index 0 was not an
@@ -4987,8 +5000,14 @@ components:
         Path to the array of child records inside an object record when `oneToMany` is true, in dot
         notation (`items`, `lines.lineItems`). Leave blank when the incoming record is itself an array
         (grouped or row-based data) — each element is then a child record. A path that does not resolve
-        to an array processes zero records and reports success.
+        to an array processes zero records and reports success. Read only on steps that receive a
+        record (imports, lookup exports); on a standalone export it is saved and ignored — see `oneToMany`.
       x-celigo-ai-guidance:
+        - |-
+          Inert on a standalone export (a flow's page generator) exactly like ``oneToMany`` — the value
+          is saved, the export's records reach the next step unchanged, and nothing errors
+          (live-verified 2026-09-18). Splitting a standalone export's records into one per element is
+          ``hooks.preSavePage`` work, or the file definition's record boundary; never this field.
         - |-
           Set this ONLY when the record entering the step is an object whose children sit under a field.
           On an array record (a ``groupByFields`` export, a CSV/file group, a script returning an array)

package/dist/export.yml

@@ -803,13 +803,26 @@ components:
         are re-joined into the record's original shape — the object with its array, or the array of rows —
         carrying any response-mapping enrichment, and that re-joined record is what the next step
         receives. Not for locating records in an export's HTTP response; use
-        `http.response.resourcePath` for that.
+        `http.response.resourcePath` for that. Applies to steps that receive a record — imports and
+        lookups (an export referenced as a page processor of a flow, API, or Tool). A standalone export
+        (a flow's page generator) has no incoming record, so the fields are saved but have no effect on
+        the records it produces; to emit one record per array element from a standalone export, use a
+        `hooks.preSavePage` script, or for a file-definition export make the repeating segment the
+        record boundary in the definition's rules.
       x-celigo-ai-guidance:
         - |-
           Two modes, decided by the SHAPE of the record entering the step. Object record with a child
           array under a field → set ``pathToMany`` to that field. Array record (a ``groupByFields``
           export, a CSV/file group, a script that returns an array) → leave ``pathToMany`` blank; each
           element becomes one record. Live-verified 2026-09-10 on flows, Tools, and APIs.
+        - |-
+          Only imports and lookups (exports placed as page processors) fan out. On a standalone export
+          (a flow's page generator) the API saves ``oneToMany`` / ``pathToMany`` and applies neither:
+          the records reach the next step unchanged and no error is raised. Live-verified 2026-09-18 on
+          a flow test run — an order record with three ``lines`` reached the import as ONE record with
+          the setting on the export, and as THREE child records with the same setting on the import.
+          Never propose these fields as the way to split a standalone export's records; that is
+          ``hooks.preSavePage`` work (or, for a file definition, the definition's record boundary).
         - |-
           Blank ``pathToMany`` on an OBJECT record fails every record with code ``oneToMany_error``:
           "Failed to extract child records from oneToMany import data. Record at index 0 was not an
@@ -839,8 +852,14 @@ components:
         Path to the array of child records inside an object record when `oneToMany` is true, in dot
         notation (`items`, `lines.lineItems`). Leave blank when the incoming record is itself an array
         (grouped or row-based data) — each element is then a child record. A path that does not resolve
-        to an array processes zero records and reports success.
+        to an array processes zero records and reports success. Read only on steps that receive a
+        record (imports, lookup exports); on a standalone export it is saved and ignored — see `oneToMany`.
       x-celigo-ai-guidance:
+        - |-
+          Inert on a standalone export (a flow's page generator) exactly like ``oneToMany`` — the value
+          is saved, the export's records reach the next step unchanged, and nothing errors
+          (live-verified 2026-09-18). Splitting a standalone export's records into one per element is
+          ``hooks.preSavePage`` work, or the file definition's record boundary; never this field.
         - |-
           Set this ONLY when the record entering the step is an object whose children sit under a field.
           On an array record (a ``groupByFields`` export, a CSV/file group, a script returning an array)
@@ -5902,10 +5921,10 @@ components:
             - blob
             - csvstream
           x-enumDescriptions:
-            file: Treats the HTTP response as raw file content (PDFs, images, binary data) rather than structured data records.
+            file: Works with files instead of a record endpoint — a raw file download (PDFs, images, binary data), or a file-provider folder whose files the file object parses into records (csv, json, xml, xlsx, filedefinition incl. EDI)
             blob: Transfers the raw response body downstream as a blob without parsing it into records.
             csvstream: Streams a large CSV response, parsing it row-by-row instead of loading the whole body into memory.
-          description: Set to `file` only when the endpoint returns raw file content (PDFs, images, binary data) to be saved as a file rather than parsed as records; the `file` object must also be configured. Leave undefined for standard data exports that return structured records (JSON, XML, GraphQL, SOAP responses) — the response is then parsed into records for downstream steps. When set to `file` or `blob`, the export appears as a "Transfer" step in Flow Builder instead of a standard "Export" step.
+          description: 'Set to `file` when the export works with files rather than a record-returning endpoint: raw file downloads (PDFs, images, binary data) and the folder mode of the cloud file providers (Google Drive, Box, Dropbox, Azure Blob, Google Cloud Storage, Celigo Storage), where each file in the folder is parsed by the `file` object''s `type` (csv, json, xml, xlsx, filedefinition — including EDI) into records; the `file` object must also be configured. Leave undefined for standard data exports that return structured records (JSON, XML, GraphQL, SOAP responses) — the response is then parsed into records for downstream steps. When set to `file` or `blob`, the export appears as a "Transfer" step in Flow Builder instead of a standard "Export" step.'
           x-celigo-ai-guidance:
             - |-
               ## IMPORTANT: This field should be LEFT UNDEFINED for the vast majority of HTTP exports.
@@ -5927,18 +5946,24 @@ components:
               - "Export all Shopify Customers" → undefined (returns JSON customer records)
               - "Retrieve orders from custom REST API" → undefined (returns JSON order records)
             - |-
-              ## WHEN TO SET THIS FIELD TO 'file' (RARE USE CASE):
+              ## WHEN TO SET THIS FIELD TO 'file' (the export works with FILES, not a record endpoint):
 
-              Set this field to 'file' ONLY when the HTTP endpoint is specifically designed to download files:
-              - The endpoint returns raw binary file content (PDFs, images, ZIP files, etc.)
-              - The endpoint is a file download service (e.g., downloading invoices, reports, attachments)
-              - The response body contains file data that needs to be saved as a file, not parsed as records
-              - You need to download and process files from a remote server
+              Set this field to 'file' in two situations:
+              - The HTTP endpoint is specifically designed to download files — it returns raw binary
+                file content (PDFs, images, ZIP files) or is a file download service (invoices,
+                reports, attachments) whose body is saved as a file rather than parsed as records
+              - The connection is a cloud file provider used in FOLDER mode (Google Drive, Box, Dropbox,
+                Azure Blob Storage, Google Cloud Storage, Celigo Storage): the export reads the files
+                in a folder and the 'file' object's `type` (csv, json, xml, xlsx, filedefinition)
+                parses each one into records — the same file layer as an FTP or S3 export
 
               Examples of when to set type: "file":
               - "Download PDF invoices from the API" → type: "file"
               - "Retrieve image files from a file server" → type: "file"
-              - "Download CSV files from an FTP server via HTTP" → type: "file"
+              - "Read the CSV files dropped in our Google Drive folder" → type: "file", with file.type "csv"
+              - "Parse EDI X12 850 files from a Google Drive / Celigo Storage folder" → type: "file",
+                with file.type "filedefinition" and a top-level _ediProfileId (EDI fields are
+                accepted on HTTP exports only in file mode)
             - |-
               ## IMPLEMENTATION DETAILS
 
@@ -5946,7 +5971,9 @@ components:
               - The 'file' object property MUST also be configured
               - The export appears as a "Transfer" step in the Flow Builder UI
               - The system applies file-specific processing to the HTTP response
-              - Downstream steps receive file content rather than record data
+              - Downstream steps receive records when the 'file' object's `type` parses the files
+                (csv, json, xml, xlsx, filedefinition with `file.output: "records"`), or the file
+                content itself when `file.output` is "blobKeys"
 
               When this field is undefined (default for most exports):
               - The export appears as a standard "Export" step in the Flow Builder UI
@@ -5961,6 +5988,9 @@ components:
                  → YES: Leave this field undefined
               3. Does the API endpoint return raw file content (PDFs, images, binary data)?
                  → YES: Set this field to "file" (and configure the 'file' property)
+              4. Is the connection a cloud file provider and the export reads a FOLDER of files
+                 (CSV, JSON, XML, XLSX, or EDI via a file definition)?
+                 → YES: Set this field to "file" (and configure the 'file' property with the parsing type)
 
               Remember: When in doubt, leave this field undefined. Most HTTP exports are standard data exports.
           examples:
@@ -16185,9 +16215,12 @@ components:
           format: objectId
           x-celigo-refModel: ediprofiles
           description: |-
-            EDI profile this export uses to parse incoming X12 EDI documents into structured JSON —
-            it supplies the envelope qualifiers, delimiters, version, and validation rules. Set it
-            when the export parses or validates EDI files; omit it otherwise.
+            EDI profile this export uses to parse incoming X12 or EDIFACT documents into structured
+            JSON — it supplies the envelope qualifiers, delimiters, version, and validation rules.
+            Set it when the export parses or validates EDI files; omit it otherwise. Accepted on the
+            file-reading exports — FTP, AS2, S3 and HTTP file mode (`http.type: "file"`).
+          x-celigo-ai-guidance:
+            - 'An HTTP export accepts this field only in file mode (`http.type: "file"`, the folder mode of file-provider connectors such as Google Drive, Box, Dropbox, Azure Blob, Google Cloud Storage and Celigo Storage). On a REST/records HTTP export the save is rejected with `not_supported`: "EDIProfile can only be associated with the export of type FTP, AS2, S3 or HTTP file."'
           examples:
             - 60a2c4e6f321d800129a1a3c
         _postParseListenerId:
@@ -16197,8 +16230,10 @@ components:
           description: |-
             Webhook export invoked once per file after EDI parsing, on both success and failure
             (errors are included in the payload when parsing fails). Primarily used to send
-            functional acknowledgements (997/999) to trading partners. Only supported for
-            `AS2Export` and `FTPExport` parsing EDI files.
+            functional acknowledgements (997/999) to trading partners. Accepted on the file-reading
+            exports that parse EDI — FTP, AS2, S3 and HTTP file mode (`http.type: "file"`).
+          x-celigo-ai-guidance:
+            - 'The listener must be an export with `type: "webhook"` and `webhook.provider: "integrator-extension"`; any other export id is rejected with `invalid_post_parse_listener`. On an HTTP export outside file mode the save is rejected with `post_parse_listener_not_supported`: "Listener for functional acknowledgment is only supported for AS2, FTP, S3 and HTTP file export."'
           examples:
             - 60a2c4e6f321d800129a1a3c
         externalId:

package/dist/import.yml

@@ -8247,11 +8247,15 @@ components:
         - `S3Import`
         - `FTPImport`
         - `AS2Import`
+        - `HTTPImport` in file mode (`http.type: "file"` — the folder mode of the cloud file
+          providers such as Google Drive, Box, Dropbox, Azure Blob, Google Cloud Storage and Celigo
+          Storage); the same `file` object, including `type: filedefinition` with `_ediProfileId`
+          for EDI, applies as on S3 / FTP
 
         ❌ **DO NOT SET** for non-file-based imports like:
         - `SalesforceImport`
         - `NetSuiteImport`
-        - `HTTPImport`
+        - `HTTPImport` in records mode (`http.type` unset — a REST endpoint receiving records)
         - `MongodbImport`
         - `RDBMSImport`
 
@@ -10581,13 +10585,26 @@ components:
         are re-joined into the record's original shape — the object with its array, or the array of rows —
         carrying any response-mapping enrichment, and that re-joined record is what the next step
         receives. Not for locating records in an export's HTTP response; use
-        `http.response.resourcePath` for that.
+        `http.response.resourcePath` for that. Applies to steps that receive a record — imports and
+        lookups (an export referenced as a page processor of a flow, API, or Tool). A standalone export
+        (a flow's page generator) has no incoming record, so the fields are saved but have no effect on
+        the records it produces; to emit one record per array element from a standalone export, use a
+        `hooks.preSavePage` script, or for a file-definition export make the repeating segment the
+        record boundary in the definition's rules.
       x-celigo-ai-guidance:
         - |-
           Two modes, decided by the SHAPE of the record entering the step. Object record with a child
           array under a field → set ``pathToMany`` to that field. Array record (a ``groupByFields``
           export, a CSV/file group, a script that returns an array) → leave ``pathToMany`` blank; each
           element becomes one record. Live-verified 2026-09-10 on flows, Tools, and APIs.
+        - |-
+          Only imports and lookups (exports placed as page processors) fan out. On a standalone export
+          (a flow's page generator) the API saves ``oneToMany`` / ``pathToMany`` and applies neither:
+          the records reach the next step unchanged and no error is raised. Live-verified 2026-09-18 on
+          a flow test run — an order record with three ``lines`` reached the import as ONE record with
+          the setting on the export, and as THREE child records with the same setting on the import.
+          Never propose these fields as the way to split a standalone export's records; that is
+          ``hooks.preSavePage`` work (or, for a file definition, the definition's record boundary).
         - |-
           Blank ``pathToMany`` on an OBJECT record fails every record with code ``oneToMany_error``:
           "Failed to extract child records from oneToMany import data. Record at index 0 was not an
@@ -10617,8 +10634,14 @@ components:
         Path to the array of child records inside an object record when `oneToMany` is true, in dot
         notation (`items`, `lines.lineItems`). Leave blank when the incoming record is itself an array
         (grouped or row-based data) — each element is then a child record. A path that does not resolve
-        to an array processes zero records and reports success.
+        to an array processes zero records and reports success. Read only on steps that receive a
+        record (imports, lookup exports); on a standalone export it is saved and ignored — see `oneToMany`.
       x-celigo-ai-guidance:
+        - |-
+          Inert on a standalone export (a flow's page generator) exactly like ``oneToMany`` — the value
+          is saved, the export's records reach the next step unchanged, and nothing errors
+          (live-verified 2026-09-18). Splitting a standalone export's records into one per element is
+          ``hooks.preSavePage`` work, or the file definition's record boundary; never this field.
         - |-
           Set this ONLY when the record entering the step is an object whose children sit under a field.
           On an array record (a ``groupByFields`` export, a CSV/file group, a script returning an array)
@@ -14393,9 +14416,12 @@ components:
           format: objectId
           x-celigo-refModel: ediprofiles
           description: |-
-            EDI profile this import uses to generate outbound X12 EDI documents — it supplies the
-            envelope qualifiers, delimiters, version, and validation rules. Set it when the import
-            produces EDI output; omit it otherwise.
+            EDI profile this import uses to generate outbound X12 or EDIFACT documents — it supplies
+            the envelope qualifiers, delimiters, version, and validation rules. Set it when the
+            import produces EDI output; omit it otherwise. Accepted on the file-writing imports —
+            FTP, AS2, S3 and HTTP file mode (`http.type: "file"`).
+          x-celigo-ai-guidance:
+            - 'On an HTTP import set `http.type: "file"` (the folder mode of file-provider connectors) and pair this field with `file.type: "filedefinition"` and `file.skipAggregation: true` or `file.aggregation.type: "key"` — the platform saves EDI files per page or per key, never aggregated per run.'
         parsers:
           type: array
           description: |-

package/dist/tool.yml

@@ -17105,11 +17105,15 @@ components:
         - `S3Import`
         - `FTPImport`
         - `AS2Import`
+        - `HTTPImport` in file mode (`http.type: "file"` — the folder mode of the cloud file
+          providers such as Google Drive, Box, Dropbox, Azure Blob, Google Cloud Storage and Celigo
+          Storage); the same `file` object, including `type: filedefinition` with `_ediProfileId`
+          for EDI, applies as on S3 / FTP
 
         ❌ **DO NOT SET** for non-file-based imports like:
         - `SalesforceImport`
         - `NetSuiteImport`
-        - `HTTPImport`
+        - `HTTPImport` in records mode (`http.type` unset — a REST endpoint receiving records)
         - `MongodbImport`
         - `RDBMSImport`
 
@@ -19439,13 +19443,26 @@ components:
         are re-joined into the record's original shape — the object with its array, or the array of rows —
         carrying any response-mapping enrichment, and that re-joined record is what the next step
         receives. Not for locating records in an export's HTTP response; use
-        `http.response.resourcePath` for that.
+        `http.response.resourcePath` for that. Applies to steps that receive a record — imports and
+        lookups (an export referenced as a page processor of a flow, API, or Tool). A standalone export
+        (a flow's page generator) has no incoming record, so the fields are saved but have no effect on
+        the records it produces; to emit one record per array element from a standalone export, use a
+        `hooks.preSavePage` script, or for a file-definition export make the repeating segment the
+        record boundary in the definition's rules.
       x-celigo-ai-guidance:
         - |-
           Two modes, decided by the SHAPE of the record entering the step. Object record with a child
           array under a field → set ``pathToMany`` to that field. Array record (a ``groupByFields``
           export, a CSV/file group, a script that returns an array) → leave ``pathToMany`` blank; each
           element becomes one record. Live-verified 2026-09-10 on flows, Tools, and APIs.
+        - |-
+          Only imports and lookups (exports placed as page processors) fan out. On a standalone export
+          (a flow's page generator) the API saves ``oneToMany`` / ``pathToMany`` and applies neither:
+          the records reach the next step unchanged and no error is raised. Live-verified 2026-09-18 on
+          a flow test run — an order record with three ``lines`` reached the import as ONE record with
+          the setting on the export, and as THREE child records with the same setting on the import.
+          Never propose these fields as the way to split a standalone export's records; that is
+          ``hooks.preSavePage`` work (or, for a file definition, the definition's record boundary).
         - |-
           Blank ``pathToMany`` on an OBJECT record fails every record with code ``oneToMany_error``:
           "Failed to extract child records from oneToMany import data. Record at index 0 was not an
@@ -19475,8 +19492,14 @@ components:
         Path to the array of child records inside an object record when `oneToMany` is true, in dot
         notation (`items`, `lines.lineItems`). Leave blank when the incoming record is itself an array
         (grouped or row-based data) — each element is then a child record. A path that does not resolve
-        to an array processes zero records and reports success.
+        to an array processes zero records and reports success. Read only on steps that receive a
+        record (imports, lookup exports); on a standalone export it is saved and ignored — see `oneToMany`.
       x-celigo-ai-guidance:
+        - |-
+          Inert on a standalone export (a flow's page generator) exactly like ``oneToMany`` — the value
+          is saved, the export's records reach the next step unchanged, and nothing errors
+          (live-verified 2026-09-18). Splitting a standalone export's records into one per element is
+          ``hooks.preSavePage`` work, or the file definition's record boundary; never this field.
         - |-
           Set this ONLY when the record entering the step is an object whose children sit under a field.
           On an array record (a ``groupByFields`` export, a CSV/file group, a script returning an array)
@@ -21172,9 +21195,12 @@ components:
           format: objectId
           x-celigo-refModel: ediprofiles
           description: |-
-            EDI profile this import uses to generate outbound X12 EDI documents — it supplies the
-            envelope qualifiers, delimiters, version, and validation rules. Set it when the import
-            produces EDI output; omit it otherwise.
+            EDI profile this import uses to generate outbound X12 or EDIFACT documents — it supplies
+            the envelope qualifiers, delimiters, version, and validation rules. Set it when the
+            import produces EDI output; omit it otherwise. Accepted on the file-writing imports —
+            FTP, AS2, S3 and HTTP file mode (`http.type: "file"`).
+          x-celigo-ai-guidance:
+            - 'On an HTTP import set `http.type: "file"` (the folder mode of file-provider connectors) and pair this field with `file.type: "filedefinition"` and `file.skipAggregation: true` or `file.aggregation.type: "key"` — the platform saves EDI files per page or per key, never aggregated per run.'
         parsers:
           type: array
           description: |-
@@ -26294,10 +26320,10 @@ components:
             - blob
             - csvstream
           x-enumDescriptions:
-            file: Treats the HTTP response as raw file content (PDFs, images, binary data) rather than structured data records.
+            file: Works with files instead of a record endpoint — a raw file download (PDFs, images, binary data), or a file-provider folder whose files the file object parses into records (csv, json, xml, xlsx, filedefinition incl. EDI)
             blob: Transfers the raw response body downstream as a blob without parsing it into records.
             csvstream: Streams a large CSV response, parsing it row-by-row instead of loading the whole body into memory.
-          description: Set to `file` only when the endpoint returns raw file content (PDFs, images, binary data) to be saved as a file rather than parsed as records; the `file` object must also be configured. Leave undefined for standard data exports that return structured records (JSON, XML, GraphQL, SOAP responses) — the response is then parsed into records for downstream steps. When set to `file` or `blob`, the export appears as a "Transfer" step in Flow Builder instead of a standard "Export" step.
+          description: 'Set to `file` when the export works with files rather than a record-returning endpoint: raw file downloads (PDFs, images, binary data) and the folder mode of the cloud file providers (Google Drive, Box, Dropbox, Azure Blob, Google Cloud Storage, Celigo Storage), where each file in the folder is parsed by the `file` object''s `type` (csv, json, xml, xlsx, filedefinition — including EDI) into records; the `file` object must also be configured. Leave undefined for standard data exports that return structured records (JSON, XML, GraphQL, SOAP responses) — the response is then parsed into records for downstream steps. When set to `file` or `blob`, the export appears as a "Transfer" step in Flow Builder instead of a standard "Export" step.'
           x-celigo-ai-guidance:
             - |-
               ## IMPORTANT: This field should be LEFT UNDEFINED for the vast majority of HTTP exports.
@@ -26319,18 +26345,24 @@ components:
               - "Export all Shopify Customers" → undefined (returns JSON customer records)
               - "Retrieve orders from custom REST API" → undefined (returns JSON order records)
             - |-
-              ## WHEN TO SET THIS FIELD TO 'file' (RARE USE CASE):
+              ## WHEN TO SET THIS FIELD TO 'file' (the export works with FILES, not a record endpoint):
 
-              Set this field to 'file' ONLY when the HTTP endpoint is specifically designed to download files:
-              - The endpoint returns raw binary file content (PDFs, images, ZIP files, etc.)
-              - The endpoint is a file download service (e.g., downloading invoices, reports, attachments)
-              - The response body contains file data that needs to be saved as a file, not parsed as records
-              - You need to download and process files from a remote server
+              Set this field to 'file' in two situations:
+              - The HTTP endpoint is specifically designed to download files — it returns raw binary
+                file content (PDFs, images, ZIP files) or is a file download service (invoices,
+                reports, attachments) whose body is saved as a file rather than parsed as records
+              - The connection is a cloud file provider used in FOLDER mode (Google Drive, Box, Dropbox,
+                Azure Blob Storage, Google Cloud Storage, Celigo Storage): the export reads the files
+                in a folder and the 'file' object's `type` (csv, json, xml, xlsx, filedefinition)
+                parses each one into records — the same file layer as an FTP or S3 export
 
               Examples of when to set type: "file":
               - "Download PDF invoices from the API" → type: "file"
               - "Retrieve image files from a file server" → type: "file"
-              - "Download CSV files from an FTP server via HTTP" → type: "file"
+              - "Read the CSV files dropped in our Google Drive folder" → type: "file", with file.type "csv"
+              - "Parse EDI X12 850 files from a Google Drive / Celigo Storage folder" → type: "file",
+                with file.type "filedefinition" and a top-level _ediProfileId (EDI fields are
+                accepted on HTTP exports only in file mode)
             - |-
               ## IMPLEMENTATION DETAILS
 
@@ -26338,7 +26370,9 @@ components:
               - The 'file' object property MUST also be configured
               - The export appears as a "Transfer" step in the Flow Builder UI
               - The system applies file-specific processing to the HTTP response
-              - Downstream steps receive file content rather than record data
+              - Downstream steps receive records when the 'file' object's `type` parses the files
+                (csv, json, xml, xlsx, filedefinition with `file.output: "records"`), or the file
+                content itself when `file.output` is "blobKeys"
 
               When this field is undefined (default for most exports):
               - The export appears as a standard "Export" step in the Flow Builder UI
@@ -26353,6 +26387,9 @@ components:
                  → YES: Leave this field undefined
               3. Does the API endpoint return raw file content (PDFs, images, binary data)?
                  → YES: Set this field to "file" (and configure the 'file' property)
+              4. Is the connection a cloud file provider and the export reads a FOLDER of files
+                 (CSV, JSON, XML, XLSX, or EDI via a file definition)?
+                 → YES: Set this field to "file" (and configure the 'file' property with the parsing type)
 
               Remember: When in doubt, leave this field undefined. Most HTTP exports are standard data exports.
           examples:
@@ -33607,9 +33644,12 @@ components:
           format: objectId
           x-celigo-refModel: ediprofiles
           description: |-
-            EDI profile this export uses to parse incoming X12 EDI documents into structured JSON —
-            it supplies the envelope qualifiers, delimiters, version, and validation rules. Set it
-            when the export parses or validates EDI files; omit it otherwise.
+            EDI profile this export uses to parse incoming X12 or EDIFACT documents into structured
+            JSON — it supplies the envelope qualifiers, delimiters, version, and validation rules.
+            Set it when the export parses or validates EDI files; omit it otherwise. Accepted on the
+            file-reading exports — FTP, AS2, S3 and HTTP file mode (`http.type: "file"`).
+          x-celigo-ai-guidance:
+            - 'An HTTP export accepts this field only in file mode (`http.type: "file"`, the folder mode of file-provider connectors such as Google Drive, Box, Dropbox, Azure Blob, Google Cloud Storage and Celigo Storage). On a REST/records HTTP export the save is rejected with `not_supported`: "EDIProfile can only be associated with the export of type FTP, AS2, S3 or HTTP file."'
           examples:
             - 60a2c4e6f321d800129a1a3c
         _postParseListenerId:
@@ -33619,8 +33659,10 @@ components:
           description: |-
             Webhook export invoked once per file after EDI parsing, on both success and failure
             (errors are included in the payload when parsing fails). Primarily used to send
-            functional acknowledgements (997/999) to trading partners. Only supported for
-            `AS2Export` and `FTPExport` parsing EDI files.
+            functional acknowledgements (997/999) to trading partners. Accepted on the file-reading
+            exports that parse EDI — FTP, AS2, S3 and HTTP file mode (`http.type: "file"`).
+          x-celigo-ai-guidance:
+            - 'The listener must be an export with `type: "webhook"` and `webhook.provider: "integrator-extension"`; any other export id is rejected with `invalid_post_parse_listener`. On an HTTP export outside file mode the save is rejected with `post_parse_listener_not_supported`: "Listener for functional acknowledgment is only supported for AS2, FTP, S3 and HTTP file export."'
           examples:
             - 60a2c4e6f321d800129a1a3c
         externalId:

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@celigo/api-specs",
-  "version": "0.2.21",
+  "version": "0.2.23",
   "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": "dc9205a",
+		"iasCommit": "ed5e198",
 		"generatedAt": "2026-09-18"
 	},
 	"roots": {