01
What was decided
Ask what the platform channel decided about retries and get the decision, who made it and when, without reading three hundred messages.
Slack + Memtro
Search messages, read channel history and threads.
Decisions live in Slack. Search messages, list channels, read history and threads, and let extraction turn what was decided into memory.
What you can do with Slack in Memtro
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Slack tool, reads what it needs, and answers with the source cited.
02
Find the thread you half remember
Search by topic and people, then read the replies in order and save the conclusion to shared memory.
- Search messages
- List channels, read channel history and a thread
Ask it like this
Questions people ask once Slack is connected. In agent mode each one also checks the other systems that know about the same people, companies or identifiers.
- ›What did we decide about retries in #payments?
- ›Find the thread where the launch date moved
Where it fits
Teams that get the most from Slack in Memtro, with the rest of their stack attached.
- SupportAnswer tickets with the whole company behind youSupport teams spend their day switching tabs: the ticket in Help Scout, the customer in the CRM, the order in the warehouse, the invoice in Xero. Memtro reads the ticket and does the switching for them.
- SalesWalk into every call briefedAccount history, open tickets, invoices, the last email thread and what was decided internally, pulled together from the systems that hold them and remembered for next time.
- LeadershipOne question across the whole companyFounders and managers ask what is happening and get an answer stitched from support, sales, finance and engineering, with every figure traced to its source and the rest of the week handled by jobs.
- OperationsMonitors and digests that run themselvesJobs are prompts the agent runs on a schedule with the same tools as their owner. Create them in plain language, get the report in a chat, pause or change them in a sentence.
Better together
A record in Slack is rarely the whole story. Connect the systems that hold the rest and the agent cross-references them by default, then remembers what it learned so the next question starts further along.
Also in Email, calendar and chat
Using something else for the same job, or both? Each connector has its own tools; connect as many as you like.
How to connect
- 01Paste a user token on Dashboard → Connections → Slack, or use Sign in with Slack where configured
Also works from
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Slack tools are the same everywhere.
Clients and agents →Questions
- Can Memtro change anything in Slack?
- No. The Slack connector is read-only: every tool reads, searches or lists. Nothing is created, sent, updated or deleted, and the credentials you give it should be read-only too.
- Who can use a Slack connection?
- A personal connection serves only your own requests. A shared connection serves the organisation: everyone, or only the teams an admin chooses. Admins can always add shared connections; other members need the permission.
- Does Memtro store my Slack data?
- Credentials are encrypted at rest. Tool results are cached briefly so agent loops do not repeat identical calls, and the facts the model extracts are saved to your organisation's memory with provenance (system, record and link) so they can be checked and superseded.
- How do I connect Slack?
- User token or OAuth. Paste a user token on Dashboard → Connections → Slack, or use Sign in with Slack where configured.
Connect Slack in a few minutes
Seven-day free trial, then one monthly price per organisation. Connectors, jobs and memory are never metered.