Sabaki Guide
Slack Headcount KPI Setup In Sabaki
How to connect Slack to Sabaki and sync active human workspace members into the Headcount KPI.
Slack headcount sync is the Sabaki workflow for reading active human members from a connected Slack workspace and writing that count into the monthly Headcount KPI.
Key Takeaways
- Slack sync counts active human members and excludes bots, deleted users, app users, and Slackbot.
- The synced value writes to the current monthly Headcount KPI snapshot.
- Slack pasted tokens do not refresh automatically; reconnect when the token is rotated or revoked.
How To Sync Slack Headcount
- Create or choose a Slack tokenUse a Slack token that can call workspace member listing and validate with Slack auth testing.
- Connect Slack in SabakiOpen Apps, choose Slack, paste the token, and save the connection.
- Run Sync NowUse the Slack connection row to start a manual sync.
- Check HeadcountOpen KPIs and confirm Headcount updated for the current month with app-backed provenance.
- Reconnect after token changesIf Slack reports invalid auth, create a new token and reconnect the app.
Quick Comparison
| Sabaki Output | Source Data | How Sabaki Treats It |
|---|---|---|
| Headcount | Slack workspace members | Counts active human users only |
| Sync status | Slack API response | Shows success, rate limit, or authorization failure |
| Source label | Connected Slack workspace | Marks the KPI row as connector-backed |
Frequently Asked Questions
Does Slack sync messages?
No. The current Slack connection is for workspace member count, not Slack message content.
Why is Headcount lower than my Slack member list?
Sabaki excludes bots, deleted users, app users, and Slackbot before writing the Headcount KPI.
Can Slack update historical months?
The current Slack sync writes the current monthly Headcount snapshot.
What should I do when Slack sync fails?
Check that the token is still valid and can read workspace members, then reconnect Slack in Sabaki if needed.