Automate Notion + Telegram
The team wiki agents can actually keep current. 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.
Content Producer is a ready-made agent built around Notion; point its last step at Telegram to finish this hand-off.
Automations teams run
Unlike field-mapping automation, the step in the middle is an agent: it can summarise, classify, judge and draft, not merely copy values from Notion into Telegram.
When a page is created or edited in Notion…
…an agent can send messages and alerts in Telegram — after reading the context and deciding it should.
When a database row changes in Notion…
…an agent can reply to commands in Telegram — after reading the context and deciding it should.
When a status flips in Notion…
…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 pages in Notion — with the reasoning recorded in the run’s receipt.
When a command is sent in Telegram…
…an agent can write database rows in Notion — with the reasoning recorded in the run’s receipt.
When a schedule fires in Telegram…
…an agent can append meeting notes in Notion — with the reasoning recorded in the run’s receipt.
Notion to Telegram, setup template
Start with the notion-api node and the telegram-api node. Configure the Notion 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": "3c524a19-4ace-4aba-ac9e-00d1ea2a983c",
"name": "Notion → Telegram",
"nodes": [
{
"id": "e931e537-9210-4159-ac7c-06fc595f2a1a",
"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": "70227d29-49b8-4b63-abc5-366ace5d3a8e",
"text": "Read Notion",
"x": 512,
"y": 336,
"isEditing": false,
"type": "notion-api",
"icon": "connect",
"category": "action",
"isSelected": false,
"parameters": {
"operation": "search",
"pageSize": 1,
"query": "CONFIGURE_QUERY",
"filterType": "all"
},
"description": "Setup template for Notion API. Interact with Notion - search, query databases, get pages, and create pages. Configure credentials, inputs and output mapping before use.",
"error": null,
"isActive": false,
"output": null,
"outputs": {}
},
{
"id": "0f3a1e44-eabf-4069-a05d-7b87ed38c3c2",
"text": "Review source and draft",
"x": 512,
"y": 528,
"isEditing": false,
"type": "agnt-agent",
"icon": "connect",
"category": "action",
"isSelected": false,
"parameters": {
"agentId": "CONFIGURE_AGENTID",
"message": "Read the Notion 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": "9938eebc-7870-4156-af88-700ccee6ff04",
"text": "Configure destination in Telegram",
"x": 512,
"y": 720,
"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": "835c9108-cda2-46ec-a3ea-c578dbb01250",
"start": {
"id": "e931e537-9210-4159-ac7c-06fc595f2a1a",
"type": "output"
},
"end": {
"id": "70227d29-49b8-4b63-abc5-366ace5d3a8e",
"type": "input"
},
"startX": 800,
"startY": 168,
"endX": 512,
"endY": 360
},
{
"id": "f05a7c47-acf8-404f-a135-d7ea0595adc2",
"start": {
"id": "70227d29-49b8-4b63-abc5-366ace5d3a8e",
"type": "output"
},
"end": {
"id": "0f3a1e44-eabf-4069-a05d-7b87ed38c3c2",
"type": "input"
},
"startX": 800,
"startY": 360,
"endX": 512,
"endY": 552
},
{
"id": "aac6059f-ee6a-4dca-aad8-75cbf6301db8",
"start": {
"id": "0f3a1e44-eabf-4069-a05d-7b87ed38c3c2",
"type": "output"
},
"end": {
"id": "9938eebc-7870-4156-af88-700ccee6ff04",
"type": "input"
},
"startX": 800,
"startY": 552,
"endX": 512,
"endY": 744
}
],
"zoomLevel": 1,
"canvasOffsetX": 0,
"canvasOffsetY": 0,
"isTinyNodeMode": false
}Configure Notion API
Interact with Notion - search, query databases, get pages, and create pages.
- operation — Operation to perform Current example:
search. - query — Search query text Current example:
CONFIGURE_QUERY. - filterType — Filter results by type Current example:
all. - pageSize — Max results (default: 10-100) Current example:
1.
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 Content Producer
Content Producer is a working agent built around Notion. 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
What building this looks like
- Download AGNT Community Core — free and local-first.
- Connect Notion with one OAuth sign-in and Telegram with an API key pasted into the vault; both land in the local vault.
- Start from a marketplace workflow, or drop notion-api 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 Notion and what was written to Telegram.
Notion and Telegram — common questions
Can I connect Notion to Telegram without writing code?
No code is required. Add both connections in the vault (Notion uses one OAuth sign-in, Telegram uses an API key pasted into the vault), then either install a marketplace workflow for this pair or drag the two nodes onto the canvas and put an agent between them.
How is this different from a field-mapping Notion to Telegram automation?
Mapping tools move data; this reasons about it. Rather than copying a field into Telegram, the agent can weigh what arrived from Notion, classify it against criteria you wrote in prose, draft something new, and act only when it is warranted.
Does my Notion and Telegram data leave my machine?
Your credentials stay in a vault on your own disk rather than in someone else’s cloud. The only calls made are the ones the workflow needs: Notion, Telegram, and your chosen model provider — which can be a local one.
What does a Notion and Telegram run leave behind?
You get an auditable trail rather than a success flag. It shows the Notion 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.
