Saltar al contenido principal

Notification

Category: Integration
Node id: notification

Sends notifications via email (SMTP), SMS (platform messaging carrier), Slack or webhook. Push is not available.

What it does​

  • Delivery over email (SMTP connector), SMS (platform messaging carrier), Slack and webhook; push fails explicitly
  • Priority levels: low, medium, high, urgent
  • Configurable retry logic with count and delay
  • Slack Block Kit support for rich message formatting
  • Unique notification ID generation for tracking
  • Channel-specific configuration (SMTP, sender number, Slack/webhook URL)

Use cases​

  • Send Slack alerts when a pipeline detects a critical condition
  • Notify on-call staff via SMS for urgent healthcare events
  • Email stakeholders when batch data processing completes
  • Push notifications to mobile apps for patient status updates
  • Webhook callbacks to external systems for event-driven architectures

Runtime​

  • Performance tier: variable

Input ports​

NameTypeRequiredDescription
recipienttextYesNotification recipient (email, phone, channel, URL, or device token)
messagetextYesNotification message body
subjecttextNoNotification subject (for email and push)
metadatajsonNoAdditional metadata to include with the notification

Output ports​

NameTypeRequiredDescription
resultjsonNoNotification delivery summary with id, channel, recipient, status, priority, and sent_at
successbooleanNoWhether the notification was sent successfully

Settings​

Basic​

SettingNameTypeRequiredDefaultAllowed valuesDescription
ChannelchannelenumYesemailemail, sms, slack, webhook, pushNotification delivery channel
PrioritypriorityenumNomediumlow, medium, high, urgentNotification priority level

Auth​

SettingNameTypeRequiredDefaultAllowed valuesDescription
SMTP Hostsmtp_hoststringNoSMTP server for email channel
SMTP Portsmtp_portnumberNo587SMTP port for email channel
SMTP Usersmtp_userstringNoSMTP username for email channel
SMTP Passwordsmtp_passwordsecretNoSMTP password for email channel
From Addressfrom_addressstringNoSender address for email channel
SMTP TLS Modesmtp_tls_modeenumNostarttlsstarttls, tls, noneTransport security for email
SMS Providersms_providerenumNotwiliotwilioIgnored: SMS goes through the platform's messaging carrier
SMS API Keysms_api_keysecretNoIgnored: carrier credentials are platform configuration
From Numberfrom_numberstringNoSender number for SMS; must belong to the organization. Empty uses the organization's default sender
Slack Webhook URLslack_webhook_urlsecretNoSlack incoming webhook URL
Webhook URLwebhook_urlstringNoTarget URL for webhook channel
Webhook Methodwebhook_methodenumNoPOSTPOST, PUTHTTP method for webhook
Push Providerpush_providerenumNofcmfcmNot available: the push channel always fails
Push API Keypush_api_keysecretNoNot available: the push channel always fails

Advanced​

SettingNameTypeRequiredDefaultAllowed valuesDescription
Retry Countretry_countnumberNo3min 0; max 10Number of retry attempts
Retry Delay (ms)retry_delay_msnumberNo1000min 0Delay between retries in milliseconds
Webhook HeadersheadersjsonNoCustom HTTP headers for webhook notifications

Errors​

CodeDescription
MISSING_RECIPIENTRecipient input is required but was not provided
MISSING_MESSAGEMessage input is required but was not provided
UNSUPPORTED_CHANNELNotification channel is not one of: email, sms, slack, webhook, push
DELIVERY_FAILEDNotification delivery failed after all retry attempts
CHANNEL_CONFIG_MISSINGRequired configuration for the selected channel is missing

Runtime notes​

  • On failure after all retries, the node returns the result with status='failed' AND returns an error
  • success is true only when status='sent'; downstream nodes should check both
  • Each notification gets a unique ID (notif_<timestamp>_<seq>) for tracking; SMS adds the carrier's provider_message_id
  • A channel that cannot deliver fails: SMS without a configured carrier, and push (no provider), never report success
  • Retry logic sleeps between attempts; total latency = retry_count * retry_delay_ms in worst case

See Build any workflow for how to put nodes together and Ports, types and data flow for how port types connect.

¿Algo no está claro? Envíe sus comentarios sobre la documentación por correo electrónico..