Skip to Content

SugarCRM Connector

Summary

The Jitterbit Harmony SugarCRM Connector establishes access to SugarCRM.

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

The SugarCRM 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 SugarCRM 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 SugarCRM connection and its activities are referred to as a SugarCRM endpoint:

SugarCRM activity types

  • Get Contacts: Retrieves contacts from SugarCRM and is intended to be used as a source in an operation.

  • Delete Contacts: Deletes contacts from SugarCRM and is intended to be used as a target in an operation.

  • Create Contacts: Creates new contacts in SugarCRM and is intended to be used as a target in an operation.

  • Update Contacts: Updates existing contacts in SugarCRM 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 SugarCRM 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 SugarCRM connector uses the SugarCRM REST API. Refer to the API documentation for information on the schema nodes and fields.

Troubleshooting

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

  1. Ensure the SugarCRM 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 check the agent logs for more information.