When should you use it?
- Ideas hit you away from your desk
- You use Todoist or a similar list
- You want a simple, controlled bot
Not for: People who want an agent with wide system access; Lists that live only on an offline machine without an API
What do you need, and what do you get?
You need
- Telegram bot token
- Todoist API token
- n8n instance
You get
- Tasks created from chat messages
- A confirmation reply in Telegram
How does it work, step by step?
- Create the botRegister a Telegram bot and restrict it to your user ID.
- Trigger a workflowUse n8n's Telegram trigger to receive each message.
- Let a model read the messageTurn the message into a task title, due date and project.
- Create the taskCall the Todoist API with the parsed fields.
- ConfirmReply in Telegram with what was added so mistakes are visible.
The prompt
Our own prompt, inspired by lucw on Hacker News and written to work in n8n, ChatGPT and Claude. Values in lime are placeholders.
Fill in the blanks (optional; the copied prompt uses your values)
Turn this message into a Todoist task: {message} Return JSON with title, due_date (YYYY-MM-DD or null), project from {projects}, and priority 1 to 4. If the date is unclear, set it to null and add a question field.
Inspired by lucw on Hacker News: Hacker News reply on adding to-dos by Telegram without OpenClaw. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.
What can go wrong?
- Leaving the bot open to anyone lets strangers add tasks.
- LLM date parsing can be off by a day; echo the date back.
Our take
Not every job needs an autonomous agent. A single-purpose workflow with a small LLM step gives natural-language input without handing broad access to a general assistant. lucw's suggestion is a good corrective to the habit of reaching for a general agent. A Telegram bot, an n8n workflow and a small model that turns a sentence into a title, due date and project gives you natural phrasing with fixed, predictable steps. Restrict the bot to your own user ID first, or anyone who finds it can add tasks to your list. Have the workflow reply with exactly what it created, including the date, because model date parsing can be off by a day and an echo makes the mistake obvious immediately. The Todoist API call only needs permission to create tasks, so scope the token accordingly. If you later want more, add another workflow rather than widening this one. Lists without an API will not work here.
Where the time goes back: Capturing a task takes one chat message, and it lands in the right list without opening another app.
FAQ
Why not a general agent?
Can it write to a list on a home PC?
Source and credit
Inspired by lucw on Hacker News. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.
- Inspired by
- Hacker News reply on adding to-dos by Telegram without OpenClaw
- Creator
- lucw on Hacker News
- Published on
- Hacker News
- Original date
- Apr 11, 2026
- License
- Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
- Originally for
- n8n
- AI dry run
- Oct 23, 2026: passed. Dry-run tested by our AI test agent on sample input. PASS: Gates held on desk check; no live sends or purchases.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails. - Verified
- Oct 24, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.
Are you the creator? Claim or correct this page.