Skip to main content
Automations need the Trader plan or above. See plans.
Every automation ends at an Action node, and that node decides where the alert goes. You pick the channels there, write the message, and set the cooldown. New automations start with In-App selected and nothing else.
A single automation trigger branching to five delivery channels: in-app, Discord, email, Telegram, and an outbound webhook

One trigger, one message, delivered independently to each channel you turned on.

​
The five channels

Alerts arrive as embedded cards in a channel of your choice. You need a webhook URL — a private address Discord gives you that lets an outside service post into one specific channel. Anyone holding that URL can post to that channel, so treat it like a password.In Discord, go to Server Settings → Integrations → Webhooks (you need Manage Webhooks permission), click New Webhook, pick the channel alerts should land in, and click Copy Webhook URL. It looks like https://discord.com/api/webhooks/000000000000/PLACEHOLDER-TOKEN. Turn on Discord on the Action node and paste it in.Tradion only accepts HTTPS URLs on Discord’s own domains. A long agent brief is split across up to three messages, sent in order.

​
Writing the message

The Action node has a template editor. Click a variable chip to insert it, and the preview underneath shows roughly what will be sent. Three variables are always available: If you have Agent nodes on the canvas, one variable per agent appears too — {research_agent}, {fundamental_agent}, {sentiment_agent}, {chart_agent}, {market_brief_agent}, and {report_agent}. These use single braces, not double.
An agent variable only works when that agent is on the canvas; type one that isn’t and the editor warns you which agent it needs. If an agent is present but produced nothing, the whole line containing its variable is dropped rather than left as a gap. There is also a Footer field, shown at the bottom of Discord and email alerts. Leave it blank to hide it.
Each channel has a Personal Insights toggle. On, the AI output draws on patterns from your own trading history — right for a private inbox. Discord, Telegram, and webhook default to off, because those channels usually have other people reading them.

​
Several channels at once

Turn on as many as you like. Each is delivered independently, so one failing does not hold up the others, and each gets its own row in the run’s notification timeline. Every channel renders the same template.

​
Delivery, retries, and failure

Sending is queued, which is what makes retries possible. A timeout or dropped connection is retried up to three times with a growing gap — roughly two seconds, then four, then eight. Configuration errors, such as a webhook URL Discord has revoked, are not retried, because retrying would change nothing.

​
In plain English

Tradion tries, tries again for about fifteen seconds, then gives up and writes down why. The run’s notification row reads Failed with the attempt count and the error text. That message is never sent again and there is no retry button.
A failing channel does not pause the automation. A revoked Discord webhook or a bouncing email address goes on failing quietly while the automation goes on firing. Automations → Runs is the only place this shows up, so check it if alerts stop arriving.
Common causes, in the order worth checking:
Webhook URLs are revoked when the target channel is deleted, when someone resets the server’s integrations, or when the webhook itself is deleted. Create a new one and paste the new URL.
You have not pressed Start on @TradionBot, or the chat ID is wrong — a group ID missing its leading minus sign is the usual version. Telegram blocks bots from messaging first, and there is nothing Tradion can do about that from its side.
Check spam, then check the address on the Action node — a typed-in address overrides your account email.
Your endpoint must be HTTPS and reachable from the public internet. Private addresses, local addresses, and plain HTTP are rejected before the request is made.

​
Next

Webhook payloads

The JSON shape and how to verify the signature.

Runs and history

See exactly which deliveries succeeded and which didn’t.