Slack is a popular cloud-based platform for team communication and collaboration. It is a messaging app that combines elements of instant messaging, email, and social media.

This technical documentation provides a comprehensive guide to integrating Slack with Nected. You will learn how to configure the Slack integration and perform operations and troubleshoot common issues.

By the end of this guide, you will have the knowledge to seamlessly connect Slack with Nected and leverage its capabilities for your applications.

Setting Up Slack Integration

To establish a connection between Nected and Slack for seamless data interaction, you need to configure a Slack integration. This section outlines the step-by-step process for setting up the integration effectively.

  1. Adding Integration: Select Slack from the integrations page. This choice initiates the process of setting up a integration for Slack.

  2. Configuring Connection Settings: The configuration of connection settings is a critical step in establishing the connection between Nected and your Slack account. The following parameters need to be defined:

    1. Environment Type: Choose whether you are configuring the integration for a "Staging" or "Production" environment. The selection of the environment type determines the context in which the connector will operate. By default, the environment type is set to “Staging”.

    2. Name: Assign a unique and meaningful name for the integration. It is essential that this name is distinct throughout the Nected platform and does not contain any spaces.

    3. IP Addresses for Allow-list: To enhance security, it's recommended to configure an allow-list of IP addresses. Ensure that Nected service IP addresses, such as "," are included in this allow-list to secure the connection.

    After this, click the Connect App button , you will be redirected to a webpage. Check permissions requested by the app. Grant if you agree.

  3. Test the Connection: After configuring the connection settings, it's crucial to test the connection to ensure that Nected can successfully communicate with the Slack App. This test verifies that the provided information is accurate and the connection is established without issues.

  4. Publishing in Staging: If the connection test is successful, you can proceed to publish the integration in the "Staging" environment. In this context, "Staging" refers to a development or testing environment. For a "Production" database, the option will be "Publish in Production." Publishing the connector in a specific environment enables you to set up rules and operations within that environment.

  5. Integration Status: After configuring and publishing the integration, it's essential to check the connector status. Close the connection information form and check the connector status. For a "Staging" environment, the status will be "staging," and for a "Production" environment, it will be "Production." Monitoring the status ensures that the integration is active and properly integrated into the selected environment.

Note: If using Nected cloud, Nected IP address ( must be added to the allow-list on your database server to secure your connections. Not required in on-premise setup

You need to publish staging and production connectors in their respective environments. If a connector is published only in staging, then it cannot be used in the production environment, and any call to rule in production environment will fail giving "connector not published in production" error will be shown


Here are some common troubleshooting steps and potential actions for your Slack integration in Nected:

Connection Issues:

  • Error: "Failed to connect to Slack"

    • Action: Double-check your connection settings, including environment type, integration name, and IP addresses in the allow-list. Ensure they match your Slack configuration.

    • Action: Verify that your internet connection is stable and Nected service IP addresses are accessible.

    • Action: If using Nected cloud, confirm the Nected IP address ( is added to your database server allow-list.

  • Error: "Unauthorized access"

    • Action: Ensure you granted the necessary permissions when connecting the app. Check your Slack app permissions and grant any missing ones.

  • Error: "Integration not published in the environment"

    • Action: Publish the connector in the correct environment (staging or production) depending on where you're testing or using it.

Testing and Publishing:

  • Error: "Test in Staging failed"

    • Action: Review the error message for specific details. Check your rule configuration, message content, and token validity.

    • Action: Ensure your Slack channel name is correct and the channel allows messages from the integration.

  • Error: "Publish failed"

    • Action: Verify you have the necessary permissions to publish connectors in the chosen environment.

    • Action: Check for any outstanding issues or limitations within your Nected environment that might prevent publishing.

Slack messages not sent:

  • Action: Confirm your message content and channel selection are correct.

  • Action: Check if your token has expired or lost permissions. Regenerate the token if needed.

  • Action: Ensure your Slack app is active and functioning properly.

Last updated