Slace
Version 0.0.0
Check out the Slace documentation for more information
Set up
To use the connector you need a Slace Service Account access token (information on how to generate one is available here).
Create the service account under a dedicated integration user, as the token stops working if that user is deactivated. Login tokens expire after 15 minutes and will not work.
Features
| Feature | Support | Notes |
|---|---|---|
| Backfill | ✅ | 3 days to 24 months for Messages. Conversations, Contacts and Channels are always a full extract. |
| Incremental | ✅ | Messages only, when the load method is Append. Conversations, Contacts and Channels are full snapshots. |
| API Reliability | 🟠 | The API has a known limitation that can result in missing rows (Get Conversations and Get Messages) |
Reports detail
| ⬇️ Report | 🔑 Incremental key | 🔑 Primary key | 📄 Link to API endpoint |
|---|---|---|---|
| Channels | N/A | id | GET /core/channels (not in the public documentation) |
| Contacts | N/A | id | List contacts |
| Conversations | N/A | id | Get conversations |
| Messages | timestamp | id | Get messages |
Limitations
Risk of missing rows (ConversationsandMessagesreports)Due to the way pagination is implemented on the API, rows that share exactly the same timestamp as the cursor used for paginating the results (
last_msg_atfor conversations,timestampfor messages) may be skipped on page boundaries. This can result in missing conversations or messages from connector runs. This is a known limitation on the API side.
Conversations withoutlast_msg_atvalue are not extractedThe API paginates conversations on
last_msg_at, so conversations where that field is empty cannot be paged through and are excluded from theConversationsreport. Any messages such conversations might hold are missing from theMessagesreport as well, since messages are fetched per extracted conversation.
Updated about 8 hours ago