Ask in Slack
Ask /docpipe a question and get an answer grounded in your docs, with citations, right in the channel.
When someone has a question your team has answered before, they can ask Docpipe in Slack instead of interrupting a colleague. Docpipe replies in the channel with an answer drawn from your documentation — and links to the exact sources behind it.
Ask a question
In any channel, or in a DM to the Docpipe bot, type /docpipe followed by your question:
/docpipe How long does a production access token stay valid?Docpipe replies "On it — Docpipe is processing your message and will reply here shortly," then follows up with the answer.
There's no separate command for questions. Docpipe reads what you wrote and decides whether it's a question to answer or documentation to capture — a question gets a cited answer, and a statement becomes a proposal. (See Capture from Slack for the capture side.)
Read the answer and its sources
The reply comes in two parts:
- The answer, written in plain language from your documentation.
- A Sources list beneath it — the documents (and, where relevant, indexed code files) the answer draws from, shown as clickable links. Open a source to read the full context and confirm the details yourself.
A question in Slack searches across all the documentation you have access to.
Asking in Slack is the fastest way to find out whether something is documented. If Docpipe can't answer, that's a signal the knowledge is missing — a good moment to capture it once you have the answer.
Docpipe won't guess
Docpipe answers only from what it can find in your knowledge base. If the docs don't cover your question, it says so rather than inventing an answer — and it can forward the question to a subject-matter expert instead. See When docs can't answer.
To ask about a single open document, or to work in the app rather than Slack, use the web assistant.