Your team already wrote the answers in Confluence; people just cannot find them, so they ask in Slack instead. This agent reads the docs for them.
sonnet4 daysConfluenceOpenAIPineconeSlack
Claude
84ROI
81Scale
$3k90Saved
ROI for
README.md
Why this subagent
Your team already wrote the answers in Confluence; people just cannot find them, so they ask in Slack instead. This agent reads the docs for them.
It indexes your spaces, retrieves the right passages for any question, and answers with a link straight to the source page. It answers only from your own documentation and admits when the knowledge base has a gap, so you trust what it tells you.
How it runs
Used at step 01 to kick off the pipeline.
Write
Used at step 01 to kick off the pipeline.
WebFetch
Used at step 01 to kick off the pipeline.
WebSearch
Used at step 01 to kick off the pipeline.
Take a question from Slack or your app and retrieve the most relevant passages.
pending
Answer from those passages only, quoting the specific section it relied on.
pending
Link back to the source pages and flag when the knowledge base has no good answer.
pending
Sample output
json
// Sample output
// (generated when the pipeline finishes)
Answer the user's question using only retrieved Confluence passages; cite the page and section, and if no passage supports an answer, say so instead of guessing.
Unlock the rest
The full agent definition, install snippet, and starter task are gated for community members.
Members get the full `.md` agent file, the npm / pnpm install one-liners, a starter prompt that we've tuned against real runs, and the open-source repo when this automation ships there. One email, magic link, done.