use-cases/slack-action-triage.md +123 −0 added
1---
2name: Prioritize Slack action items
3tagline: Turn Slack threads and DMs into a ranked queue of next steps.
4summary: Use Codex with Slack and the tools where work happens to find direct
5 asks, implicit follow-ups, resolved items, and the highest-impact next actions
6 before drafting replies or handoffs.
7skills:
8 - token: slack
9 url: https://github.com/openai/plugins/tree/main/plugins/slack
10 description: Search DMs, channels, thread replies, mentions, and shared context
11 before deciding what still needs attention.
12 - token: gmail
13 url: https://github.com/openai/plugins/tree/main/plugins/gmail
14 description: Cross-check email when a Slack thread refers to an outreach, intro,
15 or sent follow-up.
16 - token: google-drive
17 url: https://github.com/openai/plugins/tree/main/plugins/google-drive
18 description: Read linked docs, decks, sheets, or source material when the Slack
19 thread depends on an artifact.
20 - token: google-calendar
21 url: https://github.com/openai/plugins/tree/main/plugins/google-calendar
22 description: Check event timing when a thread depends on a meeting, launch,
23 webinar, or deadline.
24bestFor:
25 - People who get work through Slack and need Codex to separate live asks from
26 already-handled chatter.
27 - Launch, community, support, product, and operations workstreams where
28 context is split across DMs, channels, and threads.
29 - Teams that want a ranked action queue before drafting replies, handoffs,
30 docs changes, or follow-up tasks.
31starterPrompt:
32 title: Find What Needs Attention in Slack
33 body: >-
34 Can you check @slack for messages to me about [workstream] from [time
35 window] and return a ranked action queue?
36
37
38 Look across DMs, group DMs, channel mentions, and threads.
39
40
41 For each item, include:
42
43 - source link or thread
44
45 - what is being asked
46
47 - whether it needs my reply, a person or lead, a docs or code change, or
48 just a decision
49
50 - why it matters
51
52 - the recommended next step
53
54
55 Before calling anything unresolved, read the latest thread replies and skip
56 items that were already handled.
57
58
59 Do not post messages directly but suggest drafts for my review.
60 suggestedEffort: low
61relatedLinks:
62 - label: Codex plugins
63 url: /codex/plugins
64 - label: Use Codex in Slack
65 url: /codex/integrations/slack
66 - label: Codex automations
67 url: /codex/app/automations
68---
69
70## Find the work hidden in Slack
71
72Slack 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.
73
74Use this workflow when you want Codex 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.
75
76## Run the triage pass
77
78
79
801. Give Codex a time window, workstream, person, channel, or topic.
812. Ask it to search DMs, group DMs, channel mentions, and relevant thread replies.
823. Have Codex read the latest thread tail before calling an item unresolved.
834. Ask for a ranked queue sorted by urgency and impact.
845. Ask Codex to draft the reply, handoff, or follow-up task.
85
86
87
88After trying this and tweaking the flow to match your needs, you can turn it into a [thread automation](https://developers.openai.com/codex/app/automations#thread-automations) by asking Codex to do the same thing on a schedule.
89
90## Ask for the right output
91
92A useful triage result should explain why each item is still live. It should also skip old asks that someone answered later in the thread.
93
94You should expect to see something like this:
95
96
97
98<p>
99 <strong>Top action item:</strong> Priya is asking for concrete customer
100 examples, not just more ideas.
101 </p>
102 <p>
103 <strong>Why it matters:</strong> the launch update needs real people the
104 team can contact this week.
105 </p>
106 <p>
107 <strong>Evidence:</strong> the original channel message asked for use cases,
108 but the thread later says "please DM me if you have leads."
109 </p>
110 <p>
111 <strong>Next step:</strong> reply with two named leads, or say you can be
112 the example if that is more useful.
113 </p>
114
115
116
117Good 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.
118
119If you get too much noise or too few actionable items, tweak the prompt and if needed, mention specific slack channels you want Codex to pay attention to.
120
121## Draft the follow-up
122
123Once the queue is right, keep the action in the same thread. Ask Codex to draft a reply or handoff from the evidence it already gathered: