Skip to Content

Smartsheet connector for Jitterbit Integration Studio

Summary

The Smartsheet connector establishes access to Smartsheet.

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

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

Connector overview

This connector is used to first configure a Smartsheet 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 Smartsheet connection and its activities are referred to as a Smartsheet endpoint:

Smartsheet activity types

  • Delete Sheet: Deletes a sheet from Smartsheet and is intended to be used as a target in an operation.

  • Import Sheet: Imports a sheet into Smartsheet and is intended to be used as a target in an operation.

  • Get Sheet: Retrieves a sheet from Smartsheet and is intended to be used as a source 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 Smartsheet 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 Smartsheet connector uses the Smartsheet API 2.0. Refer to the API documentation for information on the schema nodes and fields.

Troubleshooting

If you experience issues with the Smartsheet 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.

  5. For additional troubleshooting considerations, see Operation troubleshooting.