Skip to content

Guide4 min read

Telegram messages for new Airtable records

How to send a Telegram message when an Airtable record is added

On this page

Where a client's staff talk in a Telegram group, a bot in that group is the shortest path from "a new order is in the base" to "someone is on it". This guide sets up a bot message for every new Airtable row. It covers Zapier's version briefly and spends most of its length on Thrum, where the bot belongs to the client and the message goes out within one 15-minute check of the table.

Before you start, whichever tool you use

You need a Telegram bot. In Telegram, message @BotFather, send /newbot, follow its questions and copy the token it gives you. Treat the token like a password. Then either add the bot to the client's group, or have the person who should receive the messages send the bot one message first, since the bot writes only to chats it is part of.

Telegram may offer other ways to do this through its own bot tools, and Telegram's bot documentation is the place to read about them. Inside Airtable, Airtable's help centre sends calls to outside services through the "Run a script" action, which means writing and maintaining code.

With Zapier

Zapier's Airtable and Telegram page offers "Send messages in Telegram for new records in Airtable" and a version for new or updated records. Its Telegram action sends a message from your bot, and Zapier also has a Telegram event that starts instantly when your bot receives a message, for the reverse direction. The Airtable "New Record" event handles new records and records the first time they enter a chosen view. Zapier's Free plan checks for new data every 15 minutes.

With Thrum

Thrum's starter is "Send a message in Telegram when a record is added in Airtable". It reads the client's base with the client's token and sends with the client's bot, inside that client's own workspace.

  1. Install the starter. Templates → Library, open the starter, pick the client, install. You get the workflow switched off plus a checklist of two accounts and three fields.
  1. Connect the bot. Paste the token from @BotFather as the client's Telegram connection. Thrum stores it encrypted with the client's other keys.

  2. Connect Airtable. Create a token at airtable.com/create/tokens with data.records:read and data.records:write, and add the client's base to its access list.

  3. Fill in the Chat ID. "Telegram: Chat ID" is where the bot writes. For a group, it is a number such as -1001234567890. For a public channel, it can be its @name. The bot has to be a member of that group or channel.

  4. Fill in the base and table. "Airtable: Base ID" is the appXXXXXXXXXXXXXX code, and "Airtable: Table" is the table to watch, for example Leads.

The setup for an example client, bot and Airtable token connected, with the chat ID, base ID and table filled in.
  1. Write a message worth reading, then switch it on. As installed, the bot sends two lines, "A record is added in Airtable." and "Added at:" followed by the row's creation time. Change them in the Telegram step to the columns the team needs ({{ trigger.payload.fields.Address }} brings in a column called Address). Once switched on, Thrum checks the table every 15 minutes and sends one message per new row, oldest first, leaving out rows that were already there.
The workflow on the canvas after installing, Airtable's new-record step joined to the Telegram message step.

Photos and files

Telegram has two more steps in Thrum. "Send a photo" sends a picture from a web address, and "Send a file" sends a PDF, an invoice or a report the same way. Each takes files up to 4.5 MB with an optional caption. Pointing either at a link from an earlier step lets the bot share a quote or a job photo alongside the alert.

When a row changes instead

For alerts about progress, such as a delivery marked out, use "Send a message in Telegram when a record is changed in Airtable". It needs a field of the type "Last modified time" in the table, named in the starter, and it can be narrowed to rows in one view. Like the first, it checks every 15 minutes.

Messages to the bot, saved in Airtable

The pair works the other way too. With "Create a record in Airtable when a message is sent to the bot in Telegram", each message reaches Thrum within seconds and becomes a row holding the text, the sender's first name, the group's name and whether the chat is private or a group. Two rules come with it. A bot sends its incoming messages to one place, so only one workflow can listen per bot, and no other tool can use that bot's updates at the same time. In a group, the bot sees only commands, replies and mentions unless privacy mode is switched off in BotFather.

If Telegram says no

A busy or failing Telegram is retried after 5 seconds and then at doubling waits, up to 3 attempts. Any other refusal fails the step straight away, so check the Chat ID and that the bot is in the group. If a message may have gone out before the connection dropped, Thrum leaves the retry to you so the group does not see it twice.

All the ways the two apps join are on the Airtable and Telegram page.

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.