A rate limit being reached. When OpenAI reports that the request rate has been exceeded, the transfer is rescheduled automatically and resumes once the limit window has passed. Nothing is lost and no action is required.

A notification without routing details. An inbound notification that does not carry the details the integration attached to the original request is recorded and skipped without raising an error. This is how notifications generated outside the integration are ignored. See the OpenAI Integration Known Limitations article.

Connection and Authentication

OpenAI API Requests

Record Identifiers

Add/Update OpenAI Customer FROM iPaaS.com

Add/Update OpenAI Product FROM iPaaS.com

Add/Update OpenAI Message TO iPaaS.com

Unsupported Operations

Description: Raised when subscription settings are saved and iPaaS.com cannot establish a connection to OpenAI. There is no fixed message text — what follows the code is the reason OpenAI gave, passed through unchanged. When the failure carried no detail at all, a generic fallback is used instead: "Unable to reach OpenAI to validate the connection. Check the API Url and API Key on the subscription, then try again." That fallback usually points at a network-level problem between iPaaS.com and OpenAI rather than a configuration mistake, since a revoked key or a bad address normally produces a specific reason. The connection is not established and no transfers run until it is resolved.

Resolution: Confirm the API Url is correct and reachable, and that the API Key is current and has not been revoked in the OpenAI console. Because connection validation needs fewer permissions than enrichment does, a key that validates successfully may still be too restricted to run a transfer — confirm it carries at least Write permission on the Responses capability. See the OpenAI Connections and Settings article. If the generic fallback appears and the settings are correct, check whether OpenAI is reporting a service incident before treating it as a configuration fault.

Description: OpenAI rejected a request or returned an unexpected result. The {action} portion names the operation attempted, {status} is the HTTP status OpenAI returned, and the middle portion is OpenAI's own response, reproduced as received. Common causes are an API key that has been revoked or lacks the required permission, a model name the account cannot access, and a malformed request produced by a ModelInstructions value. On the return leg this also covers attempting to retrieve a response OpenAI no longer holds — enrichment requests are submitted without long-term storage, so a response is retained only briefly after it completes.

Resolution: Read the status and OpenAI's message first, as they identify the cause directly. For a permission or authentication status, confirm the API Key on the subscription is current and carries at least Write permission on the Responses capability. For a model-related message, confirm the OpenAI Model setting names a model the account can use. When writing an enriched Product back, note that iPaaS.com requires Sku, Name, Type, TrackingMethod, DefaultPrice and Status, and accepts only Physical or Virtual for Type, Product or Variant for TrackingMethod, and Preorder, Active, Disabled or Discontinued for Status — an instruction that rewrites any of those risks producing a value the write will not accept. If the message indicates a problem inside OpenAI rather than with the request, retry the transfer.

Description: There is no fixed message text for this case: what follows the code is the transport error reported by the connection attempt, for example a name resolution failure, a connection timeout, or a TLS negotiation failure, and no HTTP status is present. The request never reached OpenAI.

Resolution: Confirm the API Url on the subscription is correct. Transport failures are frequently transient, so retry once before treating this as a configuration problem. If it persists, check whether OpenAI is reporting a service incident.

Description: A record identifier supplied for a transfer was not in the form the integration expects for that record type. The rejected value is shown at the end of the message. This most often follows a manual sync submitted with a mistyped identifier, or a mapping that produces an identifier in an unexpected format.

Resolution: Compare the value shown in the message against the identifier as it appears on the record, and re-submit using the exact form. If the value came from a mapping rather than a manual entry, review the mapping that produces the record identifier for that collection.

Description: The collection has no mapping writing to the Id destination, so the enrichment request has nothing to identify the Customer by. The transfer stops before anything is sent to OpenAI.

Resolution: Add a Field mapping on this collection with CustomerNumber as the source and Id as the destination. Any value may be used as the source provided it uniquely identifies the Customer, because the return leg relies on it to match the enriched result back to the right record.

