This is the guide that ships with the template, published here in full before you buy — read it first. If these steps look out of reach, don't pay.
Budget 20 to 30 minutes. No code to write, and every technical word is explained where it first appears.
TaskMaster Pro runs on n8n, an automation tool you install on a server: you draw what should happen, and n8n runs it for you. One drawing is called a workflow, and each box inside it is a node. This template is five such drawings, ready to import.
Now the part that decides whether your install goes well. Telegram never comes to your
server to collect messages. It pushes them the moment someone writes to
your bot — Telegram calls an address that belongs to you, and that incoming call is what the
word webhook means. So your n8n has to be reachable from the internet, at
an address starting with https. Almost every failed install comes down to this
one point.
n8n Cloud, or n8n on your own server behind a domain name: there is nothing to do. When you publish, n8n tells Telegram where to call, on its own. Nothing to paste into BotFather.
Telegram cannot reach localhost, the name a computer gives itself and which
means nothing to the outside world. One command gets you a free public address:
cloudflared tunnel --url http://localhost:5678. It prints an address ending
in .trycloudflare.com, and that is your public address. Careful: it changes
at every restart, which is fine to try things out, and wrong for a bot that runs day and
night.
None of this is specific to this template. Every Telegram bot works this way.
Gather these five things first. Hunting for them halfway through the install is how people lose an evening.
Credentials, then environment variables, then import, then your values, then tables, then publish. Done in that order, every node binds itself during the import — you publish in one clean shot. Done out of order, you will spend the evening re-picking accesses box by box.
An empty PostgreSQL database, and a database user allowed to create tables in it. That is
all: CREATE DATABASE taskmaster;. The tables, meaning the shelves the bot
stores things on, come at step 6 in one click, with no terminal.
In n8n: Settings → Credentials. A credential is an access saved once (a token, a key, a database login) that every node then reuses. n8n stores it encrypted, which is why your keys never sit in the workflow file itself.
Name each one exactly as below, capital letters included. That name is how n8n matches an access to a node when it reads the imported file. One capital out of place and you get to rebind every node by hand.
Telegram account: type Telegram APIPostgres account: type Postgres, pointed at the database from step 1OpenAI account: with a capital I, the n8n default namePerplexity account: not "Perplexity API"All four are needed to publish: n8n refuses to activate a workflow whose nodes have an unconfigured access. If you don't want the AI part, move those nodes to Ollama or delete them; the guide inside the bundle names each one.
An environment variable is a setting you hand to the program itself
rather than to a workflow. n8n reads it once when it starts, so you set it and then
restart n8n: WEBHOOK_URL, your public address, and BOT_TOKEN,
the token from BotFather.
Why the first one matters: a program has no way of knowing the address the outside world
reaches it at. WEBHOOK_URL is what n8n hands to Telegram so the messages come
back to you. No AI keys here; those stay in the credentials from step 2.
Workflows → Add workflow → Import from File, once per file. Importing means loading a drawing someone else made into your own n8n. Because the accesses already exist under the right names, every node picks its own: no red nodes waiting for you.
The template ships with four blanks, because four things belong to you and nobody else: your Telegram chat id (so the bot knows who its administrator is), the name the bot gives itself, its @username, and your public address. The Configure workflow fills them for you: type the four values into one node, click Execute workflow, and it replaces them everywhere. You can delete Configure afterwards.
The other route is to open the file in a text editor and replace the four values yourself, before importing. Both work; the first one saves you the typos.
Open the Setup workflow and click Execute workflow. The eleven tables the bot needs are created for you, which is why you never open a terminal. Running it a second time breaks nothing and erases no data.
Activate the three running workflows, not Setup. Activating is what tells n8n to listen
for real messages, and it is at that exact moment that n8n registers the webhook with
Telegram. Send /start to your bot from your own account: you are approved
automatically, because your chat id is the administrator one. Anyone else who finds your
bot lands in a pending list until you approve them.
Toggle the bot workflow off, then on again. n8n registers the webhook with Telegram at
activation, and a fresh toggle registers it again. You need this when the token had
already been used for another bot, since Telegram keeps only one address per token. Send
/start again afterwards.
Red means the node found no access to use. The credential name does not match the expected one exactly. Fix the name in Credentials, or pick the access again from the dropdown inside the node. It is almost always a capital letter.
Nothing here is jargon for its own sake. These eight words cover the whole install, and you will see them again in n8n's own screens.
Do these steps look doable? The template is 39 CHF, the files arrive straight away, and the full guide is inside, with the detail of every setting. Do they look out of reach? Then don't buy it — a lost evening for you, a refund for us.