Slack

Supports:

• ✅ Bulk sync source
• ✅ Connection Proxy

Overview

Polytomic connects to Slack using a Bot User OAuth Access Token. This requires first creating a Slack app

1. Go to the Slack App site.

2. Click Create an App.

3. Give the app a name and select the workspace you want to sync data from.

4. Click Create App.

5. Add the following OAuth Scopes to the list of Bot Token Scopes:

• channels:history
• channels:join
• channels:read
• files:read
• groups:read
• links:read
• reactions:read
• remote_files:read
• remote_files:write
• team:read
• useergroups:read
• users.profile:read
• users:read
• users:read.email

6. Install the app to your Slack workspace.

7. After successfully installing the app to your Slack workspace, use the resulting Bot User OAuth Access Token as the api_key value in your Polytomic Slack connection config.

Ingesting Slack events

If you want to ingest Slack’s real-time events using Polytomic’s Bulk Syncs, you’ll need to perform additional configuration in the Slack app you set up above after creating a Polytomic Slack connection.

1. Turn on the Enable Events switch in the Event Subscriptions section of your Slack app config:

2. Copy the Event Subscription Request URL (the read-only event_url value in the connection configuration) from your newly-created Polytomic Slack connection and paste it in the Request URL field above. You can also use your own URL as long as you implement a 301HTTP redirect to your Polytomic Slack connection’s event subscription request URL.

3. Click Add Bot User Event to specify the list of Slack events that Polytomic should ingest.

4. Once you’ve saved your new Slack application config, you’ll be able to add the collection Events to your Polytomic bulk sync config. You’ll then receive all Slack events you added in Step 3.

Connection

Configuration

Example

1
{
2
  "name": "Slack connection",
3
  "type": "slack",
4
  "configuration": {
5
    "api_key": "secret"
6
  }
7
}

Read-only properties

Bulk Sync

Source

Configuration

Example

1
{
2
  ...
3
  "source_configuration": {
4
    "message_lookback": 0
5
  }
6
}