Description: The collection has a ModelInstructions mapping whose value is not valid JSON. That mapping is read as a JSON object of additional request options, so malformed content stops the transfer. The Error Details portion carries the specific parsing complaint.

Resolution: Correct the ModelInstructions value so it is a well-formed JSON object, or remove the mapping if no additional request options are needed. The parsing complaint in Error Details identifies where the problem is. ModelInstructions is optional — enrichment works without it.

Description: The collection has no mapping writing to the Id destination, so the enrichment request has nothing to identify the Product by. The transfer stops before anything is sent to OpenAI.

Resolution: Add a Field mapping on this collection with Sku as the source and Id as the destination. Any value may be used as the source provided it uniquely identifies the Product, because the return leg relies on it to match the enriched result back to the right record.

Description: The collection has a ModelInstructions mapping whose value is not valid JSON. That mapping is read as a JSON object of additional request options, so malformed content stops the transfer. The Error Details portion carries the specific parsing complaint.

Resolution: Correct the ModelInstructions value so it is a well-formed JSON object, or remove the mapping if no additional request options are needed. ModelInstructions is optional — enrichment works without it.

Description: The inbound notification was received and its routing details were read, but the Customer or Product transfer it dispatched did not complete. Because that dispatch is a prerequisite, the Message transfer stops as well and the enrichment is not applied. The underlying failure is logged separately and is usually the more useful entry to read.

Resolution: Look for the accompanying error on the Customer or Product flow and resolve that — this message reports that a dependent transfer failed, not what went wrong inside it. Confirm the target collection is enabled, then re-submit the record for enrichment. Note that re-running the notification alone is not usually possible, because the response it points at is retained only briefly.

Description: The integration sends Customer records to OpenAI for enrichment and reads the results back, but never deletes anything in OpenAI, so a delete attempt fails.

Resolution: Confirm no delete event is enabled against the Customer collections. Enrichment requests are not stored records that need removing.

Description: The Update OpenAI Customer TO iPaaS.com flow returns an enrichment result when one is requested; it does not poll OpenAI for changes on a schedule.

Resolution: Confirm no polling schedule is configured against the Customer TO iPaaS.com collection. Enriched Customers arrive through the return leg of a request you initiated.

Description: Messages represent notifications OpenAI sends back to iPaaS.com. Creating one from iPaaS.com is not implemented, so the attempt fails.

Resolution: Confirm the Message collection is configured TO iPaaS.com only, and that no create event is enabled against it.

Description: Writing message values back to OpenAI is not implemented, so the attempt fails and no OpenAI call is made.

Resolution: Confirm the Message collection is configured TO iPaaS.com only, and that no update event is enabled against it.

Description: Deleting a message in OpenAI from iPaaS.com is not implemented, so the attempt fails and nothing is removed in OpenAI.

Resolution: Confirm no delete event is enabled against the Message collection. Deleting the record in iPaaS.com removes only the iPaaS.com record.

Description: Messages arrive as inbound notifications through the hook the integration registers, not by iPaaS.com asking OpenAI for new items on a schedule.

Resolution: Confirm no polling schedule is configured against the Message collection. If messages are not arriving, the hook registration is the thing to check — see OPAI-INTL-1001 above.

Description: The integration sends Product records to OpenAI for enrichment and reads the results back, but never deletes anything in OpenAI, so a delete attempt fails.

Resolution: Confirm no delete event is enabled against the Product collections. Enrichment requests are not stored records that need removing.

Description: The Add/Update OpenAI Product TO iPaaS.com flow returns an enrichment result when one is requested; it does not poll OpenAI for changes on a schedule.

Resolution: Confirm no polling schedule is configured against the Product TO iPaaS.com collection. Enriched Products arrive through the return leg of a request you initiated.

iPaaS.com <> OpenAI: Background

OpenAI Installation Instructions

OpenAI Connections and Settings

OpenAI API Endpoints

OpenAI Integration Known Limitations