Skip to Content

Gzip Connector


The Gzip connector provides an interface for creating a Gzip connection. That connection provides the foundation to configure associated Gzip activities that interact with the connection. Together, a specific Gzip connection and its activities are referred to as a Gzip endpoint.


The HTTP connection setting HTTP Accept Encoding Gzip and the SOAP connection setting Set Accept-Encoding to Gzip, which are used to automatically decompress Gzip-compressed responses returned by HTTP and SOAP activities, respectively, are unrelated to the Gzip connector.


The Gzip 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.

Connector Overview

This connector is used to first configure a Gzip connection, establishing access to the Gzip endpoint, and then used to configure one or more Gzip activities associated with that connection as a source or target within an operation:

  • Decompress: Decompresses a Base64-encoded string of Gzip-compressed data in a Gzip endpoint and is intended to be used as a source in an operation.

  • Compress: Compresses a string of content into a Base64-encoded string of Gzip-compressed data in a Gzip endpoint 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.

Accessing the Connector

The Gzip connector is accessed from the design component palette's Project endpoints and connectors tab (see Design Component Palette).



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

  1. 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).

  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.