SpyBara
Go Premium

use-cases/slack-action-triage.md 2026-07-08 02:01 UTC to 2026-07-14 17:03 UTC

This page contains 96 additions and 139 deletions.

2026
Tue 14 17:03 Fri 17 22:57 Tue 28 23:01

name: Prioritize Slack action items tagline: Turn Slack threads and DMs into a ranked queue of next steps. summary: Use ChatGPT with Slack and the tools where work happens to find direct asks, implicit follow-ups, resolved items, and the highest-impact next actions before drafting replies or handoffs. skills:

  • token: slack url: https://github.com/openai/plugins/tree/main/plugins/slack description: Search DMs, channels, thread replies, mentions, and shared context before deciding what still needs attention.

  • token: gmail url: https://github.com/openai/plugins/tree/main/plugins/gmail description: Cross-check email when a Slack thread refers to an outreach, intro, or sent follow-up.

  • token: google-drive url: https://github.com/openai/plugins/tree/main/plugins/google-drive description: Read linked docs, decks, sheets, or source material when the Slack thread depends on an artifact.

  • token: google-calendar url: https://github.com/openai/plugins/tree/main/plugins/google-calendar description: Check event timing when a thread depends on a meeting, launch, webinar, or deadline. bestFor:

  • People who get work through Slack and need ChatGPT to separate live asks from already-handled chatter.

  • Launch, community, support, product, and operations workstreams where context is split across DMs, channels, and threads.

  • Teams that want a ranked action queue before drafting replies, handoffs, docs changes, or follow-up tasks. starterPrompt: title: Find What Needs Attention in Slack body: >- Can you check @slack for messages to me about [workstream] from [time window] and return a ranked action queue?

    Look across DMs, group DMs, channel mentions, and threads.

    For each item, include:

    • source link or thread

    • what is being asked

    • whether it needs my reply, a person or lead, a docs or code change, or just a decision

    • why it matters

    • the recommended next step

    Before calling anything unresolved, read the latest thread replies and skip items that were already handled.

    Do not post messages directly but suggest drafts for my review. suggestedEffort: low relatedLinks:

  • label: Plugins url: /codex/plugins

  • label: Use ChatGPT in Slack url: /codex/third-party/slack

  • label: Scheduled tasks url: /codex/automations

Find the work hidden in Slack

Slack is often where a request starts, but not where the full context lives. A teammate might ask for a reply in a DM, clarify the real action in a thread, link a doc in a channel, and resolve the issue later without mentioning you again.

Use this workflow when you want ChatGPT to read the Slack context, check whether the ask is still live, and return the few items that actually need your attention. The goal is to get a ranked action queue: what needs a reply, a decision, a person to contact, a doc update, or a handoff.

Run the triage pass

  1. Give ChatGPT a time window, workstream, person, channel, or topic.
  2. Ask it to search DMs, group DMs, channel mentions, and relevant thread replies.
  3. Have ChatGPT read the latest thread tail before calling an item unresolved.
  4. Ask for a ranked queue sorted by urgency and impact.
  5. Ask ChatGPT to draft the reply, handoff, or follow-up task.

After trying this and tweaking the flow to match your needs, you can schedule the work from the task by asking ChatGPT to do the same thing on a schedule.

Ask for the right output

A useful triage result should explain why each item is still live. It should also skip old asks that someone answered later in the thread.

You should expect to see something like this:

Top action item: Priya is asking for concrete customer examples, not just more ideas.

Why it matters: the launch update needs real people the team can contact this week.

Evidence: the original channel message asked for use cases, but the thread later says "please DM me if you have leads."

Next step: reply with two named leads, or say you can be the example if that is more useful.

Good output makes the distinction explicit: an idea is different from a lead, a live ask is different from an FYI, and a request you already answered shouldn't stay in the queue.

If you get too much noise or too few actionable items, tweak the prompt and if needed, mention specific slack channels you want ChatGPT to pay attention to.

Draft the follow-up

Once the queue is right, keep the action in the same task. Ask ChatGPT to draft a reply or handoff from the evidence it already gathered: