Delivery
Sinks: Telegram, browser, webhook, AI agent
Where Subtrigger sends messages: Telegram, browser notifications, signed webhooks and AI agents, and how to test them.
3 min readUpdated
A sink is where your messages go: a Telegram chat, this browser, your server or an AI agent. Set it up once, then pick it under Send to in any alert or reminder, or in a proxy.
Kinds of sinks
| Kind | Where messages go | Plan |
|---|---|---|
| Telegram | A chat, group or channel, through your bot | Free |
| Browser notifications | Pop-ups on this device, even when the site is closed | Free |
| Webhook | A signed HTTP request to your server | Pro |
| AI agent | Your agent, with your instructions, over A2A or HTTP | Pro |
Free has 2 sinks, Pro 30. One sink can serve many alerts, reminders and proxies.
A sink's page lists every message it sent, delivered or not, with the error. Messages that fail for a temporary reason, such as a network error, are tried again.
Telegram
- Create a bot in @BotFather and copy its token.
- Add the bot to your group or channel, or send it
/startin a private chat. - Enter the chat ID, a number like
-1001234567890, or@channelfor a public channel. Then press Send test.
Send without sound makes messages arrive silently. If the token is wrong or the bot isn't in the chat, the test says so. Markdown messages (Pro) arrive formatted, JSON as a code block.
Browser notifications
Press Allow notifications and accept the browser's prompt. Messages then pop up on this device even when Subtrigger isn't open, titled with the alert's name.
A browser sink belongs to one browser. From another one you can Move to this browser, and the old one stops receiving. For both, create a sink in each.
Webhook
A webhook sends each message as an HTTPS request to your URL. Choose the method (POST, PUT or PATCH), add headers such as Authorization, and choose what to Send:
- Full event: JSON with the values, the conditions and the message.
- Message only: the alert's message as written, in its format (text, Markdown or JSON).
Every request is signed. The Subtrigger-Signature header looks like t=1794687657,v1=โฆ: an HMAC-SHA256 of the timestamp, a dot and the body, made with the sink's signing secret. Compute the same and compare; a match means the request came from your sink. The form has an example under How to check it.
A retried message keeps the same Subtrigger-Event-Id, so you can skip duplicates. Webhooks are on Pro.
AI agent
An AI agent sink hands each message to your agent with your instructions, such as "When BTC moves, find news that explains it and post a short summary". Choose the protocol:
- A2A: the Agent2Agent protocol, used by Google ADK, LangGraph, CrewAI and others. Enter the agent's address and press Check to read its card.
- HTTP: a JSON POST with the instructions, the message and the full event, for n8n or your own server. Answer with text or
{"reply": "โฆ"}.
Under Conversation, One per alert lets the agent see the earlier events of the same alert; New every time sends each event on its own. The agent's reply shows in the history. To let it read history or change alerts, give it an API key for the Subtrigger MCP server. AI agents are on Pro.
Testing
Press Send test in the sink's form, even before saving. A test message goes out right away and you see Delivered or the reason it failed; for a webhook or an agent, also its response. Test again whenever you change a token or a URL.
FAQ
Can I send one alert to Telegram and a webhook?
Yes. Pick both sinks under Send to in the alert.
Why don't browser notifications arrive?
Check that notifications for the site are allowed in the browser and the system settings, and that the sink belongs to this browser. Then press Send test.
How do I know a webhook request is genuine?
Check its Subtrigger-Signature header with your signing secret, as shown in the form.