Skip to content

Communication

Nodes for sending and reading email and sending notifications. In the palette they sit under Communication, together with HTTP Request and Integration Automation.

For chat platforms (Slack, Microsoft Teams, Telegram, WhatsApp and others), use the dedicated connector nodes in the Connector catalog. They're richer than the generic options below.

Email

What: Sends, reads, searches or deletes email, through Flero's own mail service or your own mail server.

The Email node's panel in the editor: the header with the node's icon and name, and its Settings tab.The Email node's panel in the editor: the header with the node's icon and name, and its Settings tab.

Ports: in input; out output, error.

Configuration:

Field Notes
operation Required: send, read, search or delete
emailService platform (default): send through Flero's mail service. custom: use your own server.
connection For custom: your SMTP (sending) or IMAP (reading) server details
to Recipient(s)
subject Subject line
body The message
isHtml Send body as HTML. Default off.
folder For read and search. Default INBOX.
limit For read and search. Default 10.

Example:

operation: send
to:        {{ $trigger.payload.customerEmail }}
subject:   Your order #{{ $trigger.payload.orderId }} has shipped
isHtml:    true
body: |
  <p>Hi {{ $trigger.payload.customerName }},</p>
  <p>Your order is on its way. Track it here: {{ $node["Create label"].output.trackingUrl }}.</p>

Tips:

  • A failed send goes to the error port. It is not reported as a success.
  • Test with Sandbox mode to avoid sending real emails while you build.
  • HTML email needs inline CSS to look right in most mail clients.
  • For high-volume or marketing email, use a transactional email connector such as SendGrid or Mandrill.

Notification

What: Sends a notification by email, SMS, push, Slack, Discord, Microsoft Teams or webhook.

The Notification node's panel in the editor: the header with the node's icon and name, and its Settings tab.The Notification node's panel in the editor: the header with the node's icon and name, and its Settings tab.

Ports: in input; out output.

Configuration:

Field Notes
channel Required: email, sms, push, slack, discord, teams or webhook
message Required. The notification text.
subject For channels that have one
recipient Who or where to send it: an address, a number, a channel or a URL
credentials Required. The details the channel needs.
priority low, normal (default), high or urgent

Use case: Lightweight alerting for ops workflows ("the nightly sync failed"), and simple customer notifications.

Tips & gotchas

  • For real chat apps, use the connectors. The Slack connector, for example, handles threads, rich messages, interactive buttons and waiting for a reply.
  • SMS rules vary by country. Some countries require sender registration. Check before going live.
  • Set up SPF and DKIM on your sending domain when you send from your own mail server, or your mail may land in spam.

Found something out of date? This page lives in the Flero docs content set.