Slack
Messaging
Read your Slack workspace so Ruby can search messages, catch up on a channel, and read threads by job.
Ask Ruby
5 read-only tools
Ruby reads from Slack and grounds her answers in your data. Every tool is read-only: she surfaces, summarizes, and drafts; a human always takes the action.
Search messages
Search the connected Slack workspace for messages using Slack's native search syntax and return matching messages. This searches across every channel and DM the connected account can see. Use it to answer 'what did the team decide about <job>', 'find the thread about the adjuster', 'did anyone mention <claim number>', and to feed the Communication Gap Detector. Use SLACK_FETCH_CONVERSATION_HISTORY to read a channel in order and SLACK_FETCH_MESSAGE_THREAD_FROM_A_CONVERSATION to read a thread's replies.
List all channels
List the channels in the connected Slack workspace (public channels, plus any private channels / DMs / group DMs the connected account is a member of) with their channel ids. Use it to resolve a channel name to the channel id you pass to SLACK_FETCH_CONVERSATION_HISTORY.
Fetch conversation history
Read the recent messages from one Slack channel (or DM) in chronological order, given its channel id (from SLACK_LIST_ALL_CHANNELS). Returns only main-timeline messages; a parent message's threaded replies are fetched separately with SLACK_FETCH_MESSAGE_THREAD_FROM_A_CONVERSATION using its thread_ts. Use it to catch up on what's been said in a channel.
Fetch message thread from a conversation
Read all replies in one Slack thread, given the channel id and the parent message's timestamp (the thread_ts from a SLACK_FETCH_CONVERSATION_HISTORY or SLACK_SEARCH_MESSAGES result). Use after finding a parent message when you need the full back-and-forth.
List all users
List the members of the connected Slack workspace with their user ids, display names, and (when the workspace shares them) emails. Use it to resolve a person's name to the user id you pass to a from:@user search modifier, or to map message author ids back to people.
Built for restoration, not bolted on.
Grounded answers
Ruby reads Slack live and cites what she found, so answers reflect your actual data, not a stale export.
Read-only by design
Least-privilege, read-only access. Ruby surfaces and drafts; your team always takes the action.
Managed, secure auth
Connect with one click. Tokens are encrypted and scoped per company; revoke access any time.
Knows restoration
Ruby understands jobs, claims, drying logs, and AR, so Slack data lands in the right operational context.
Connect once, then just ask.
Connect Slack once in Ruby. Ask in the Ruby app, or bring the same secure connection into the assistant your team already uses.
Ruby
Ask in the Ruby app and get an answer grounded in Slack and the rest of your connected stack.
Claude
Bring the same secure Slack connection into Claude so it can answer with your live data.
ChatGPT
Use Slack from ChatGPT with the same per-company, read-only access Ruby uses.
Frequently asked questions
Do I need developer credentials to connect Slack?
No. Slack connects with a single click, Ruby handles the OAuth handshake and token refresh for you.
Can Ruby change anything in Slack?
No. The Slack connection is read-only. Ruby reads, summarizes, and drafts; a human always makes the change in Slack.
Is my Slack data secure?
Credentials are encrypted at rest and access is scoped per company. You can revoke the connection at any time from Settings > Integrations, which immediately cuts Ruby off.
Can I use Slack alongside my other tools?
Yes. Ruby reasons across every tool you connect at once, so she can tie Slack to your CRM, accounting, email, and documentation in a single answer.
