Nected Docs
Try Nected For Free
  • 5 min QuickStart Guide
  • Getting Started
    • Introduction
    • Core Concepts
    • Use Cases
    • Tech Architecture
    • FAQs
  • INTEGRATIONS
    • Overview
    • Integrations Libraries
      • PostGres
      • MySQL
      • Oracle
      • MS SQL Server
      • Snowflake
      • MongoDB
      • RedShift
      • REST API
      • Google Sheets
      • Slack
    • Managing Integrations
  • DATASETS
    • Overview
    • Managing Dataset
  • Rules
    • Overview
    • Rule Types
      • SimpleRule
      • DecisionTable
      • Ruleset
      • Rule Chain
    • Rule Conditions
    • Rule Actions
    • Concepts
      • Rule Result
      • Test & Publish Rules
    • Add Input Attributes
      • JSON Input Attributes
      • List Input Attributes
  • Triggers
    • Trigger Rule via API
    • Trigger Rule via WebHook
    • Trigger Workflow via API
    • Trigger Workflow via WebHook
    • Scheduler
    • Rule Response Format
  • Workflow
    • Overview
    • Managing Workflow
    • Add Node
      • Action Nodes
        • Rule Node
        • Workflow Node
        • Custom Code Node
        • Database Node
        • REST API Node
      • Control Nodes
        • Loop Node
        • Delay Node
        • Response Node
        • Set Variables Node
        • Switch Block
    • Test & Publish Workflows
  • CODE AND DATABASE QUERIES
    • JavaScript Editor
    • Formula Editor
    • JSON Editor
    • List Editor
    • Excel-like Function
  • Embedded System
    • White-Labelling
    • Embeddable View
  • Security
    • API Authentication
      • OAuth as part of Authentication under REST API
    • Role Based Access Control (RBAC)
    • On Premise Deployment
    • SOC 2 Type 2, GDPR, ISO Compliance
  • Audit
    • Audit Trail
    • Approval Flow
    • Version Control & Rollback
    • Import/Export
  • Management API
    • Audit Log API
    • Global Variable API
  • References
    • Attribute Library
    • Global Variables
    • Pre-Configured Tokens
    • Pre-Configured Operators
    • NULL Value Handling/Behavior
    • Troubleshooting Errors
      • Multiple Tabs/Users Edits
      • Limits in Nected
    • Allowed Status Combinations
    • Environments
    • Usage Widget
    • Gen AI
Powered by GitBook
On this page
  • Overview
  • Setting Up Slack Integration
  • Trigger Slack as Action
  • Troubleshooting
  1. INTEGRATIONS
  2. Integrations Libraries

Slack

PreviousGoogle SheetsNextManaging Integrations

Last updated 7 months ago

Overview

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 . 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 "43.205.43.45," 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 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.

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

Trigger Slack as Action

Triggering a Slack as an action is simple. Follow these steps:

  1. Click on the "+Add Action" button and it will open the below list. Choose Slack from the options.

  2. After selecting the Slack, there are two options:

    1. Add from List: From the available list, choose one.

    2. Create new Connector: Click on the "+Slack" and it will take you to the integration page, on a new tab. Then follow the same steps to create a new connector and then come back to the rule editor. Then click on the refresh button and the new connector will be appear in the list. Click on the connector which will open a tab like this:

  3. Now select the method from the dropdown: "Send Slack Message".

  4. Then select the channel, add message that you want to send, and select the token type to either user token or bot token.

  5. Once all these are done, then simply save it and you'll be good to go with the action.

Troubleshooting

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 (43.205.43.45) 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.

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

on-premise setup
integrations page
connector status.