← Back to library

Send a Telegram message, get a Todoist task via n8n

lucw on Hacker News, answering someone who missed sending to-dos via OpenClaw, suggests n8n or windmill.dev instead: keep a Telegram bot plus a small LLM for natural phrasing, with fixed workflow steps that write clean tasks straight into Todoist lists.

  • OutcomeText a Telegram bot from anywhere and have an n8n workflow, with an LLM step for plain-language parsing, add the item to your Todoist list.
  • SetupUnder an hour
  • LevelStarter
  • Creditlucw on Hacker News
View original
Works with
n8nChatGPTClaude

Published Oct 23, 2026Updated Oct 23, 2026AI dry run on sample input: passed Oct 23, 2026Source verified Oct 24, 2026

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?

  1. Create the botRegister a Telegram bot and restrict it to your user ID.
  2. Trigger a workflowUse n8n's Telegram trigger to receive each message.
  3. Let a model read the messageTurn the message into a task title, due date and project.
  4. Create the taskCall the Todoist API with the parsed fields.
  5. 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)

Prompt2 variables
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?
A fixed workflow is easier to trust and debug for a single job.
Can it write to a list on a home PC?
Yes, if that list has an API or file the workflow can reach.

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.

More in Money & Admin

All 82 Money & Admin playbooks →

Related playbooks

Money & AdminWorkflow✓ AI dry run

Add a scribbled appointment slip to your calendar

Snap a handwritten appointment card or note, and have a small agent read it, add a calendar event and file any matching PDF from email into your document archive.

Credit: pimeys on Hacker News

An afternoon+
Money & AdminPrompt✓ AI dry run

Appeal a parking ticket with a clear, polite letter

Turn the facts behind a parking ticket into a short, respectful appeal to the right city office, with your evidence attached.

Credit: u/Fuhdawin on r/ChatGPT

Minutes
Money & AdminPrompt✓ AI dry run

Check a contractor's charges and challenge the wrong ones

Have AI compare every invoice line and change order with your purchase orders and emails, then draft specific, evidence-based disputes.

Credit: Addicted Hoosier (@AddictedHoosier)

Under an hour
Money & AdminRoutine✓ AI dry run

Summarize a week of payment notices in one email

Receive one email each Sunday listing every payment notice from the week with vendor, amount and date, plus totals.

Credit: Marianna Nakos

Under an hour