Automate GitHub + Telegram
Where the code — and half the process — lives. 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.
First-Pass Reviewer is a ready-made agent built around GitHub; 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 GitHub into Telegram.
When a PR opens or merges in GitHub…
…an agent can send messages and alerts in Telegram — after reading the context and deciding it should.
When an issue is filed in GitHub…
…an agent can reply to commands in Telegram — after reading the context and deciding it should.
When a release is cut in GitHub…
…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 comment on PRs and issues in GitHub — with the reasoning recorded in the run’s receipt.
When a command is sent in Telegram…
…an agent can open issues with structured detail in GitHub — with the reasoning recorded in the run’s receipt.
When a schedule fires in Telegram…
…an agent can draft release notes in GitHub — with the reasoning recorded in the run’s receipt.
GitHub to Telegram, setup template
Start with the github-api node and the telegram-api node. Configure the GitHub 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": "79ae9679-68ed-422c-ad66-50572a27ac6c",
"name": "GitHub → Telegram",
"nodes": [
{
"id": "30341ab0-5090-4c64-a802-0408c8a682fc",
"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": "c8f39d02-1ebf-4dfa-a241-cf76c6a7a944",
"text": "Read GitHub",
"x": 512,
"y": 336,
"isEditing": false,
"type": "github-api",
"icon": "connect",
"category": "action",
"isSelected": false,
"parameters": {
"action": "GET_AUTHENTICATED_USER",
"owner": "CONFIGURE_OWNER",
"repo": "CONFIGURE_REPO"
},
"description": "Setup template for GitHub API. Interact with GitHub: repos, branches, files, issues, comments, pull requests, reviews, releases, Actions/CI, and search. Configure credentials, inputs and output mapping before use.",
"error": null,
"isActive": false,
"output": null,
"outputs": {}
},
{
"id": "1635de62-5232-4777-afdc-b98315fb905e",
"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 GitHub 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": "afdcf2f7-19b6-40d8-a5ac-c841e5aa5808",
"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": "1fe4b153-16fc-40c6-a3d4-8b21c28a2ebc",
"start": {
"id": "30341ab0-5090-4c64-a802-0408c8a682fc",
"type": "output"
},
"end": {
"id": "c8f39d02-1ebf-4dfa-a241-cf76c6a7a944",
"type": "input"
},
"startX": 800,
"startY": 168,
"endX": 512,
"endY": 360
},
{
"id": "888a066b-da4f-44e9-adcf-89a67d6e8d4e",
"start": {
"id": "c8f39d02-1ebf-4dfa-a241-cf76c6a7a944",
"type": "output"
},
"end": {
"id": "1635de62-5232-4777-afdc-b98315fb905e",
"type": "input"
},
"startX": 800,
"startY": 360,
"endX": 512,
"endY": 552
},
{
"id": "e656313f-7b83-4f0d-afd9-1ef8bc2674e6",
"start": {
"id": "1635de62-5232-4777-afdc-b98315fb905e",
"type": "output"
},
"end": {
"id": "afdcf2f7-19b6-40d8-a5ac-c841e5aa5808",
"type": "input"
},
"startX": 800,
"startY": 552,
"endX": 512,
"endY": 744
}
],
"zoomLevel": 1,
"canvasOffsetX": 0,
"canvasOffsetY": 0,
"isTinyNodeMode": false
}Configure GitHub API
Interact with GitHub: repos, branches, files, issues, comments, pull requests, reviews, releases, Actions/CI, and search.
- action — The action to perform on GitHub Current example:
GET_AUTHENTICATED_USER. - owner — The owner of the repository (not needed for account-level or search actions) Current example:
CONFIGURE_OWNER. - repo — The name of the repository (for CREATE_REPO: the name of the new repository) Current example:
CONFIGURE_REPO.
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 First-Pass Reviewer
First-Pass Reviewer is a working agent built around GitHub. 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
Wiring GitHub to Telegram
- Install AGNT — it runs on your own machine and needs no account to start.
- Authorise Telegram (an API key pasted into the vault) and GitHub (one OAuth sign-in). Nothing is stored anywhere but your disk.
- Describe the job in plain language, or paste the definition above; github-api does the reading and telegram-api the writing.
- Gate anything you would not want done unattended, then let it run and read the first receipt end to end.
GitHub and Telegram — common questions
Can I connect GitHub to Telegram without writing code?
You can build it entirely from the canvas. Authorise GitHub with one OAuth sign-in, Telegram with an API key pasted into the vault, then tell the agent what first-pass review on every diff should look like once Telegram is involved. Code is an option for the unusual cases, never a requirement for the common ones.
How is this different from a field-mapping GitHub to Telegram automation?
A field mapping copies values and breaks on the first record nobody anticipated. The middle step here reads the GitHub item in full and decides — whether it matters, how to summarise it, and what belongs in Telegram. Deciding to do nothing is a valid outcome, which no mapping can express.
Does my GitHub and Telegram data leave my machine?
AGNT Community Core is local-first, so there is no vendor middleman holding your GitHub 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 GitHub and Telegram run leave behind?
A receipt: what was read in GitHub, which tools ran with which arguments, what the agent concluded, and what it wrote to Telegram. Anything consequential can sit behind an approval gate so a person signs off before it happens.
