How to turn a Slack discussion into lasting documentation
A useful Slack discussion can contain a decision or procedure that deserves a more durable home. Documentation makes that knowledge easier to find without requiring someone to reconstruct the thread.
Start with the right material.
- What you provide
- one manually expanded thread whose text is visible.
- The intended result
- Save decisions and reusable guidance with source references; no workspace-wide search.
How the workflow works.
Identify the settled guidance and organize it by topic or task. Preserve decisions, rationale and source references while separating unresolved suggestions from the agreed process.
What to check in the result.
Check the end of the thread and any supplied follow-up before writing a final procedure. Informal discussion may contain outdated proposals, and private or unrelated participant details should be omitted.
Preview the Markdown to check headings, lists and links as well as the words. Keep source references with the document so a reviewer can trace important statements back to the material you supplied.
Learn from the worked example.
The downloadable Markdown example shows one possible organization of the result. Read it alongside the source example and notice which statements are recorded facts, proposed wording or questions still needing an answer.
The supplied example is illustrative. It is not a recorded run on your data.
Download the example ↓Use it with your own material.
- Open the source you want to work with and activate WebAct on that tab.
- Copy the task from the hero, add any required fields or preferences, and review the proposed actions.
- Compare the first result with your source. Ask for a specific correction or refinement where needed.