Skip to content

Guide4 min read

How to save Telegram messages to Notion

On this page

Thrum has a starter that saves every message sent to a client's Telegram bot as a row in their Notion database, and Zapier offers a template for the same job. Field staff, drivers and clients themselves often find a quick Telegram message the easiest way to send a request, a reading from a site visit or a note that a job is done. The trouble starts when those messages need finding again next week, and a database row gives the team something to sort, assign and tick off.

Zapier

Zapier's Notion and Telegram page includes the template "Create new items in Notion from new Telegram messages". On the Telegram side, Zapier's event starts instantly when your bot receives a message, and the Notion side lists actions such as updating a data source item, or finding one and creating it when it does not exist (data source is the term Zapier uses). Most of the other templates on that page go the opposite way, sending Telegram messages when Notion items are added or updated.

Notion and Telegram may each offer ways of their own to connect the two, and Notion's help centre and Telegram's bot documentation are where to look for them.

Setting it up in Thrum

The starter is "Add a database row in Notion when a message is sent to the bot in Telegram". Telegram tells Thrum about each message within seconds of it reaching the bot.

  1. Install the starter. In Templates → Library, open it and install it into the client. It starts switched off, with a checklist of two connections and two fields.
  1. Create the bot. In Telegram, message @BotFather, send /newbot and copy the token. Paste it as the client's Telegram connection. Then add the bot to the client's group, or have the client message it once.

  2. Create the Notion connection. At notion.so/profile/integrations, make a new internal integration (Notion's word for a connection) in the client's workspace. Tick the capabilities Read content, Insert content and Update content, and copy the secret. Then open the database, choose ••• then Connections, and add it there (this is what lets it reach that database). The starter needs that last step to reach the database.

  3. Fill in the two fields. "Notion: Database ID" is the 32 characters in the database's address. "Notion: Title column" is the name of the database's title property, often Name.

The checklist for an example client with the bot and Notion connected and the database ID and title column filled in.
  1. Change the title to the message. As installed, each row's title is the chat's group name, which is the same for every message from one group. Open the Notion step and set the title to the message itself ({{ trigger.payload.text }}). The trigger (the step that starts the workflow) also carries the sender's first and last name, their username, the chat's ID and type, and when the message was sent, so you can work any of them into the title.
The installed workflow on the canvas, the Telegram message step leading to the step that adds the Notion row.
  1. Set defaults in Notion, then switch on. The step sets the title only. Notion types its other columns itself, so give a Status or an Assignee column a default in Notion, and new rows arrive ready to sort. Switch the workflow on and send the bot a test message. A row appears in the database within seconds.

Two Telegram rules to plan around

One bot, one listener. A Telegram bot sends its incoming messages to one place. Thrum lets one workflow listen per bot, and no other tool can read that bot's messages at the same time. If the client already uses a bot elsewhere, make a new one for this.

Groups hear less by default. In a group, the bot only sees commands, replies to it and messages that mention it. To save every message in the group, turn privacy mode off for the bot in BotFather.

When Notion is slow or refuses

If Notion is busy or answers with a server error, Thrum tries the step again after 5 seconds and then at doubling waits, up to 3 attempts. Any other refusal fails the step at once, and the first thing to check is the connection from step 3 (the database's Connections list). Adding a row is never repeated after a dropped connection without you, because the row may already be there.

Going the other way

The same pair can post into Telegram when the database changes. "Send a message in Telegram when a row is added to a database in Notion" checks every 15 minutes and sends the page's link, when it was added and when it was last edited, to the chat ID you give. The version for changed rows works the same way. Notion rounds edit times to the minute, so two edits within one minute count as one change. Both use the data source ID from the database's settings, under Manage data sources. The Notion and Telegram page lists all of these with their starters.

Checked on 14 November 2026.

Sources

Thrum is cooking.

Get early access and you’ll be among the first in. Early members get a launch perk.