Jitterbit Harmony Constant Contact Connector¶
Overview¶
The Jitterbit Harmony Constant Contact Connector is accessed from the design component palette's Connections tab (see Design Component Palette).
This connector is used to first configure a Constant Contact connection, establishing access to an account on the Constant Contact server, and then used to configure one or more Constant Contact activities associated with that connection as either a source or target within an operation:
-
Query Activity: Retrieves contacts from a Constant Contact connection and is used as a source in an operation.
-
Create Activity: Creates new contacts at a Constant Contact connection and is used as a target in an operation.
-
Update Activity: Updates an existing contact at a Constant Contact connection and is used as a target in an operation.
-
Delete Activity: Deletes an existing contact at a Constant Contact connection and is used as a target in an operation.
The Constant Contact connector uses the Constant Contact Java SDK. Refer to the SDK documentation for information on the schema fields.
The Constant Contact connector requires the use of an agent version 10.1 or later.
Together, a specific Constant Contact connection and its activities are referred to as a Constant Contact endpoint. Once a connection is configured, activities associated with the endpoint are available from the Endpoints filter:
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.
Constant Contact Registration¶
As the connection will be an application that interfaces with Constant Contact, you will need to register at Constant Contact as a developer and create a Constant Contact application using the Constant Contact API. See Constant Contact Registration for details.
Troubleshooting¶
If you experience issues with the Constant Contact connector, these troubleshooting steps are recommended:
-
Ensure the Constant Contact 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.
-
Check the operation logs for any information written during execution of the operation.
-
Enable operation debug logging (for Cloud Agents or for Private Agents) to generate additional log files and data.
-
If using Private Agents, you can check the agent logs for more information.