DLHDLH.io Documentation

Slack

DLH.io documentation for Slack

Slack's unique instant message and collaboration platform provides millions of users with communication capabilities that make moder work possible. DLH.io connects to your Slack workspace to help consolidate data from your Slack account to other data used within your organization to create a holistic view as well as aiding in secondary upstream and downstream data integration requirements.

Slack can be both a Source connection and a Target connection in DLH.io. Please understand the differences and see the instructions for Target Connection when using Slack as a target for sending data, etc. to one of your Slack channels.

Connector Pre-Requisites

Connecting to Slack, you need to make sure that:

  • You have administrative access to connect to your Slack account/workspace:
    • Since you are connecting to Slack with your individual user, you will see all of the public and private channels where you are a member
    • If your permissions change in Slack where you (or the person who initially created the Source/Target Connector in DLH.io) no longer have access to Slack or the Slack channel that was initially configured, reauthorize the Source/Target Connector in DLH.io and choose the appropriate Slack channel.

Instructions (Basic Connection Setup)

Remember DLH.io securely connects to your Slack instance by redirecting you to the Slack portal for you to sign in via your Slack login. DLH.io does not capture or store your password/credentials. Please remember that DLH.io will only list the public & private channels that your individual Slack user has access to in Slack.

Using the form please complete the following basic steps:

  1. Enter a Name or Alias for this connection, in the Name/Alias field, that is unique from other connectors.

  2. Enter in the Target Schema Prefix field, a name that will be unique in your target destination where you wish to integrate the data.

  3. Click the Authorize Your Account button which will transport you to the Slack login, where you will enter your Slack account credentials.   Once your credentials are accepted you will be automatically redirected back to this DLH.io portal and you should be able to see a successful connection.

Source Replicated Entities

The following entities are replicated by defualt to your Target Connection. These are the table names you will see in your Target Connection or available to your target integration. If you believe any entities/tables are missing please open a ticket with Customer Support:

  • View a list of entities after creating a connection in DLH.io for the most up-to-date list

Data Replication Details

This section provides information on how data is replicated, at what frequency and which replication/synchronization details are worth noting from DLH.io.

Replication Frequency ConfigurationsDetails
Default Replication Frequency24 Hours
Minimum Frequency1 Hour (lower on Business Critical plan)
Maximum Frequency24 Hours
Custom Frequency1-24 Hours

Replication Definitions

The following types of replication happen between this source and your target destination cloud data warehouse of choice when a Sync Bridge runs:

  • Historical Data Load (also First Time Sync)

    • Occurs during the first/initial data sync of the sync bridge pipeline and any time you need to or are requested to conduct a historical re-sync process for your data.
    • Here, DLH.io ingests all available data for the objects/tables you've selected or are available to you from the source based on your authentication access on that source.
    • This can take a relative elongated time to retrieve all data from the source and replicated to the target, as the name suggest it is retrieval all data, so if the source contains large amounts of data even in our parallel processing capability a customer could expect more than an hour for large data system. If there are any concerns that a historical load or first time sync has not completed within a reasonable amount of time please contact DLH.io Support.
  • Incremental (aka Deltas) Data Load

    • After a first time synchronization/replication or a historical data load, all subsequent processes of replicating the data for a Sync Bridge (source to target) are referred to as delta or incremental loads
    • Here, DLH.io captures the latest/newest records and/or events and any changes/updates to existing records and/or events in the source connector based on the frequency set in the Sync Bridge.

Issue Handling

If any issues occur with the authorization simply return to the sources page in DLH.io, edit the source details and click the Save & Test or Authorize Your Account or Re-Authorize Account button to confirm connectivity. If any issues persist please contact our support team via the DLH.io Support Portal.