Actions

Email Node

Send automatic emails during flow execution.
updated

Email Node

The Email Node allows automatic message sending to users or groups defined in the flow. It's ideal for notifications, alerts, action confirmations, or any other automated communication within the process.

What is it for?

With this node, you can configure an email that will be sent automatically when the flow reaches this point. You can customize the message content, include dynamic variables, and choose the desired layout.

Node Fields

  • Node Name Unique identification of the node in the flow.
  • Provider Email service used for sending. Examples: SMTP, EnSpace.
  • Subject Email title that will be displayed in the recipient's inbox.
  • Base Layout Choose between the templates:
    • EnSpace: Standardized layout with header and basic formatting.
    • Empty: Blank layout, without styling or markup.
  • Body Main email content. Can contain plain text and dynamic variables for personalization, such as:
  Hello {{data.name}},
  Your process has been updated with status: {{data.status}}.

Use the email node to keep your team informed about important process updates — all automatically.

Label and value on the same line: use a table

The body is re-normalized on send. In practice, <strong> inside a paragraph becomes its own block and <br> doesn't hold the line — the label ends up on one line and the value on the next:

Amount:
R$ 12,500.00
Installment:
2/3

The format that survives is a two-column table:

A body that stays aligned
&lt;table&gt;&lt;tbody&gt;
  &lt;tr&gt;&lt;td&gt;&lt;strong&gt;Amount&lt;/strong&gt;&amp;nbsp;&amp;nbsp;&lt;/td&gt;&lt;td&gt;&amp;nbsp;&amp;nbsp;R&amp;#36;&amp;nbsp;12,500.00&lt;/td&gt;&lt;/tr&gt;
  &lt;tr&gt;&lt;td&gt;&lt;strong&gt;Installment&lt;/strong&gt;&amp;nbsp;&amp;nbsp;&lt;/td&gt;&lt;td&gt;&amp;nbsp;&amp;nbsp;2/3&lt;/td&gt;&lt;/tr&gt;
&lt;/tbody&gt;&lt;/table&gt;
cellpadding and inline style don't survive. Add the spacing with &amp;nbsp; in both cells: the label column is sized by its widest text, so on the longest label the value touches it.

Never write a raw dollar sign in the body

The layout assembles the message by replacing a placeholder with your body. In that replacement, the sequence $& has a special meaning and gets swapped for the placeholder itself. What lands in the inbox:

R{{-body-}}nbsp;12,500.00
The character right after $ must not be &. The other patterns bite too: $$, $`, $', $< and $1–$9 — meaning R$1,500.00 would turn into something else. A plain space after the symbol is safe; &amp;nbsp; is not.

Swapping $ for the entity &amp;#36; is not enough on its own: the entity is decoded before the substitution, so if an &amp;nbsp; follows it, the problem comes back.

This is a platform defect, not a defect of the sending provider. The template placeholder is being substituted with String.replace, which interprets dollar patterns in the replacement text.

This applies to the output of a currency format as well, since it already contains the symbol. For currency in an email, format as decimal and write the symbol by hand.

Where to check what was sent

Settings → Emails → Sent Emails → View Email stores the body of every message sent and renders it. That's where you verify alignment and variables without depending on somebody's inbox.

Comparison Notification Node

Send automatic notifications based on comparison results configured in the workspace.

Form Node

Request form completion during flow execution.