hivein for Slack
Search, summarise and answer in Slack, without anyone scrolling back through the channel.
Slack's OAuth v2 install flow, after which every action is a Web API method call — chat.postMessage, conversations.history, search.messages — limited to the granted scopes.
- Post, thread and edit
- Read the conversation back
- Search what was already said
- Send at the right moment
- Run channels and find people
Your Slack, as actions the copilot can take.
Post, thread and edit
A message goes to a channel or a direct message, optionally as a reply on an existing thread. Because Slack identifies a message by its timestamp, the same message can later be edited, deleted, pinned, reacted to, or turned into a permalink to quote elsewhere.
Read the conversation back
Channel history and the replies under a particular message come back as real messages with their author and timestamp. That is what makes summarising yesterday's thread possible rather than guessing at it.
Search what was already said
Slack's own search syntax runs across the conversations the install can see, so a question that has been answered before is answered from the record. Each hit carries the channel and timestamp needed to open or quote it.
Send at the right moment
A message can be scheduled for a future time instead of sent now. The queue of scheduled but unsent messages can be listed, and any of them cancelled before it fires.
Run channels and find people
Channels are listed, created, joined, left, archived, given a topic, and have members invited or listed. People are resolved by email address or profile, and a direct message opened with one person or several.
It reads your Slack data model, not a generic one.
The schema is read first, so a question that spans two of these is one question, not two lookups.
“Summarise what happened in the incident channel overnight”
“Schedule a standup reminder in the product channel for 9am tomorrow”
“Who raised the pricing question last month and what was the answer”
“Create a channel for the launch and invite everyone from the design team”
Writes to Slack wait for you.
The same three guardrails hold on every template. They are attached to the action itself, so they hold on every path. Watch the replay →
- 01
The plan is held
A plan that writes to a real system stops before it starts. You see the goal, the risk and every step, then confirm or reject.
- 02
Each write asks first
A tool marked ask-first shows the exact call with its values. Confirm it, edit the values, or reject it. Nothing runs until you decide.
- 03
A rejection is an instruction
Pick a reason and add a line. The copilot re-plans with what you told it instead of guessing.
Slack questions.
Does it read every channel in the workspace?
Only the conversations the granted scopes cover and the channels the app has been added to. Reading history is a per-channel call, so a private channel stays out of reach until the app is invited into it.
How does it know which channel I mean by name?
Slack addresses everything by ID rather than by name, so the channel list is fetched and the name resolved to an ID before anything is posted. People work the same way, and can be looked up by email address when the display name is ambiguous.
Can it reply inside a thread rather than the main channel?
Yes. A reply is posted with the parent message's timestamp, which places it in that thread instead of the channel. The replies under any message can be read back the same way, which is how a thread gets summarised.
More templates like this one.
Google Workspace
Closed sourceAsk across Gmail, Calendar, Drive, Docs and Sheets, and have the answer written back into the right file.
137 actionsOpen template → — Google WorkspaceM365Microsoft 365
Closed sourceOne assistant across Outlook, Teams, OneDrive, SharePoint and Excel, all through Microsoft Graph.
74 actionsOpen template → — Microsoft 365
Notion
Closed sourceQuery a Notion database, write the answer back as a page, and keep the property types correct.
26 actionsOpen template → — NotionConnect Slack. Get a copilot this afternoon.
No card, no agent configuration, no prompt to write. Sign in and approve the actions it may take.