Automate Airtable + Telegram
Structured records with an API worth automating. The fastest channel between your agents and your phone. Put an agent between them and the hand-off stops being manual: it reads, decides, acts, and shows its work.
Document Extractor is a ready-made agent built around Airtable; point its last step at Telegram to finish this hand-off.
Automations teams run
Each of these runs with a reasoning step between the two tools, so what reaches Telegram is a decision about the Airtable event rather than a transcription of it.
When a record is created in Airtable…
…an agent can send messages and alerts in Telegram — after reading the context and deciding it should.
When a field changes in Airtable…
…an agent can reply to commands in Telegram — after reading the context and deciding it should.
When a view gains a row in Airtable…
…an agent can deliver files and reports in Telegram — after reading the context and deciding it should.
When a message arrives in Telegram…
…an agent can create and update records in Airtable — with the reasoning recorded in the run’s receipt.
When a command is sent in Telegram…
…an agent can query views for reporting in Airtable — with the reasoning recorded in the run’s receipt.
When a schedule fires in Telegram…
…an agent can link records across tables in Airtable — with the reasoning recorded in the run’s receipt.
Copy this Airtable → Telegram workflow
Start with a custom-api call to api.airtable.com and the telegram-api node. Configure the Airtable source payload, the agent input, and the Telegram operation. The sequential template does not implement conditional writes or approval by itself.
This is a schema-checked starting point, not an end-to-end tested automation. Replace every CONFIGURE_ value, choose the operations you intend, connect credentials and map source outputs into later inputs. An edge orders steps; it does not supply a condition, an approval gate or a field mapping. Add and test those controls explicitly before any write. Cloud APIs and model providers may receive data. Keep the workflow inactive until tested with fixtures.
{
"id": "89fcaa7d-337a-4113-a64d-d3c880c3c666",
"name": "Airtable → Telegram",
"nodes": [
{
"id": "73d1de46-e7ec-4dbf-ae94-dbefc4a16016",
"text": "Run on a schedule",
"x": 512,
"y": 144,
"isEditing": false,
"type": "trigger-timer",
"icon": "connect",
"category": "trigger",
"isSelected": false,
"parameters": {
"fireOnStart": "No",
"scheduleType": "Interval",
"schedule": "Every 15 Minutes"
},
"description": "Setup template for Timer Trigger. This trigger node fires the workflow at specified intervals or at a specific time. Configure credentials, inputs and output mapping before use.",
"error": null,
"isActive": false,
"output": null,
"outputs": {}
},
{
"id": "e51b8076-5c5b-4215-a05e-2bfd1df8e73e",
"text": "Review source and draft",
"x": 512,
"y": 336,
"isEditing": false,
"type": "agnt-agent",
"icon": "connect",
"category": "action",
"isSelected": false,
"parameters": {
"agentId": "CONFIGURE_AGENTID",
"message": "Read the Airtable item. Decide whether it warrants action in Telegram, and explain why.\nSource input: CONFIGURE_SOURCE_INPUT. Produce a reviewable draft only; do not take external actions."
},
"description": "Setup template for Agent Chat. Chat with an AI agent from your agent library. Select an agent and send messages to interact with it within your workflow. Configure credentials, inputs and output mapping before use.",
"error": null,
"isActive": false,
"output": null,
"outputs": {}
},
{
"id": "44842c36-b4b6-431a-ac58-b8886e663fc8",
"text": "Configure destination in Telegram",
"x": 512,
"y": 528,
"isEditing": false,
"type": "telegram-api",
"icon": "connect",
"category": "action",
"isSelected": false,
"parameters": {
"action": "GET_ME",
"botToken": "CONFIGURE_BOTTOKEN",
"apiBaseUrl": "CONFIGURE_APIBASEURL",
"includeRaw": false
},
"description": "Setup template for Telegram API. Use Telegram Bot API from a single AGNT node. Choose an action to validate a bot, send messages/media, edit/delete messages, download files, or call any raw Bot API method. Configure credentials, inputs and output mapping before use.",
"error": null,
"isActive": false,
"output": null,
"outputs": {}
}
],
"edges": [
{
"id": "979b95df-f92a-4833-aeb4-9872d42b7f56",
"start": {
"id": "73d1de46-e7ec-4dbf-ae94-dbefc4a16016",
"type": "output"
},
"end": {
"id": "e51b8076-5c5b-4215-a05e-2bfd1df8e73e",
"type": "input"
},
"startX": 800,
"startY": 168,
"endX": 512,
"endY": 360
},
{
"id": "2b45820c-b762-4f46-a573-785ead1a0b5c",
"start": {
"id": "e51b8076-5c5b-4215-a05e-2bfd1df8e73e",
"type": "output"
},
"end": {
"id": "44842c36-b4b6-431a-ac58-b8886e663fc8",
"type": "input"
},
"startX": 800,
"startY": 360,
"endX": 512,
"endY": 552
}
],
"zoomLevel": 1,
"canvasOffsetX": 0,
"canvasOffsetY": 0,
"isTinyNodeMode": false
}Configure Telegram API
Use Telegram Bot API from a single AGNT node. Choose an action to validate a bot, send messages/media, edit/delete messages, download files, or call any raw Bot API method.
- action — Telegram operation to perform. Current example:
GET_ME. - botToken — Optional fallback Telegram bot token from @BotFather. If omitted, AGNT uses the connected Telegram provider token from Settings → Connections. Current example:
CONFIGURE_BOTTOKEN. - apiBaseUrl — Optional Bot API base URL. Use https://api.telegram.org by default, or a local Bot API server URL. Current example:
CONFIGURE_APIBASEURL. - includeRaw — Include the full raw Telegram API response when available. Current example:
false.
Install Document Extractor
Document Extractor is a working agent built around Airtable. Install it, point its last step at Telegram, and you have this hand-off without building it from an empty canvas.
Runs on your own machine · See what it does
Build it in AGNT
- Download AGNT Community Core — free and local-first.
- Connect Airtable with an API key pasted into the vault and Telegram with an API key pasted into the vault; both land in the local vault.
- Start from a marketplace workflow, or drop a custom-api node and telegram-api onto the canvas with an agent between them.
- Put an approval gate on anything consequential, then run it — the receipt shows what was read in Airtable and what was written to Telegram.
Airtable and Telegram — common questions
Can I connect Airtable to Telegram without writing code?
Yes. Airtable connects with an API key pasted into the vault and Telegram with an API key pasted into the vault, both from the local credential vault. You then describe the job in plain language — “when a record is created, send messages and alerts” — and the agent handles the rest.
How is this different from a field-mapping Airtable to Telegram automation?
The difference shows up on the messy inputs. A rule chain needs every case enumerated in advance; an agent handles pipeline trackers that stay current the way a colleague would — reading the Airtable context, judging it, then writing to Telegram with the reasoning recorded.
Does my Airtable and Telegram data leave my machine?
AGNT Community Core is local-first, so there is no vendor middleman holding your Airtable or Telegram tokens. The runtime talks directly to both services. Choose a local model and the content of what it reads never leaves the machine at all.
What does a Airtable and Telegram run leave behind?
You get an auditable trail rather than a success flag. It shows the Airtable context the agent worked from, the judgment it made about approve agent actions from anywhere, and the exact change applied in Telegram, with approvals attached where you required them.
