Configure Slack as a Source in your Pipeline

Perform the following steps to configure your Slack Source:

1. Click Pipelines in the Navigation Bar.

2. Click + Create Pipeline in the Pipelines List View.

3. On the Select Source Type page, select Slack.

4. On the Select Destination Type page, select the type of Destination you want to use.

5. On the Select Pipeline Type page, click Edge, and then click Continue.

   

   This page appears only if the selected Destination type is supported in Edge and your Team has an existing Slack Pipeline with the same Destination type. Otherwise, you can proceed to create an Edge Pipeline.

6. In the Configure Source screen, specify the following:

   

   • Source Name: A unique name for your Source, not exceeding 255 characters. For example, Slack Source.

   • OAuth Token: The OAuth token that you generated for your Slack workspace.

7. Click Test & Continue to test the connection to your Slack Source. Once the test is successful, you can proceed to set up your Destination.

   When you click this button, Hevo validates that the OAuth Token field is not null or empty, and then makes a request to the Slack auth.test endpoint using the token provided. If the request confirms that the token is valid and the associated Slack workspace is active, the connection test is marked as successful. You can then proceed to set up your Destination.

---

Data Replication

Hevo replicates data for all the objects selected on the Configure Objects page during Pipeline creation. By default, all supported objects and their available fields are selected. However, you can modify this selection while creating or editing the Pipeline.

Selecting a parent object automatically includes all its associated child objects for replication. Child objects cannot be selected or deselected individually.

Hevo ingests the following types of data from your Source objects:

• Historical Data: The first run of the Pipeline ingests all available historical data for the selected objects and loads it into the Destination.

• Incremental Data: Once the historical load is complete, new and updated records for objects are ingested as per the sync frequency.

For the following objects, Hevo ingests only the incremental data in subsequent Pipeline runs:

• Message

• Message Reply

Incremental changes are detected using the ts timestamp field. The maximum ts value recorded in the previous Pipeline run is used as the oldest parameter in subsequent API calls to fetch only new and updated messages.

For all other objects, Hevo ingests the entire data during each Pipeline run.

Slack enforces per-method API rate limits. Depending on the API method used, rate limits range from approximately 20 requests per minute for metadata APIs to approximately 100 requests per minute for message history APIs. If a rate limit is exceeded, a rate limit exception occurs. To understand how Hevo handles such scenarios, read Handling Rate Limit Exceptions.

Note: You can create a Pipeline with this Source only using the Merge load mode. The Append mode is not supported for this Source.

---

Schema and Primary Keys

Hevo uses the following schema to upload the records in the Destination. For a detailed view of the objects, fields, and relationships, click the ERD.

---

Data Model

The following is the list of tables (objects) that are created at the Destination when you run the Pipeline:

---