Levee for Slack

A daily digest from your Slack and Jira backlog with AI-drafted replies. Levee reads your unread mentions and DMs, summarises each conversation, and posts one message a day to your @Levee app DM with a draft you can edit and send.

You'll be redirected to Slack to sign in and approve the app. By installing you agree to the Terms of Service and Privacy Policy.
Already a Levee user? Connect from your account.
Looking for Jira? See /install/atlassian.

Levee App

Levee daily digest — Sat, May 9, 6:00 PM

3 conversations need your reply · 2 mentions · 1 DM

Sara Mohamedin #engineering · 4 messages

Asking when you'll review the API freeze RFC, with follow-ups about timeline.

Suggested reply: Thanks for the bump. I'll review by EOD tomorrow and post specific feedback in-thread.

Abdullah Adelin DM · 2 messages

Wants confirmation on the GCC vendor short-list before sending to procurement.

Suggested reply: Confirmed — proceed with the three vendors we discussed. I'll send the rationale separately.

Mohamed Rafatin #ops

Flagged Caddy config drift on staging.

Suggested reply: Looking into it now. Let's sync at 4pm if I can't reproduce.

What you get

One message a day

Every morning Levee posts a single, scannable digest into your @Levee app DM — no more 30-channel sweep.

AI-drafted replies

Each conversation gets a one-sentence summary plus a suggested reply. Edit the draft, click Send, the reply lands in the original thread.

Snooze and triage

Open the levee dashboard for the full Slack and Jira queue: "needs your reply", "follow-ups", overdue, stuck. Press ⌘K to search across everything.

What permissions Levee asks for

Granular by design.

Levee uses two token types: a bot token (so the daily digest comes from @Levee, not your own account) and a user token for searching your messages and posting replies on your behalf. Every scope below maps to one specific feature; nothing is collected speculatively.

Bot token @Levee

chat:write

Post the daily digest as @Levee in your app DM.

im:history

Read the bot ↔ user DM so we don't re-send items you've already actioned by replying inside that thread.

im:read

Look up the channel ID of the bot ↔ user DM to know where to post.

User token on your behalf

search:read

Find your unread mentions and DMs from the last 48 hours — the input for the digest.

chat:write

Post your edited reply back into the original thread when you click Send in the levee dashboard.

channels:history · groups:history · im:history · mpim:history

Read the surrounding messages of each conversation so the AI summary captures full context, not just the trigger message.

users:read

Resolve user IDs into display names so the digest reads "Sara replied" instead of "U07ABC123".

im:write

Open a DM channel with you (used as a fallback if the bot token isn't available).

FAQ

Where's my data stored?

On a single server we control. All Slack and Jira tokens are encrypted at rest with AES-256-GCM. We don't sell, share, or run analytics on your data. Full privacy policy →

Can I uninstall?

Yes, anytime. Click Remove on /connections or uninstall the app from your Slack workspace. Both delete the encrypted token from our database immediately.

Does Levee read every Slack message?

No. We only fetch messages that match your unread mentions or DMs from the last 48 hours, plus their immediate thread/channel context for AI summarisation. Nothing is indexed long-term.