The Jitterbit Harmony Slack Connector establishes access to Slack.
The Slack connector provides an interface for creating a Slack connection, the foundation used for generating instances of Slack activities. These activities, once configured, interact with Slack through the connection.
The Slack connector is accessed from the design component palette's Connections tab (see Design Component Palette).
This connector is used to first configure a Slack 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 Slack connection and its activities are referred to as a Slack endpoint:
Search: Finds messages in Slack and is intended to be used as a source in an operation.
Post: Posts an object into a Slack channel and is intended to be used as a target in an operation.
Chat: Places chat information into Slack and is intended to be used as a target in an operation.
Get: Retrieves object data from Slack and is intended to be used as a source in an operation.
Files: Places file information into Slack and is intended to be used as a target in an operation.
Conversations: Posts conversations information into Slack and is intended to be used as a target in an operation.
Users: Places user information into Slack 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 Slack 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 Slack connector uses the Slack REST API. Refer to the API documentation for information on the schema nodes and fields.
To use this connector with a Slack workspace, you must create a Slack app and add the required scopes (as described in Slack Prerequisites).
If you experience issues with the Slack connector, these troubleshooting steps are recommended:
Ensure the Slack 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.
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.slack" level="DEBUG"/>
If using Private Agents, you can check the agent logs for more information.