Hey everyone! I've been lurking for a bit and finally decided to post. I'm trying to get my team to use Le Chat for some research and brainstorming tasks, but we live in Slack. Like, *everything* happens there—project updates, standups, file sharing, you name it.
I've seen that Le Chat has some kind of Slack integration, but I'm a bit lost on how to actually make it useful. I don't just want another bot that spams the channel. For example, can I use Le Chat to summarize a long thread in Slack and post the summary? Or maybe draft a project brief based on a conversation and post it back to a specific channel?
Basically, how are you all connecting Le Chat to your actual day-to-day Slack workflows? Are you using it as a custom slash command, or through Zapier/Make? Any simple examples or gotchas would be super helpful. I'm still pretty new to this kind of automation, so the simpler the explanation, the better 😅
Thx!
Before you get too deep, check if the integration is free. Their basic Slack bot might only let you ask it questions, not summarize existing threads. The useful features often sit in a higher pricing tier.
You mention Zapier/Make - that's where the real TCO hits. Now you're paying for Le Chat *and* automation platform credits. The per-user cost balloons fast.
For simple stuff, try the native /slash command first. It's probably limited, but at least you'll see what you're missing before you commit.
always ask for a multi-year discount
The native integration is indeed limited, mostly exposing the chat interface within Slack. For the workflows you described, like summarizing a long thread, you're looking at custom development.
The core blocker is Slack's API. To summarize a thread, you must first programmatically fetch that thread's history, which requires the appropriate scopes and handling pagination. Then you send that text to Le Chat's API, and finally post the result back. This isn't a simple "turn on" setting.
You have two main architectural paths, each with a significant trade-off:
1. A custom Slack app using Bolt.js or similar, with a backend service calling the Le Chat API. This gives you full control but requires hosting, monitoring, and maintenance.
2. A no-code platform like Make or Zapier. The gotcha here, beyond cost, is data throughput. A long thread can easily exceed the payload limits for a single automation step, forcing you to implement chunking logic within the no-code tool, which defeats its simplicity.
For a proof of concept, try building a single slash command that summarizes the last 50 messages in the channel it's invoked in. That'll expose the data and latency challenges immediately.
Show me the numbers, not the roadmap.
That point about payload limits for no-code tools is a serious one. I hadn't considered the size of a thread just breaking the automation step.
It sounds like the "proof of concept" you suggest is the only real starting point. But is fetching the last 50 messages, even for a test, something a typical team admin can do without a developer? It feels like you'd already need to build the custom Slack app just to run that test, which is a high barrier for a trial.
You're right about the native integration being basically a chat window. For thread summaries specifically, the Zapier/Make route gets expensive fast once you factor in platform costs on top of Le Chat. Not to mention, you'll blow through step limits if a thread is long.
One dirty, cheap hack we've used? The bookmark app. Save the thread as a bookmark, generate a share link, and paste *that* into Le Chat's web interface. It's a manual step, but the models are decent at pulling content from public links. Lets you test the output quality before you sink time into building a bot.
If you do go custom, start with a simple slash command that just sends the *last* message to Le Chat. It's a tiny scope that still feels magical and proves the concept without needing pagination.
- elle