Skip to content
Docs
flero.ai

Communication

Nodes for sending messages, notifications, and real-time updates.

For chat-platform integrations (Slack, Teams, Discord, etc.), use the dedicated connector nodes in the Connector catalog, they're richer than the generic options below.

Email

What: Sends an email via SMTP.

Inputs: Email fields (to, subject, body…).

Outputs: messageId, accepted, rejected arrays.

Configuration:

Field Notes
Credential SMTP connection (host, port, user, password, TLS), or use a transactional-email connector (SendGrid, AWS SES, Mailgun) instead
From Sender address (must be authorised by your SMTP provider)
To Recipient(s), comma-separated or array
Cc, Bcc Optional
Subject Required
Body, text Plain-text version
Body, HTML HTML version (most clients prefer this; both is best)
Attachments Array of { filename, content, contentType }
Reply-To Optional
Headers Custom headers (rare)

Example:

To:      {{ $trigger.body.customerEmail }}
Subject: Your order #{{ $trigger.body.orderId }} has shipped
Body — HTML: |
  <p>Hi {{ $trigger.body.customerName }},</p>
  <p>Your order is on its way. Track it here: {{ $node["Create label"].json.trackingUrl }}.</p>

Tips:

  • Use a transactional email provider (SendGrid, Postmark, SES) for production, better deliverability than raw SMTP.
  • Test in sandbox mode to avoid sending real emails during development.
  • HTML bodies need inline CSS for compatibility with most email clients. Avoid <script>.

Notification

What: Sends a notification to a delivery channel, push notification, SMS, or in-app.

Channels:

Channel What it does
Push Mobile / desktop push via FCM, APNs, or web-push (configured per workspace)
SMS Text message via Twilio / AWS SNS / Vonage
In-app Toast notification in the recipient's Flero UI
Webhook POST to a URL

Configuration: Channel-specific. SMS needs a credential and a phone number; push needs a device token; in-app needs a user ID.

Use case: Lightweight alerting for ops workflows ("the deploy succeeded"), customer notifications ("your appointment is in an hour").

Real-time Communication

What: Send messages over a WebSocket or Server-Sent-Event connection. Useful for live dashboards, real-time updates to a custom front-end you've built that listens to Flero events.

Operations: publish (to a channel), subscribe (in a separate workflow).

Use case: Pushing workflow execution updates to your own dashboard, broadcasting events to many connected clients.

Tips & gotchas

  • For real chat apps (Slack, Teams, Discord), use the connectors. The connectors handle threading, rich blocks, file uploads, and reactions in a typed way the generic email/notification nodes don't.
  • SMS regulations vary by country. Twilio and friends require sender registration in some jurisdictions; verify before going live.
  • Don't use email for transactional flows where deliverability matters without DKIM / SPF set up on the sender domain. Test with mail-tester.com before launch.
  • In-app notifications respect user Notification Settings in the receiver's account, they may not see your message if they've turned off that category.

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