Skip to Content

Active Campaign Connector

Summary

The Jitterbit Harmony Active Campaign Connector establishes access to Active Campaign.

The Active Campaign connector provides an interface for creating an Active Campaign connection, the foundation used for generating instances of Active Campaign activities. Activities interact with Active Campaign through the connection and are intended to be used as sources (to provide data in an operation) or targets (to consume data in an operation).

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

Note

This connector can be used only with Private Agents. In addition, it is a Connector SDK-based connector, which may be referred to by Jitterbit when communicating changes made to connectors built with the Connector SDK.

Connection Documentation

See Jitterbit's comprehensive Active Campaign connection documentation, which is provided at a dedicated website. Configuration details such as these are included:

  • Getting Started: Initial steps for establishing a connection.
  • Advanced Features: User-defined views and SSL configuration.
  • Data Model: The data model that the connector uses to represent the endpoint.
  • Advanced Configurations Properties: Properties that can be defined to configure the connection for both basic and advanced configurations.

Activity Documentation

Together, a specific Active Campaign connection and its activities are referred to as an Active Campaign endpoint:

Active Campaign activity types

  • Query: Retrieves records from a table at Active Campaign and is intended to be used as a source in an operation. (Generically documented in Query Activities.)

  • Create: Inserts a record into a table at Active Campaign and is intended to be used as a target in an operation. (Generically documented in Create Activities.)

  • Update: Updates a record in a table at Active Campaign and is intended to be used as a target in an operation. (Generically documented in Update Activities.)

  • Delete: Deletes a record from a table at Active Campaign and is intended to be used as a target in an operation. (Generically documented in Delete Activities.)

  • Execute: Executes a procedure at Active Campaign and is intended to be used as a target in an operation. (Generically documented in Execute Activities.)

Prerequisites and Supported API Versions

The Active Campaign 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.

This connector requires the use of a Private Agent.

Refer to the documentation for information on the schema nodes and fields.

Troubleshooting

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

  1. Ensure the Active Campaign 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 Private Agents to generate additional log files and data.

  4. Enable connector verbose logging for this connector using this specific configuration entry of logger name and level:

    <logger name="org.jitterbit.connector.verbose.logging.ActiveCampaign" level="TRACE"/>
    
  5. Check the agent logs for more information.