Find the thread where we decided how to handle duplicate refund webhooks — `in:#engineering has:link from:@rob after:2025-11-01`
Slack app install · Live
Find the message you half-remember.
Install the Lumen Slack app and the agent can search your workspace's messages with native Slack modifiers — `in:#channel`, `from:@user`, `after:YYYY-MM-DD`, `has:link`.
- Auth
- Slack app install (bot token)
- Access
- Read-only message search
- Plan
- Every plan
- Freshness
- Live — every search hits Slack's `search.messages` API
- Available on
- Every plan
Examples
Questions teams actually ask.
The tools it pulls from are shown inline — every answer in Lumen cites the underlying records it read.
Who's had the "how does cost attribution work" conversation before, and what did we tell them?
What's every Slack mention of the word "churn" in #cs-escalations over the last 30 days?
Pull every message from @sam where they linked to a Notion doc in the last week.
Preview
See what the answer looks like.
Toggle the tools Lumen is allowed to use. The plan, answer, and cited sources update to match.
How did we decide to cap refunds last quarter?
- slack.searchMessages — `refund cap in:#finance in:#engineering after:2025-10-01 before:2025-12-31`
- sort by score; look at top 10 matches
- open the highest-score permalink for the thread where the decision landed
The decision came out of a finance ⇄ engineering thread on 12 Nov. Consensus was a $200 per-order, $2000 per-day, per-user cap, with human approval above that. Permalink: slack.com/archives/C.../p... · three follow-up messages added context.
- [1]slack.searchMessages — 47 matches in #finance + #engineering
- [2]slack.searchMessages — top 3 threads ranked by relevance
Scope
What Lumen sees. What it can change.
Read is on by default. Every write is a separate toggle, capped per user, and logged.
What Lumen reads
Lumen calls Slack's `search.messages` endpoint with the bot's access. Results are scoped to whatever the bot user can see — typically public channels plus any private channel the bot has been invited to.
- Message search
Supports Slack's native modifiers: `in:`, `from:`, `has:link`, `has:file`, `after:`, `before:`
- Result metadata
Includes channel name, user, timestamp, and permalink for every match
What Lumen can write
Lumen does not post to Slack today. No message sending, no channel posts, no DMs. Posting Lumen answers back into a thread is on the roadmap as an opt-in per-channel action.
Every search is logged with user, the query string (including modifiers), and the match count. Exportable as CSV.
Install
Connect in under a minute.
No keys, no call, no app marketplace fine print.
- Install01
Add to Slack
In Settings → Integrations → Slack, click Add to Slack. You'll land on Slack's install page where you approve the bot scopes. Lumen stores the bot token encrypted and enforces one workspace per Lumen org.
- Invite to channels02
Let the bot see what it should
By default, bots can only see public channels. If you want the agent to search a private channel, `/invite @Lumen` in that channel. Revoking is as simple as `/kick` — the bot's search scope shrinks immediately.
- Ask03
Try a search
Start with "Find any mention of the word X in #channel this month." The agent will pick modifiers automatically and return the top matches with permalinks.
Questions
Frequently asked.
Can Lumen post back into Slack?
What channels can Lumen see?
Does Lumen store my Slack messages?
Can I connect multiple workspaces?
What happens if the token is revoked?
Can I scope the bot to specific channels?
Add Lumen to Slack. Find anything.
Standard Slack app install. Read-only. One workspace per org.