Skip to Content

Ripley connector


The Ripley connector establishes access to Ripley.

The Ripley connector provides an interface for creating a Ripley connection, the foundation used for generating instances of Ripley activities. These activities, once configured, interact with Ripley through the connection.

The Ripley connector is accessed from the design component palette's Project endpoints and connectors tab (see Design component palette).

Connector overview

This connector is used to first configure a Ripley connection. Activity types associated with that connection are then used to create instances of activities that are intended to be used as sources (to provide data in an operation) or targets (to consume data in an operation).

Together, a specific Ripley connection and its activities are referred to as a Ripley endpoint:

Ripley activity types

  • Read: Retrieves object data from Ripley and is intended to be used as a source in an operation.

  • Create: Creates object data in Ripley and is intended to be used as a target in an operation.

  • Update: Updates object data in Ripley and is intended to be used as a target in an operation.


This connector is a Connector SDK-based connector, which may be referred to by Jitterbit when communicating changes made to connectors built with the Connector SDK.

Prerequisites and supported API versions

The Ripley connector requires the use of an agent version 10.1 or later. These agent versions automatically download the latest version of the connector when required.

The Ripley connector uses the API Mercado Ripley. Refer to the API documentation for information on the schema nodes and fields.


If you experience issues with the Ripley connector, these troubleshooting steps are recommended:

  1. Click the Test button in the connection configuration to ensure the connection is successful and to ensure the latest version of the connector is downloaded to the agent (unless using the Disable Auto Connector Update organization policy).

  2. Check the operation logs for any information written during execution of the operation.

  3. Enable operation debug logging (for cloud agents or for private agents) to generate additional log files and data.

  4. If using private agents, you can check the agent logs for more information.