Slack

Your assistant can read your unread messages the way you would, channel by channel and DM by DM, and give you back a summary organized by what needs a reply rather than by when it arrived. It resolves channel names to IDs first, so you can just say the channel name. Nothing gets marked read, posted, or reacted to.

What you end up with. A written catch-up separating the things waiting on you from the things you only need to know about, with links back to the original messages.

Start with it bringing you the information and you deciding.

Never without. Ask it to check threads explicitly. Slack's conversation history endpoint returns only the main channel timeline and not threaded replies, so a catch-up built from history alone will quietly miss the conversation that happened inside a thread.

Built on: List unread channel messages / Get unread messages from user / Fetch conversation history / Find channels

Workspace search is available to your assistant with the same modifiers you would type by hand, so it can look across channels, filter by person and date range, and read the files that came up alongside the messages. Because it reads rather than skims, you can ask for the answer rather than for the search results. It can only see what your own account can see.

What you end up with. The actual message or file you were thinking of, with its channel, its date, and the surrounding conversation.

Start with it bringing you the information and you deciding.

Never without. Treat an empty result as a permissions answer rather than a factual one. Slack search is scoped to what your token can see, so a private channel you are not in returns nothing and looks identical to the thing never having been said.

Built on: Search messages / Search all content / Real-time search / Download Slack file

The assistant can look up people by name, display name or email, read the full workspace roster with profile and team membership, and cross-reference that against who has been talking about the topic recently. That last part is usually the useful bit: the org chart says one thing and the channels say another.

What you end up with. A name, their Slack handle, and the recent messages that show why they are the right person to ask.

Start with it bringing you the information and you deciding.

Never without. Filter bots and deactivated accounts out of any roster you build from this, because the user list returns is_bot, is_app_user and deleted accounts alongside real colleagues and the profile data is not always current.

Built on: Find users / List all users / Search messages

It can read the week out of the relevant channels, draft the update, and post or schedule it into the channel you name. Scheduling reaches up to 120 days ahead, which covers the standing Friday slot. If you spot a problem after it posts, it can edit the message in place rather than posting a correction underneath.

What you end up with. A posted or scheduled update in the right channel, drafted from what actually happened in the channels rather than from your memory of it.

Start with it doing the work and checking with you.

Never without. Name the destination channel yourself and read the draft before it posts. Channel display names are not unique, the assistant resolves names to IDs on its own, and a message is visible to everyone in the channel the instant it goes out.

Built on: Fetch conversation history / Send message / Schedule message / Update a Slack message

Slack Canvas is writable by your assistant, including targeted edits: it can look up section IDs and then replace or insert content at a specific place rather than rewriting the whole document. So a canvas can be a live project summary that gets updated from the channel as things happen, instead of a snapshot that goes stale the day after you write it.

What you end up with. A canvas in the channel that stays current with decisions and open questions, updated section by section rather than replaced.

Start with it doing the work and checking with you.

Never without. Have it insert into a named section rather than replacing the canvas wholesale, and keep anything you cannot afford to lose in a section it is not allowed to touch.

Built on: Create Slack Canvas / Lookup Canvas Sections / Edit Slack Canvas / Fetch conversation history

Slack Lists are readable and writable, so the assistant can create a list with typed columns, add a row per commitment with owner and due date filled in, and update those rows later as things move. It can read the list back at any point to tell you what is still open. The list lives in Slack, so nobody has to open a second tool to see it.

What you end up with. A Slack List with one row per commitment, each with an owner and a date, sitting in the channel where the conversation happened.

Start with it doing the work and checking with you.

Never without. Read the rows it created before telling anyone the list is the source of truth. It is inferring owners and dates from conversational language, and a commitment attributed to the wrong person is worse than no list at all.

Built on: Create Slack List / Create Slack List item / List Slack List items / Update Slack List item / Get Slack List item

It can, and this is the part to hold onto. Deleting list rows, deleting a canvas, and revoking a list's sharing access are all permanent in Slack with no recovery. The bulk row delete is all-or-nothing and returns a single success or failure with no per-row detail, so if it fails you cannot tell from the response which rows survived.

What you end up with. An emptied list and, where you asked for it, a deleted canvas, with the contents saved somewhere outside Slack before either went.

Start with it doing the work and checking with you.

Never without. Have it export the rows or the canvas content to somewhere outside Slack first, and approve the exact list of items by name. Deleting a canvas is permanent and irreversible in the connector's own words, revoking list access is not a soft toggle, and the multi-row delete reports no per-item result, so a partial failure leaves you unable to tell what is still there.

Built on: List Slack List items / Delete Slack List item / Delete multiple Slack List items / Delete Slack Canvas / Delete Slack List access

Reminders and scheduled messages are both writable, so a recurring prompt can become a routine you look at rather than one you run. Reminders accept natural language timing such as every Thursday at 2pm. Start it supervised, and not because of the risk: the wording and the timing usually need two or three corrections before they are right.

What you end up with. A standing weekly prompt going out on the same day each week, with the wording settled after the first few runs rather than before them.

Start with it doing the work and checking with you.

Never without. Set an explicit boundary on which channels it may post to, and check the scheduled queue after the first few runs. A recurring message with a wrong date reference repeats the error every week to the whole channel until somebody notices.

Built on: Create a reminder / Schedule message / Send message / Fetch conversation history