Skip to Content

Coupa Connector

Summary

The Jitterbit Harmony Coupa Connector establishes access to Coupa.

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

The Coupa connector is accessed from the design component palette's Connections tab (see Design Component Palette).

Connector Overview

This connector is used to first configure a Coupa 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 Coupa connection and its activities are referred to as a Coupa endpoint:

Coupa activity types

  • Query: Queries object data in Coupa and is intended to be used as a source in an operation.

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

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

Note

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 Coupa 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 Coupa connector uses the Coupa R36 Core Platform API. Refer to the API documentation for information on the schema nodes and fields.

Limitations

The Coupa connector does not currently support the Attachment object using Coupa's Attachments API.

Troubleshooting

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

  1. Ensure the Coupa connection is successful by using the Test button in the configuration screen. If the connection is not successful, the error returned may provide an indication as to the problem.

  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 enable connector verbose logging for this connector using this specific configuration entry of logger name and level:

    <logger name="org.jitterbit.connector.coupa" level="DEBUG"/>

  5. If using Private Agents, you can check the agent logs for more information.