Send an email

Email a report, a confirmation or a reply — from the business's own mailbox.

What it does

Sends a message from the business's own mailbox. This is the workhorse of most packages: the reminder, the summary, the receipt, the escalation. Because it goes through the business's own mail server, it arrives with their reputation behind it rather than ours.

What you need

Mail server connection from Email (SMTP). The business's own mailbox — Zoho, Google Workspace, cPanel, Microsoft 365. Their account, so the mail is already trusted for their domain; anything we sent on their behalf would spend months in spam folders. Use smtps:// for port 465.

It also needs Send from — The address customers see, and reply to. Leave blank to use the login above. Both halves are entered together.

Connecting it

Credentials belong to one project, not to your workspace and not to you. A system built for one client never runs on another client's account, and a package handed to a business runs on theirs.

Open the project and stay on the Visual Editor tab.
Open the Tools & Integrations rail on the right.
Find this tool, open it, and paste the credential.

To change it later, open the same panel — you can leave the key blank to keep the stored one and change only the other field.

Using it in a step

An Action step runs one tool with the arguments you type, exactly as written, with no model involved — so it costs nothing per run and behaves the same every time. Add one from the canvas toolbar, choose Send an email, and fill in:

Field	Required	What goes in it
`to`	yes	One email address. `{{row:email}}` when the run is about a row.
`subject`	yes	The subject line. Keep it specific — 'Fees outstanding: ₦45,000' beats 'Notice'.
`body`	yes	The message. Plain text; `{{previous}}` drops in what the step before produced.

Values can carry results forward: {{previous}} is the step before, and {{row:column}} is a column from the row this run is about when the trigger fans out.

Press Try it to run the step on its own before committing to a whole sequence.

This one really sends. Trying it delivers a real message — use your own address or number, never a customer's.

Using it with an agent

Tick Send an email on any agent that should be able to call it, and the agent decides when to. Use an agent when the judgement matters and an Action step when the certainty does.

A worked example

A school runs a fees reminder every weekday morning. A Postgres Search step finds the families with an outstanding balance, the trigger fans out one run per family, and a Deliver step emails each one — addressed with {{row:full_name}} and carrying the amount from {{row:balance}}. Nobody at the school touches it.

When it goes wrong

Nothing arrives. Almost always the sender, not the code: check the Send from address is one the mail provider has authorised. A relay will happily accept a message and drop it later if the sender is not verified.

It arrives from the wrong name. Set Who it comes from in project Settings. Note that Google Workspace and Microsoft 365 will only send as the mailbox you authenticated with, so a name they have not authorised may be replaced.