Automate Stripe + Telegram
Payments, subscriptions and the events behind 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.
Report Assembler is a ready-made agent built around Stripe; 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 Stripe into Telegram.
When a payment succeeds or fails in Stripe…
…an agent can send messages and alerts in Telegram — after reading the context and deciding it should.
When a subscription changes in Stripe…
…an agent can reply to commands in Telegram — after reading the context and deciding it should.
When a dispute opens in Stripe…
…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 look up customers and charges in Stripe — with the reasoning recorded in the run’s receipt.
When a command is sent in Telegram…
…an agent can summarise revenue activity in Stripe — with the reasoning recorded in the run’s receipt.
When a schedule fires in Telegram…
…an agent can flag anomalies in Stripe — with the reasoning recorded in the run’s receipt.
The Stripe and Telegram hand-off, setup template
Start with the stripe-invoice node and the telegram-api node. Configure the Stripe 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": "a9c4d709-cc1a-44c8-ad02-5f0b2ab896c4",
"name": "Stripe → Telegram",
"nodes": [
{
"id": "3edb950f-777e-4aa9-ad5c-d246b099b542",
"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": "c0f3857d-6aef-45cf-a3b4-82ba0b2a880e",
"text": "Read Stripe",
"x": 512,
"y": 336,
"isEditing": false,
"type": "stripe-invoice",
"icon": "connect",
"category": "action",
"isSelected": false,
"parameters": {
"customerEmail": "CONFIGURE_CUSTOMEREMAIL",
"dueDate": "CONFIGURE_DUEDATE",
"currency": "USD",
"amount": 1,
"description": "CONFIGURE_DESCRIPTION",
"lineItems": []
},
"description": "Setup template for Stripe API. Create and send a Stripe invoice with support for single or multiple line items Configure credentials, inputs and output mapping before use.",
"error": null,
"isActive": false,
"output": null,
"outputs": {}
},
{
"id": "5c9fd6df-9fd6-4385-af34-1bd836734ce2",
"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 Stripe 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": "e260ef98-918a-44e2-ae5a-9d46a77cc89c",
"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": "5c2c17fc-4fe5-4b94-a058-2f449d330f88",
"start": {
"id": "3edb950f-777e-4aa9-ad5c-d246b099b542",
"type": "output"
},
"end": {
"id": "c0f3857d-6aef-45cf-a3b4-82ba0b2a880e",
"type": "input"
},
"startX": 800,
"startY": 168,
"endX": 512,
"endY": 360
},
{
"id": "c842ee1f-a73e-46af-a5cd-e31e8271b16a",
"start": {
"id": "c0f3857d-6aef-45cf-a3b4-82ba0b2a880e",
"type": "output"
},
"end": {
"id": "5c9fd6df-9fd6-4385-af34-1bd836734ce2",
"type": "input"
},
"startX": 800,
"startY": 360,
"endX": 512,
"endY": 552
},
{
"id": "7046ef20-95dd-4304-a852-37728189e1f0",
"start": {
"id": "5c9fd6df-9fd6-4385-af34-1bd836734ce2",
"type": "output"
},
"end": {
"id": "e260ef98-918a-44e2-ae5a-9d46a77cc89c",
"type": "input"
},
"startX": 800,
"startY": 552,
"endX": 512,
"endY": 744
}
],
"zoomLevel": 1,
"canvasOffsetX": 0,
"canvasOffsetY": 0,
"isTinyNodeMode": false
}Configure Stripe API
Create and send a Stripe invoice with support for single or multiple line items
- customerEmail — Email address of the customer to bill Current example:
CONFIGURE_CUSTOMEREMAIL. - dueDate — Due date for the invoice (YYYY-MM-DD) Current example:
CONFIGURE_DUEDATE. - currency — Currency for the invoice Current example:
USD. - amount — Amount in cents for single item (e.g., 1000 for $10.00) Current example:
1. - description — Description for single item invoice Current example:
CONFIGURE_DESCRIPTION. - lineItems — Array of line items for the invoice. Each item must have 'description' and 'amount' (in cents). Example: [{"description": "Consulting", "amount": 5000, "quantity": 2}] Current example:
[].
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 Report Assembler
Report Assembler is a working agent built around Stripe. 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 Stripe 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 Stripe (an API key pasted into the vault). Nothing is stored anywhere but your disk.
- Describe the job in plain language, or paste the definition above; stripe-invoice 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.
Stripe and Telegram — common questions
Can I connect Stripe to Telegram without writing code?
You can build it entirely from the canvas. Authorise Stripe with an API key pasted into the vault, Telegram with an API key pasted into the vault, then tell the agent what failed payments chased automatically 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 Stripe to Telegram automation?
The difference shows up on the messy inputs. A rule chain needs every case enumerated in advance; an agent handles failed payments chased automatically the way a colleague would — reading the Stripe context, judging it, then writing to Telegram with the reasoning recorded.
Does my Stripe and Telegram data leave my machine?
Not to us. AGNT runs locally and both sets of credentials are encrypted on your own disk. Outbound traffic goes only to Stripe, Telegram and whichever model you chose — and pointing that at Ollama or LM Studio keeps everything on your hardware.
What does a Stripe and Telegram run leave behind?
A receipt: what was read in Stripe, 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.
