Cross-tool integration
Cross-tool integration
SlackBuzz is designed as the glue between Slack, ClickUp, and GitHub CLIs. It detects references to other tools in your Slack messages and provides actionable hints.
The digest command
The digest command combines activity from all three tools in a single view:
$ slackbuzz digest
SLACK -- 3 unread mentions @alice in #dev "Can you review PR #42?" 2h ago @bob in #backend "CU-abc needs your input" 5h ago @sarah DM "meeting at 3?" 1d ago
CLICKUP -- 2 tasks assigned to you CU-abc123 In Review API redesign CU-def456 In Progress Deploy pipeline fix
GITHUB -- 1 PR needs your review #42 feat: add caching layer alice +120 -30
---Quick actions: slackbuzz message send #dev "reviewing now" clickup task update CU-abc123 --status complete gh pr review 42 --approveHow it works
The digest shells out to the clickup and gh CLIs if installed:
- Slack: Uses
search.messagesAPI to find your recent mentions - ClickUp: Runs
clickup task list --assignee me --jsonto find your assigned tasks - GitHub: Runs
gh pr list --review-requested=@me --jsonto find PRs needing review
Sections are gracefully skipped if a CLI is not installed (exec.LookPath).
Flags
slackbuzz digest --since 2d # Look back 2 days instead of defaultslackbuzz digest --slack-only # Only show Slack sectionslackbuzz digest --clickup-only # Only show ClickUp sectionslackbuzz digest --github-only # Only show GitHub sectionslackbuzz digest --json # Structured outputEnrichment in activity views
The activity and threads commands auto-detect cross-tool references in message text:
ClickUp task IDs
The regex CU-[a-z0-9]+ is detected in message bodies. When found, slackbuzz shows an actionable hint:
@mention bob #backend 5h ago CU-abc123 needs your input on the API design -> clickup task view CU-abc123GitHub PR/issue URLs
URLs matching github.com/.../pull/\d+ or github.com/.../issues/\d+ are detected:
@mention alice #engineering 2h ago Can you review? https://github.com/org/repo/pull/42 -> gh pr view 42Slack deeplinks
All activity and message views include clickable deeplinks that open items directly in the Slack desktop app. In terminals that support OSC 8 hyperlinks, timestamps and channel names are clickable.
Deeplink format: slack://channel?team=TEAM_ID&id=CHANNEL_ID&message=TIMESTAMP
Workflow example
A typical morning workflow combining all three tools:
# 1. Check what needs attention across all toolsslackbuzz digest
# 2. Read the thread that mentions a ClickUp taskslackbuzz message list #backend --thread-ts 1706000000.000000
# 3. Check the ClickUp taskclickup task view CU-abc123
# 4. Reply in Slackslackbuzz message send #backend "On it, updating the API now" --thread-ts 1706000000.000000
# 5. Update the ClickUp task statusclickup status set "in progress"
# 6. React to acknowledgeslackbuzz react #backend 1706000000.000000 :eyes:
# 7. Save a message for later follow-upslackbuzz later add #backend 1706000000.000000Required CLIs
| Tool | Install | Used by |
|---|---|---|
| slackbuzz | brew install triptechtravel/tap/slackbuzz | Core Slack operations |
| clickup | brew install triptechtravel/tap/clickup | digest ClickUp section, task ID enrichment hints |
| gh | brew install gh | digest GitHub section, PR URL enrichment hints |
All three CLIs store credentials in the system keyring and support --json output for programmatic access.