obsidian-slack

To archive Slack messages into Obsidian notes, this Skill automatically classifies conversations using channel-based project routing and incremental ingestion to prevent duplicate entries. It groups messages by project and updates your wiki to maintain an ongoing, searchable knowledge base.

Mapping Slack channels to Obsidian projects is handled through channel-based project routing, which automatically categorizes ingested messages into specific project notes. This ensures conversations are organized contextually within your knowledge base without manual sorting.

Yes, you can update your Obsidian wiki with Slack decisions and action items through the wiki integration feature. It automatically extracts relevant outcomes from conversations and reflects them in your unified knowledge base during the archiving process.

Yes, this Slack to Obsidian integration supports incremental ingestion by tracking message timestamps. This mechanism ensures only new messages are processed, avoiding duplicates and keeping your project-based notes and wiki up to date.

Meeting attendees are handled through attendee-aware notes generation when archiving Slack conversations. This feature captures participant context alongside project-based message grouping to maintain clear records of ongoing collaboration.

Yes, Slack data is processed safely using read-only data handling when classifying messages for Obsidian. This approach ensures your conversations are extracted and categorized without risking accidental modifications to the original Slack workspace.