FlowTask is a Company Brain for AI agents. Connect WhatsApp, Slack, and Gmail it structures your fragmented company knowledge into a live, always-updated memory that any AI agent can access simultaneously via MCP. With an approval layer on top, you control what enters the brain personal chats stay personal, wrong signals get filtered. No more re-explaining your company to Claude and ChatGPT every morning. No more stale CLAUDE.md files. Free to start. No API key needed.
This is the 4th launch from FlowTask. View more
FlowTask 2.0
Launching today
Company Brain for AI agents, Fragmented communication and data of a company which is left on channels Emails, Slacks, WhatsApp and LinkedIn connect it all in one place with approval layer attach so personal and works chats don't gets mixed and connect it with any ai agents simultaneously, where records are keep getting updated minutes by minutes and so AI agents are getting updated as well so use AI agents with less cost of context and don't have to repeat.
Free Options
Launch Team
FlowTask
A company brain for AI agents (the question is why)
So I posted one simple question on Reddit about a frustration I have while using AI.
got 8.5k views in 5hrs with 45+ comments
Almost nobody said the problem didn't exist, instead everyone shared their own workaround.
Some use Chatgpt Projects. Some maintain PROJECT.md or CLAUDE.md files.
Some build knowledge graphs. Some create automation pipelines with n8n or Zapier.
Some use RAG connectors and custom memory systems.
The pattern was surprisingly consistent.
The real problem is Claude doesn't know what's happening minute to minute people said use an API or connect it manually. But then you're still feeding it everything including the useless stuff so we added an approval layer you decide what goes to AI combined with MCP, no need for Make, Zapier, or n8n it just works.
And what's the output
AI agents 10x better, knows what's happening minutes by minutes + no daily updates
The "approval layer so personal stays personal" line is the part I'd want to understand more. Once Slack, WhatsApp and Gmail are all feeding the same brain and any agent can read from it via MCP, is the approval/redaction happening per-source before it ever enters the brain, or per-agent at query time? Asking because those give very different guarantees — one keeps sensitive stuff out entirely, the other trusts every agent to respect scope once it's already in.
Congrats on the launch. The approval layer is the part I like most — most tools that pull from Slack and WhatsApp just take everything, so personal and work chats get mixed. Letting you decide what actually enters the brain is a smart call.
One thing I keep thinking about: when the memory updates every few minutes from so many channels, how do you handle facts that go stale or contradict each other? Like a decision made in Slack last week that gets reversed today — does the brain catch that on its own, or does someone have to approve the change?
both the Google Workspace and Slack connectors are broken which means there's no way to actually proceed into the app and try it out. bit disappointing and not a great experience for new potential customers
Voquill
I like that you're tackling the context problem instead of trying to cram more data into the model. Congrats on the launch!