Jitterbit Harmony Slack Connector¶
The Jitterbit Harmony 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, establishing access to the Slack application, and then used to configure a Slack activity associated with that connection as a source or target within an operation.
If you used the Slack connector with projects prior to the Jitterbit Harmony Cloud Studio 10.23 release, you must reconfigure your connection as it no longer uses a webhook URL to connect and authenticate.
The Slack connector requires the use of an agent version 10.1 or later.
Together, a specific Slack connection and its activities are referred to as a Slack endpoint. Once a connection is configured, activities associated with the endpoint are available from the Endpoints filter:
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.
Create a Slack App¶
To use this connector with a Slack instance, you must create a Slack app and add the required scopes (as described in Slack Prerequisites).
After configuring a Slack connection, you can configure one or more Slack activities associated with that connection to use as a source or target within an operation. For more information, see these pages:
- Get: Retrieves table or view data from a Slack connection 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.
- Search: Finds messages at a Slack endpoint and is intended to be used as a source in an operation.
- Chat: Places chat information into a Slack endpoint and is intended to be used as a target in an operation.
- Files: Places file information into a Slack endpoint and is intended to be used as a target in an operation.
- Conversations: Posts an object into a Slack endpoint and is intended to be used as a target in an operation.
- Users: Places user information into a Slack endpoint and is intended to be used as a target in an operation.
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.
Enable operation debug logging (for Cloud Agents or for Private Agents) to generate additional log files and data.
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.