@celigo/api-specs 0.2.110 → 0.2.111

package/dist/export.yml

@@ -7891,8 +7891,8 @@ components:
               - Requires the "soql" object with query configuration
 
           2. **Real-time Event Listeners** (type="distributed")
-              - Responds to Salesforce events as they happen
-              - Uses Salesforce's streaming API and platform events
+              - Responds to Salesforce record creates, updates, and deletes as they happen
+              - Fires through an Apex trigger on the object in the connected org (see `distributed`)
               - Always appears as a "Listener" in the flow builder UI
               - Requires the "distributed" object with event configuration
 
@@ -7957,7 +7957,7 @@ components:
               - **Use Cases**: Real-time synchronization, event-driven integration
               - **Dependencies**:
                 - Only uses REST API (api field is ignored)
-                - Automatically configured with trigger logic in Salesforce
+                - Depends on an Apex trigger on the object in the connected org: Integration Apps create it at installation; for a custom flow the customer deploys it from the export page's Required trigger code (see `distributed`)
                 - Only compatible with standard export type (ignores delta/test/once)
             - |-
               ## IMPLEMENTATION CONSIDERATIONS
@@ -8421,34 +8421,21 @@ components:
                 - SELECT Id, Name, (SELECT Id, FirstName, LastName FROM Contacts) FROM Account
         distributed:
           type: object
-          description: Real-time event listener configuration; required when `type` is `distributed` and not used otherwise. The system installs triggers in the connected Salesforce org and delivers records to the flow as create, update, and delete events occur — no scheduling or manual execution is involved.
+          description: Real-time listener configuration; required when `type` is `distributed` and not used otherwise. Records reach the flow only when an Apex trigger on `sObjectType` in the connected org calls the Celigo package (`integrator_da__.RealTimeExporter.processExport()`) — no scheduling or manual execution is involved. Integration Apps create their triggers at installation; for a custom flow the customer deploys the trigger in Salesforce, starting from the code the export page shows under Required trigger.
           x-celigo-ai-guidance:
-            - Configuration for real-time Salesforce event-driven exports.
             - |-
-              ## FIELD BEHAVIOR
-
-              This object defines real-time event listener settings:
-
-              - REQUIRED when type="distributed"
-              - Not used when type="soql" or for blob exports
-              - Creates push-based integration triggered by Salesforce events
-              - Implements real-time processing of creates, updates, and deletes
-            - |-
-              ## IMPLEMENTATION CONTEXT
-
-              Distributed exports work fundamentally differently from SOQL exports:
-              - No scheduling or manual execution required
-              - Triggered automatically when records change in Salesforce
-              - Data flows in real-time as events occur
-              - Uses Salesforce's platform events and streaming API
-            - |-
-              ## TECHNICAL ARCHITECTURE
-
-              When configured, the system:
-              1. Creates custom triggers in the connected Salesforce org
-              2. Establishes event listeners for the specified objects
-              3. Processes events as they occur (create/update/delete operations)
-              4. Delivers the changed records to the integration flow
+              After creating a listener on a custom flow, relay what the Help Center's "Listen for real-time data
+              from Salesforce" states: an Apex trigger is required per sObject type and, for a custom flow, the
+              customer creates it in Salesforce — copy the export page's Required trigger code, replace `<name>`,
+              and save it under Setup → Object Manager → <object> → Triggers → New; deploying to production also
+              needs a test class with 75% coverage. Integration Apps create their triggers at installation.
+            - |-
+              When a listener on an enabled flow never creates a job for a create, update, or delete, the
+              Celigo-side causes are `distributed.disabled` true, an offline connection, and a qualifier the
+              record does not satisfy — and any qualifier drops delete events (see `qualifier`). Also verify the
+              Help Center's trigger requirement in the connected org: an active Apex trigger on the object whose
+              code calls `integrator_da__.RealTimeExporter`, and the Celigo package reachable through the
+              connection (`GET /v1/connections/{_id}/distributed`, documented in this spec set).
           properties:
             referencedFields:
               type:

package/dist/tool.yml

