Communication Nodes

> Send email from a route, either through Brickr's shared sending domain or your own provider.

All communication nodes perform an external operation, so each one requires a sequence connection.

Sending Email

send-email-brickr

Sends an email through Brickr's infrastructure. The message body is built from the connected web object, so the same visual content can be reused across routes.

| Pin | Direction | Type | |-----|-----------|------| | sequence in | Input | sequence | | to | Input | string | | subject | Input | string | | webObject | Input | asset-reference-webobject | | context | Input | object:any | | sequence out | Output | sequence | | success | Output | boolean | | messageId | Output | string |

The sender address comes from the workspace's sender identity, not from the member whose route is running. A workspace without a claimed identity cannot send: the node returns success: false with a message pointing at the setting.

Claim a sender handle in Workspace Settings under Email before using this node. Until then every send fails.

#### Sender identity

A workspace claims one handle on Brickr's shared, DNS-verified sending domain:

[email protected]

No domain setup and no DNS records are needed. Because the domain is shared across all workspaces, the handle carries the identity, so Brickr enforces three rules:

  • Handles are globally unique, compared after normalization and after folding look-alike characters. acme and 4cme cannot both exist.
  • Common role names and well-known brand names are reserved and cannot be claimed.
  • A released handle is retired permanently. Neither the workspace that held it nor anyone else can claim it again.
  • A handle can be claimed once a month, counted per workspace and unaffected by releasing.

The handle itself is permanent once claimed. The display name can be changed at any time, and Brickr always appends via Brickr to it so recipients can tell a shared-domain sender apart from a company sending on its own domain.

Set a verified reply-to address so replies land in your own inbox: the message leaves as [email protected] but replies go to [email protected]. Brickr emails a confirmation code to the address before honoring it.

#### Sending limits

Each workspace has a daily send cap, shown in Workspace Settings under Email. The cap exists because every workspace shares one sending domain and therefore one sending reputation. Exceeding it makes the node return success: false with the code daily_send_limit_reached. The counter resets at midnight UTC.

Only accepted sends count against the cap; a message the provider rejects does not. Every attempt, accepted or not, appears in the Recent emails list in Workspace Settings under Email.

send-email-resend

Sends an email through your own Resend account using a domain you have verified there. Use this when you need messages to come from your own domain instead of the Brickr handle.

| Pin | Direction | Type | |-----|-----------|------| | sequence in | Input | sequence | | apiKey | Input | string | | fromEmail | Input | string | | to | Input | string | | subject | Input | string | | html | Input | string | | sequence out | Output | sequence | | success | Output | boolean |

Store the Resend API key as a workspace secret rather than typing it into the pin.

Choosing between them

| | send-email-brickr | send-email-resend | |---|---|---| | Domain setup | None | Verify your domain at Resend | | From address | [email protected] | Any address on your domain | | Provider account | Not needed | Your own Resend account | | Daily cap | Per workspace | Your Resend plan |

Start with send-email-brickr. Move to send-email-resend when recipients need to see your own domain in the From field.