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 | ✅ | 1 day to 6 months for Messages. All other reports are always a full extract. |
| Incremental | ✅ | Messages only, when the load method is Append. All other reports are full snapshots on every run. |
| API Reliability | 🟠 | Known limitations can result in missing rows on Messages: page-boundary ties, and WhatsApp history syncs that Append does not capture (see Limitations) |
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 |
| Gateways | N/A | id | GET /core/gateways (not in the public documentation) |
| Interactions | N/A | id | GET https://interactions.slace.com/v1/channels/{channel_id}/interactions (not in the public documentation) |
| Messages | timestamp | id | Get messages |
| Users | N/A | id | GET /core/users (not in the public documentation) |
Limitations
Risk of missing messages (Messagesreport)Due to the way pagination is implemented on the API, messages that share exactly the same
timestampas the cursor used for paginating the results may be skipped on page boundaries. This is a known limitation on the API side.
Use a short backfill on large accounts (Messagesreport)The longer the backfill window, the more conversations and messages a run has to fetch, and the longer it takes. If your account has a high volume of conversations or messages, first start and test with a short backfill such as 1 day or 7 days and extend it later if you need more history.
Messages synced late by the messaging provider (Messagesreport)Slace has confirmed that the messaging provider can deliver messages out of order during synchronisation, so a message can be stored after newer ones while keeping its original, earlier
timestamp. Incremental (Append) runs only fetch messages newer than the newest one already loaded, so such a message can be missed. A periodic full reload of the recent period covers this.
Message history synced by WhatsApp is not picked up by Append (Messagesreport)When a phone number is connected to Slace for the first time, or reconnected after being offline, WhatsApp (Meta) sends Slace that number's message history from the last 6 months. Slace stores these messages with their original dates, so they are older than the newest message already loaded and Append runs do not pick them up. The sync can take several hours. After connecting or reconnecting a number, wait for the sync to finish, then run the report once with Drop, Create, Load or Truncate, Load and a 6-month backfill to load the history.
Updated 13 days ago