Automate Salesforce + Telegram
The enterprise system of record for revenue. 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.
Lead Researcher is a ready-made agent built around Salesforce; point its last step at Telegram to finish this hand-off.
Automations teams run
These are not field mappings. An agent reads the Salesforce side, works out what it means, and only then decides what — if anything — should happen in Telegram.
When a lead or opportunity changes in Salesforce…
…an agent can send messages and alerts in Telegram — after reading the context and deciding it should.
When a task is due in Salesforce…
…an agent can reply to commands in Telegram — after reading the context and deciding it should.
When a report cycle begins in Salesforce…
…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 update records and fields in Salesforce — with the reasoning recorded in the run’s receipt.
When a command is sent in Telegram…
…an agent can create tasks and notes in Salesforce — with the reasoning recorded in the run’s receipt.
When a schedule fires in Telegram…
…an agent can extract report data in Salesforce — with the reasoning recorded in the run’s receipt.
Copy this Salesforce → Telegram workflow
Start with a custom-api call to {instance}.my.salesforce.com and the telegram-api node. Configure the Salesforce 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": "6a9cb42e-5fa2-425c-a618-d2ee390e1cb8",
"name": "Salesforce → Telegram",
"nodes": [
{
"id": "0fa4b769-c24b-4de2-ab38-6f71d09d9974",
"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": "93a14d59-522d-4c6c-adb7-17c52091be70",
"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 Salesforce 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": "eaa50d05-5078-408b-ad24-6cccb5f34d66",
"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": "144a2c1c-2098-4394-a6b6-f868568089a8",
"start": {
"id": "0fa4b769-c24b-4de2-ab38-6f71d09d9974",
"type": "output"
},
"end": {
"id": "93a14d59-522d-4c6c-adb7-17c52091be70",
"type": "input"
},
"startX": 800,
"startY": 168,
"endX": 512,
"endY": 360
},
{
"id": "802ccaa6-9098-4763-afa1-09c1db358ec6",
"start": {
"id": "93a14d59-522d-4c6c-adb7-17c52091be70",
"type": "output"
},
"end": {
"id": "eaa50d05-5078-408b-ad24-6cccb5f34d66",
"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 Lead Researcher
Lead Researcher is a working agent built around Salesforce. 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
- Install AGNT — it runs on your own machine and needs no account to start.
- Authorise Telegram (an API key pasted into the vault) and Salesforce (one OAuth sign-in). Nothing is stored anywhere but your disk.
- Describe the job in plain language, or paste the definition above; custom-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.
Salesforce and Telegram — common questions
Can I connect Salesforce to Telegram without writing code?
You can build it entirely from the canvas. Authorise Salesforce with one OAuth sign-in, Telegram with an API key pasted into the vault, then tell the agent what hygiene enforced across the pipeline 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 Salesforce to Telegram automation?
A field mapping copies values and breaks on the first record nobody anticipated. The middle step here reads the Salesforce 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 Salesforce and Telegram data leave my machine?
AGNT Community Core is local-first, so there is no vendor middleman holding your Salesforce 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 Salesforce and Telegram run leave behind?
A receipt: what was read in Salesforce, 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.