Who it is forA researcher or support engineer who has a set of internal documents and wants a workflow to answer questions from them.
The problemAn LLM workflow cannot answer from private documents until they are indexed in a vector store.
The outcomeA Milvus collection holding embedded chunks of your documents, which a workflow can query through the pluggable retriever.
What you need first
- Python 3.12
- Redis (cluster or standalone) and MySQL
- A cloned copy of the goalflow repository and a filled-in .env file copied from .env.example
- A Dify DSL export (.yml) if you want to transpile a visual flow
Steps
- Run
git cloneon the goalflow repository andcd goalflow. - Run
pip install -e .and set Milvus connection values in .env from .env.example. - Read docs/knowledge-retrieval.md to confirm the ingestion CLI name and options.
- Run the document ingestion CLI on your document folder to extract, chunk, embed, and write to Milvus. (inferred, check the README)
- Set the retriever to Milvus in your workflow configuration and run one test question.
Prompt for your agent
In the goalflow repo, follow docs/knowledge-retrieval.md to ingest the documents in <document-folder> into Milvus. Expected output is a Milvus collection with embedded chunks. Verify the ingestion count matches the number of input documents and run one retrieval query for <question>.
Caveat. The README does not state the ingestion command or the Milvus settings, so the exact invocation must come from docs/knowledge-retrieval.md.
Use this in your AI agent
Ask your agent
Using the Deduped MCP, get the setup steps for wanmol/goal-flow and "Load documents into Milvus for retrieval in a workflow"
Add Deduped to Claude Code once
claude mcp add --transport http deduped https://dedupedai.com/mcp
Every Monday: the 5 hottest repos and exactly how to use them. Free, one email a week, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Third-party repos we don't own. AI-written use cases can be wrong. Disclaimer