Add home TODO items by Telegram message
The author told an OpenClaw agent over Telegram to add items to a home TODO list via a custom API while at the office, before they stopped using it. Task: The author operated OpenClaw on a home PC with a custom API for a local TODO list. From the office, they sent Telegram messages which the agent parsed to call the API and append items. The workflow relied on OpenClaw's ability to interface with the custom endpoint without phone syncing.; tools: OpenClaw. Human role: The source does not fully disclose the division of human labor; please refer to the original text for details.; limitations: OpenClaw required significant tinkering and was deemed unreliable for perfect setups, though easier than coding per use case. The home API was not exposed to the outside world, requiring specific infrastructure to bridge Telegram and the local PC securely..
Tools
Published on Agent Work Atlas:
Overview
The author told an OpenClaw agent over Telegram to add items to a home TODO list via a custom API while at the office, before they stopped using it.
Workflow
The author operated OpenClaw on a home PC with a custom API for a local TODO list. From the office, they sent Telegram messages which the agent parsed to call the API and append items. The workflow relied on OpenClaw's ability to interface with the custom endpoint without phone syncing.
Reported result
The system functioned well enough that the author misses it, but usage ceased when the underlying QEMU software broke. The author is currently seeking a simpler replication method without the original setup hassle, indicating the previous solution was effective but fragile.
Human role
The source does not fully disclose the division of human labor; please refer to the original text for details.
Limitations
OpenClaw required significant tinkering and was deemed unreliable for perfect setups, though easier than coding per use case. The home API was not exposed to the outside world, requiring specific infrastructure to bridge Telegram and the local PC securely.
Try it
Act as a technical architect. I need to replicate a workflow where I send a Telegram message from my office to add items to a TODO list on my home PC. My home PC runs a local API at [replaceable_input: local_api_endpoint] that accepts POST requests with 'title' and 'summary' fields. The API is not publicly exposed. Please design a secure bridge using [replaceable_input: preferred_tool, e.g., n8n, Tailscale, or a custom Python bot]. Steps: 1. Propose an architecture where a Telegram bot receives my message. 2. Define how an LLM parses the message into 'title' and 'summary'. 3. Explain how the bot securely calls the local API (e.g., via Tailscale or a persistent connection). 4. Provide a sample configuration or code snippet for the parsing and API call logic. Constraints: Do not expose the home API directly to the internet. Ensure the solution is lightweight and avoids the complexity of OpenClaw. First, ask me for the specific programming language or platform I prefer for the bot. Then, provide a dry-run plan for testing the connection before full implementation.
Source reports are not independently verified. Publication date is the catalog publication date, not the original article date.