Notifier
The Notifier node dispatches alerts through one or more channels — App, Gmail, HTTP webhook, SMS, Telegram, and WhatsApp — whenever triggered by an upstream signal. Configure multiple services simultaneously; all enabled channels fire in parallel. The message body is the same across all services.
Trigger Behaviour
- 1
Connect a logic or boolean signal to the Notifier's input port. The node listens for the signal value to become non-zero (truthy).
- 2
When triggered, all enabled services fire in parallel. Each service either resolves with success: true or catches and records an error.
- 3
The node is an async action node — it uses a .signal handler rather than .proc, meaning it does not produce a time series and is not plotted.
- 4
It reports overall success (true if all enabled services succeed) plus a per-service results map for debugging failed deliveries.
Message Body
| Parameter | Type | Description |
|---|---|---|
| body | string | The message text sent to all enabled services. Supports Markdown when the service renders it (e.g. Telegram with parseMode = Markdown). |
Services
Shows a browser alert() dialog. Zero config — just enable and set the title.
titleAlert dialog title. Default: 'Alert'.Sends an email. Requires the recipient address and subject line at minimum.
toRecipient email address (required).subjectEmail subject line (required).cc / bccOptional carbon-copy and blind-copy addresses.POSTs (or any method) the message body to an arbitrary URL. Ideal for custom integrations.
urlDestination URL (required).methodHTTP method. Default: POST.headersAdditional request headers as key/value pairs.contentTypeContent-Type header. Default: application/json.timeoutRequest timeout in ms. Default: 30000.Sends an SMS via Twilio (or compatible provider). Requires credentials and destination number.
phoneNumberRecipient phone number in E.164 format (required).accountSidTwilio Account SID (required).authTokenTwilio Auth Token (required).providerSMS provider name. Default: Twilio.Sends a message to a Telegram chat via a bot. Fast, lightweight, and free.
chatIdTarget chat or channel ID (required).botTokenTelegram Bot API token (required).parseModeMessage format: Markdown, HTML, or plain. Default: Markdown.Sends a WhatsApp message via a supported API provider.
phoneNumberRecipient WhatsApp number (required).apiKeyProvider API key (required).Inputs & Outputs
| Port | Type | Description |
|---|---|---|
| Input | ||
| input | signal | Trigger signal. Non-zero value activates all enabled services. |
| Outputs | ||
| success | boolean | true if all enabled services dispatched without error. |
| results | Record<string, { success, error }> | Per-service delivery status. Keys are service names (app, gmail, http, sms, telegram, whatsapp). |
| error | string | null | Top-level error message if dispatch itself failed (null on success). |
Use Cases
Real-time trade alerts via Telegram
Wire a crossover signal through Activator, then connect to Notifier with Telegram enabled. Each time the crossover fires and the system is active, you receive a Telegram message with the configured body — all without any code.
Webhook to a trading execution service
Enable the HTTP service and point the URL at a webhook endpoint (e.g. n8n, Make, Zapier, or a custom broker API). Set the body to a JSON payload and the strategy will POST it automatically on every signal.
Multi-channel redundancy
Enable both Telegram and SMS simultaneously. If one delivery fails (network error, rate limit), the other still fires. The per-service results map tells you which channel succeeded and which didn't.