DashboardSign inStart your trial

Email

The Send Email node, sending from your own domain, and the sending limits and deliverability protections that keep your mail trusted.

Rills can send email straight from a workflow, no third-party email service to wire up. This page covers the Send Email node, sending from your own domain, and the limits that keep deliverability healthy. (Receiving email is a trigger, see Inbound Email .)

#Send Email node

Sends an email as a workflow step. It costs 1 Workflow Credit per send, flat. Configure:

  • To (required), a recipient address or a {{variable}} reference.
  • CC / BCC (optional), additional recipients, each an address or variable.
  • Subject (required), up to 200 characters.
  • Body (required), HTML. Reference workflow data with {{variable}} anywhere in it.
  • Plain-text body (optional), a text fallback. Left empty, Rills generates one from your HTML.
  • Base template (on by default), wraps your body in a clean base template. Turn it off to send exactly the HTML you provide.
  • From (optional), the sender address. See the sending rules below.
  • Reply-To (optional), where replies should go.
  • Attachments (optional), each a name, content type, and a {{variable}} reference to the file data.

#Who you can send to

Sending from the default @rills.ai address is restricted to members of your workspace: this keeps Rills’ shared sending reputation clean. To email people outside your workspace, send from a domain you’ve verified (below). One exception: when a run was started by an authenticated inbound email , a Send Email node can reply to that sender even on the default address.

If a From address isn’t the default and isn’t on a domain your workspace has verified, the send is rejected: this prevents one workspace from spoofing another’s domain.

#Sending from your own domain

By default, the Send Email node sends from a @rills.ai address. To send from your own domain for better deliverability, higher limits, and a branded “from” line, verify the domain first.

Available on Professional and higher.

#Setting up

  1. Open Settings → Sender Domains and click Add domain.
  2. Enter the domain you want to send from (e.g. yourcompany.com).
  3. Rills shows you DNS records to add at your domain registrar, typically a TXT record for verification, plus DKIM and SPF records for deliverability.
  4. Add the records, then click Verify.

DNS propagation can take up to a few hours. Verification re-checks automatically; you can manually retry if needed.

#Once verified

The verified domain shows up as an option in the from field of Send Email nodes. You can use any local-part (e.g. hello@yourcompany.com, notifications@yourcompany.com): addresses don’t need separate verification.

#Multiple domains

You can verify any number of domains. Useful if you operate multiple brands or send from different domains for different workflow categories.

#Removing a domain

Removing a verified domain stops Send Email nodes configured to send from it. Existing workflows referencing the removed domain will fail until you change the from field or re-verify.

#Sending limits & deliverability

Rills protects deliverability, yours and the platform’s, with two mechanisms you may notice.

Daily send caps. Each plan has a daily cap on bulk workflow email; the cap scales with your plan. See pricing for the numbers. When a workspace reaches its cap, further Send Email steps fail for the rest of the day with an error saying the cap was reached; sending resumes the next day or when you upgrade. One-to-one transactional mail is not counted against the cap.

Abuse monitoring. Rills watches bounce and complaint rates across recent sends. If they climb past healthy thresholds, workflow email sending is paused for the workspace automatically, and Send Email steps fail until it’s resumed. Because a pause means real deliverability trouble, resuming is manual, contact support after you’ve addressed the cause. Keeping your lists clean and sending from a verified domain is the best way to never see this.

#See also