Build an AI agent in 5 minutes: Notion + Telegram

Six minutes, start to finish. The written steps below are the reference version.

What makes this five minutes

Most of the setup work you would expect is missing, and that is the point worth noticing before the steps. There is no integrations screen to hunt through and no configuration file. You ask the agent to connect something, in the same chat window you will use it in, and it searches its own integration library, finds the right one, and hands you a sign-in link.

By the end you can message a bot from your phone — "write up a page explaining X and send me the link" — and get a real Notion page back.

Step 1 — Create the agent

Create an agent, name it, and pick a model. That is the whole step; the agent exists and is usable immediately. In the video it is called Grace, which matters more than it sounds: you will be talking to it by name on Telegram later, so pick something you will recognise in a notification.

Step 2 — Ask it to connect Notion

In the chat, ask: "Can you connect Notion MCP?"

The agent searches the list of available integrations, finds Notion, and opens a magic link. This is the part worth understanding, because it is doing real work on your behalf: the magic link is a separate, secure sign-in surface that exists so that tokens and API keys never pass through the agent. The model is not handed your credentials, because it never sees them.

You will see a short PIN in the chat. Enter it on the magic-link page and hit start. Notion's own authentication page opens, you approve, and the resulting tokens are written into your encrypted vault. Close the page, and the chat reports the connection is live.

Step 3 — Prove it works before adding anything else

Ask for something concrete: "Can you create a Notion page with a summary of this conversation and give me the URL?"

The agent calls the Notion tools, creates the page, and returns a link you can click. Two reasons to do this now rather than at the end: it confirms the connection and the permissions in one move, and it shows you what the agent's writing actually looks like in your workspace before anything is automated.

Step 4 — Add Telegram the same way

Same pattern, different service. Ask the agent to connect Telegram. It finds the integration and opens a magic link, and this time it also explains what it needs: a bot token from @BotFather, which you get by messaging @BotFather on Telegram and sending /newbot.

Enter the PIN, paste the token into the magic-link form, finish setup. The token goes straight into the encrypted vault on your own deployment — again, never to the model.

Then restart the agent so the new channel takes effect. This step is easy to skip and the reason a freshly-connected bot sometimes appears dead.

Step 5 — Use it from your phone

Open Telegram, find your bot, and talk to it. In the video the prompt is a real one — asking for a Notion page explaining call options and put options, with the link — and the agent does from Telegram exactly what it did from the dashboard: calls the Notion tools, creates the page, returns the URL.

That is the loop closed. The agent is not on your laptop; the channel is just another way in.

The part that comes after the five minutes

Open the agent's History. Every conversation is there — the ones from the dashboard and the ones from Telegram — in one place, labelled by where they happened. You can pick up a Telegram thread at your desk and carry on.

This is the quiet argument for a deployed agent over an assistant in a browser tab. There is one agent, with one memory, reachable from wherever you happen to be, and one record of everything it did.

Where to go next

Three natural extensions, in the order most people want them: a scheduled task so it posts a summary every Monday without being asked; a second integration so it can work across two systems at once; and written procedures so it files things your way without being told each time.

For the same pattern against a system where writes have real consequences, see the Salesforce tutorial — it also shows how an agent gets built for you by another agent.