@@ -31996,8 +31996,8 @@ components:
               - Requires the "soql" object with query configuration
 
           2. **Real-time Event Listeners** (type="distributed")
-              - Responds to Salesforce events as they happen
-              - Uses Salesforce's streaming API and platform events
+              - Responds to Salesforce record creates, updates, and deletes as they happen
+              - Fires through an Apex trigger on the object in the connected org (see `distributed`)
               - Always appears as a "Listener" in the flow builder UI
               - Requires the "distributed" object with event configuration
 
@@ -32062,7 +32062,7 @@ components:
               - **Use Cases**: Real-time synchronization, event-driven integration
               - **Dependencies**:
                 - Only uses REST API (api field is ignored)
-                - Automatically configured with trigger logic in Salesforce
+                - Depends on an Apex trigger on the object in the connected org: Integration Apps create it at installation; for a custom flow the customer deploys it from the export page's Required trigger code (see `distributed`)
                 - Only compatible with standard export type (ignores delta/test/once)
             - |-
               ## IMPLEMENTATION CONSIDERATIONS
@@ -32526,34 +32526,21 @@ components:
                 - SELECT Id, Name, (SELECT Id, FirstName, LastName FROM Contacts) FROM Account
         distributed:
           type: object
-          description: Real-time event listener configuration; required when `type` is `distributed` and not used otherwise. The system installs triggers in the connected Salesforce org and delivers records to the flow as create, update, and delete events occur — no scheduling or manual execution is involved.
+          description: Real-time listener configuration; required when `type` is `distributed` and not used otherwise. Records reach the flow only when an Apex trigger on `sObjectType` in the connected org calls the Celigo package (`integrator_da__.RealTimeExporter.processExport()`) — no scheduling or manual execution is involved. Integration Apps create their triggers at installation; for a custom flow the customer deploys the trigger in Salesforce, starting from the code the export page shows under Required trigger.
           x-celigo-ai-guidance:
-            - Configuration for real-time Salesforce event-driven exports.
             - |-
-              ## FIELD BEHAVIOR
-
-              This object defines real-time event listener settings:
-
-              - REQUIRED when type="distributed"
-              - Not used when type="soql" or for blob exports
-              - Creates push-based integration triggered by Salesforce events
-              - Implements real-time processing of creates, updates, and deletes
+              After creating a listener on a custom flow, relay what the Help Center's "Listen for real-time data
+              from Salesforce" states: an Apex trigger is required per sObject type and, for a custom flow, the
+              customer creates it in Salesforce — copy the export page's Required trigger code, replace `<name>`,
+              and save it under Setup → Object Manager → <object> → Triggers → New; deploying to production also
+              needs a test class with 75% coverage. Integration Apps create their triggers at installation.
             - |-
-              ## IMPLEMENTATION CONTEXT
-
-              Distributed exports work fundamentally differently from SOQL exports:
-              - No scheduling or manual execution required
-              - Triggered automatically when records change in Salesforce
-              - Data flows in real-time as events occur
-              - Uses Salesforce's platform events and streaming API
-            - |-
-              ## TECHNICAL ARCHITECTURE
-
-              When configured, the system:
-              1. Creates custom triggers in the connected Salesforce org
-              2. Establishes event listeners for the specified objects
-              3. Processes events as they occur (create/update/delete operations)
-              4. Delivers the changed records to the integration flow
+              When a listener on an enabled flow never creates a job for a create, update, or delete, the
+              Celigo-side causes are `distributed.disabled` true, an offline connection, and a qualifier the
+              record does not satisfy — and any qualifier drops delete events (see `qualifier`). Also verify the
+              Help Center's trigger requirement in the connected org: an active Apex trigger on the object whose
+              code calls `integrator_da__.RealTimeExporter`, and the Celigo package reachable through the
+              connection (`GET /v1/connections/{_id}/distributed`, documented in this spec set).
           properties:
             referencedFields:
               type:

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@celigo/api-specs",
-  "version": "0.2.110",
+  "version": "0.2.111",
   "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": "155f6181",
+		"iasCommit": "5353c280",
 		"generatedAt": "2026-10-14"
 	},
 	"roots": {