From ead20c23e1c2e93dc2d9934553d764637bcc6465 Mon Sep 17 00:00:00 2001 From: Reza Yaghobi Date: Sun, 30 Aug 2026 22:36:19 +0330 Subject: [PATCH] update the main readme --- README.md | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/README.md b/README.md index 17e1455..5200778 100644 --- a/README.md +++ b/README.md @@ -15,6 +15,19 @@ See inside the folder for: - **HOW_IT_WORKS.md** — architecture and data flow, step by step - **NODE_DESCRIPTIONS.md** — talking points for walking through the workflow live +### [`n8n-bale-publicchat-file-fetch`](./n8n-bale-publicchat-file-fetch) + +An n8n workflow that extends the file-retrieval concept to **public Bale bots you don't control**. The standard Bale Bot API only works within chats the bot owns — this project bypasses that limitation using client authentication (phone-number login via the unofficial [`aiobale`](https://github.com/) library), allowing access to any public bot's chat history. + +How it works: a natural-language request is parsed by an LLM to extract a keyword, which is then used to search the public bot's entire message history for matching files. Unlike the bot-API approach, this doesn't need to be admin of the target chat — it acts as a regular user session. + +Built as a proof-of-concept demonstrating that client auth can access chats where bot auth cannot, while being honest about the trade-offs (real user session vs. sanctioned bot integration). + +See inside the folder for: +- **BALE-METRO-FILE-AGENT-DOCS.md** — full technical documentation covering architecture, the two route approaches, infrastructure quirks, and reproduction steps +- **script/fetch_metro_smart.py** — the Python script that does the actual Bale client-auth + history search +- **json/** — the n8n workflow export + ### [`.freebuff`](./.freebuff) *(add a short description here once you're ready — leaving as a placeholder for now)*