# AI use cases for Telegram Parser (TheMyxa/telegram-parser) Repo: [TheMyxa/telegram-parser](https://github.com/TheMyxa/telegram-parser) | Use cases: 4 | Page: https://dedupedai.com/use-cases/themyxa-telegram-parser/ TG is a local-first Telegram comments exporter that saves channel posts, comments, and reactions to files or PostgreSQL, and includes a web dashboard for analyzing them. This file holds every use case of this repo. Each one starts with a "## " heading and ends with its URL. - Explore sample comment data in a local dashboard: https://dedupedai.com/use-cases/themyxa-telegram-parser/explore-comments-dashboard-offline/ - Export a Telegram channel's posts and comments to JSON: https://dedupedai.com/use-cases/themyxa-telegram-parser/export-channel-comments-to-json/ - Keep a channel dataset current with incremental updates: https://dedupedai.com/use-cases/themyxa-telegram-parser/keep-channel-dataset-current/ - Compare comment and reaction activity across two periods: https://dedupedai.com/use-cases/themyxa-telegram-parser/compare-engagement-between-periods/ ## How to explore sample comment data in a local dashboard with Telegram Parser Repo: [TheMyxa/telegram-parser](https://github.com/TheMyxa/telegram-parser) | Difficulty: Beginner | Time: 0.5 hours | Basis: From the README Open the bundled demo export in the dashboard to see charts, post trees, and filters without any Telegram login. **Who it is for:** A person evaluating the tool or training a teammate who has no Telegram API access yet and wants to see what the output looks like. **The problem:** Setting up Telegram credentials just to see the dashboard is a barrier when the goal is only to judge the interface. **The outcome:** The user browses posts, comment trees, user profiles, and charts from the demo JSON on their own machine. ### Steps 1. Install Docker Desktop and open the folder containing the TG project. 2. Run `docker compose up --build` in the project folder. 3. Open `http://localhost:9595` in a browser. 4. Upload `examples/example.json` through the dashboard upload control. 5. Click a post to open its comment tree, then filter by user or date range. ### Prompt to paste into your agent ```text Use the TG repo (TheMyxa/telegram-parser) to start the dashboard with `docker compose up --build` and load examples/example.json. Report the number of posts, comments, and unique users shown for the file. Verify that the dashboard responds at http://localhost:9595 before reporting. ``` ### Caveat The demo file tests the dashboard only, so it does not show how a live channel behaves. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/themyxa-telegram-parser/explore-comments-dashboard-offline/ ## How to export a Telegram channel's posts and comments to JSON with Telegram Parser Repo: [TheMyxa/telegram-parser](https://github.com/TheMyxa/telegram-parser) | Difficulty: Intermediate | Time: 1 hour | Basis: From the README Pull posts, discussion comments, and reactions from your channel into a local JSON file for analysis. **Who it is for:** A community manager or analyst who needs a full local copy of a channel's discussion for review or reporting. **The problem:** Comment threads and reactions in Telegram are hard to analyze in the app and cannot be filtered or summarized offline. **The outcome:** A dated JSON export in data/raw that the dashboard can open and that other tools can read. ### Steps 1. Get `API_ID` and `API_HASH` at `https://my.telegram.org/apps`. 2. Run `docker compose up --build` once so Docker creates `.env` from `.env.example`. 3. Open `http://localhost:9595`, then fill in the Telegram settings in the Export tab. 4. Run `docker compose run --rm cli export json` to start the export from the command line. 5. Open the new file under `data/raw/` in the dashboard. ### Prompt to paste into your agent ```text In the TheMyxa/telegram-parser repo, configure .env with API_ID, API_HASH, CHANNEL set to , and TELEGRAM_SESSION, then run `docker compose run --rm cli export json`. Expected output is a new JSON file in data/raw/. Verify the file exists and contains a list of posts before reporting success. ``` ### Caveat Live exports need your own Telegram account session, and the README does not describe how the session file is created. Risk, credentials: The export needs your Telegram API_HASH and a Telethon session file, so keep .env and the sessions folder private and out of shared repos. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/themyxa-telegram-parser/export-channel-comments-to-json/ ## How to keep a channel dataset current with incremental updates with Telegram Parser Repo: [TheMyxa/telegram-parser](https://github.com/TheMyxa/telegram-parser) | Difficulty: Intermediate | Time: 1 hour | Basis: From the README Refresh an existing export with new posts and changed comments, or run Watch mode for continuous updates. **Who it is for:** An analyst tracking a channel over weeks who wants counts and reactions on older posts to stay accurate without full re-exports. **The problem:** Re-exporting the whole channel each time is slow, and old posts keep changing as comments and reactions arrive. **The outcome:** A single dataset file that merges new posts by post_id and comments by comment_id, with counters refreshed on recent posts. ### Steps 1. Complete a first export, such as `docker compose run --rm cli export json`, so a dataset exists. 2. Run `docker compose run --rm cli export json --incremental` on a schedule you choose. 3. For continuous updates, run `docker compose run --rm cli watch --poll-interval 30 --refresh-active-posts 20`. 4. Check `data/state/` for the saved incremental state and `data/raw/` for the updated dataset. ### Prompt to paste into your agent ```text In the TheMyxa/telegram-parser repo, run `docker compose run --rm cli export json --incremental` for channel . Expected output is an updated *_dataset.json in data/raw/ and a state file in data/state/. Verify that the post count did not drop after the run before reporting. ``` ### Caveat Incremental runs depend on the saved state in data/state/, so deleting that folder makes the next run behave like a fresh export. Risk, credentials: Watch mode keeps the Telethon session open for a long time, so protect the session file and stop the process when you no longer need it. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/themyxa-telegram-parser/keep-channel-dataset-current/ ## How to compare comment and reaction activity across two periods with Telegram Parser Repo: [TheMyxa/telegram-parser](https://github.com/TheMyxa/telegram-parser) | Difficulty: Intermediate | Time: 1 hour | Basis: From the README Measure comments, unique users, and reactions for a period against the previous period of the same length. **Who it is for:** A channel owner reviewing whether a campaign or a content change raised discussion compared with the period before. **The problem:** Judging engagement by eye across weeks is unreliable, and manual counting from the app is slow. **The outcome:** A comparison of comments, unique users, and comment reactions between the chosen period and the previous one. ### Steps 1. Make sure a JSON export exists in `data/raw/`, for example from `docker compose run --rm cli export json`. 2. Pick the period start and end dates. The end date is exclusive. 3. Run `docker compose run --rm cli compare --from 2026-07-01 --to 2026-08-01 --file durov_dataset.json` with your own dates and file name. 4. Optionally open the dashboard and use the compare API at `/api/export//compare` for the same dates. ### Prompt to paste into your agent ```text In the TheMyxa/telegram-parser repo, run `docker compose run --rm cli compare --from --to --file .json`. Expected output is the comment, user, and reaction counts for the period and the previous period. Verify that both date ranges match the requested dates before reporting. ``` ### Caveat The comparison runs on the saved JSON file, so it reflects the export's state at the time it was last refreshed. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/themyxa-telegram-parser/compare-engagement-between-periods/