The Harmony Intelipost Connector establishes access to Intelipost.
The Intelipost connector provides an interface for creating an Intelipost connection, the foundation used for generating instances of Intelipost activities. These activities, once configured, interact with Intelipost through the connection.
The Intelipost connector is accessed from the design component palette's Connections tab (see Design Component Palette).
This connector is used to first configure an Intelipost 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 Intelipost connection and its activities are referred to as an Intelipost endpoint:
Read: Retrieves object data from Intelipost and is intended to be used as a source in an operation.
Create: Creates object data in Intelipost and is intended to be used as a target in an operation.
Update: Updates object data in Intelipost and is intended to be used as a target in an operation.
Delete: Deletes object data from Intelipost 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 Intelipost 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 Intelipost connector uses the Intelipost API. Refer to the API documentation for information on the schema nodes and fields.
If you experience issues with the Intelipost connector, these troubleshooting steps are recommended:
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).
Check the operation logs for any information written during execution of the operation.
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.verbose.logging.intelipost" level="DEBUG"/>
If using Private Agents, you can check the agent logs for more information.