Capture knowledge from Slack without leaving the conversation

Drop a link in Slack and ask Zero to ingest it. Zero fetches the content, summarizes it, and stores it in your team knowledge base — no context switch required.

Zero conecta:

Why good content gets lost in Slack

Someone shares a good article, a competitor announcement, or a research paper in #news. It gets a few reacts, maybe a comment, and then it's gone. Three weeks later someone asks 'didn't we read something about this?' and nobody can find it. Zero turns any shared link into a permanent entry in your team KB — fetched, summarized, and categorized from a single Slack message.

How to ask Zero to ingest a link into the KB

@Zero kb ingest https://x.com/example/status/123456

pruébalo

How Zero fetches, summarizes, and stores the content

Zero fetches the content

Zero retrieves the full text of the linked page — X thread, GitHub repo, blog post, or documentation — and extracts the meaningful content.

Zero summarizes and categorizes

Zero writes a concise summary capturing the key insight, source, and date. It adds context from the Slack thread if relevant.

Stored in the team KB

The article is saved to your team knowledge base as a markdown file, ready to be queried, compiled into wiki articles, or surfaced in future searches.

Query the KB, compile articles, or chain into a weekly digest

Query what was ingested

Ask Zero to find relevant KB content on a topic

@Zero what does the KB say about sandbox isolation approaches?

pruébalo

Compile a KB article

Turn raw ingested content into a structured wiki article

@Zero compile a KB article on agentic AI trends from the last month of ingested content.

pruébalo

Schedule weekly ingestion

Automatically ingest top links from a channel on a schedule

@Zero every Friday, ingest the top 3 most-reacted links shared in #news this week.

pruébalo

Required integrations: Slack and GitHub

Slack

Slack is where the link is shared and where Zero receives the ingest command.

Obligatorio

GitHub

GitHub is optional. Zero commits the markdown file directly to your KB repository.

Opcional

Best practices for building a living team knowledge base

●Add a note after the URL to give Zero context: 'kb ingest [url] — this is relevant to our sandbox architecture.' The note gets included in the stored file.

●Set up a dedicated #news or #kb-ingest channel so your team has a shared habit of dropping links for Zero to capture.

●Pair with a weekly KB compile to turn raw ingested articles into structured, searchable wiki entries.