Email

Send email from your module through your workspace's own mailbox, with wording each workspace can change and retries built in.

Copy page for AIUpdated November 8, 2026

Confirmations, reminders, "your quote is ready": your module can send email without knowing anything about mail servers. It hands the platform the message, and the platform sends it through the workspace's own mailbox. No passwords in your module, no mail settings to build.

One email setup, for every module

A Workspace Admin sets email up once, under System settings › Email:

OptionWhen to choose it
Microsoft 365The company uses Outlook. Mail goes out from a real mailbox and lands in its Sent Items. It uses the workspace's Microsoft 365 connection (see Integrations).
SMTP relayAny other mail service with a relay address.

After that, every module in the workspace sends through it. The same page has Send a test message and Recent messages, so the admin can see what went out and what didn't.

Wording people can change

Your module declares each message it sends, with a name, a short description and its default subject and text. Placeholders in braces, such as {first_name} or {job_title}, are filled in when it's sent.

Each workspace gets its own copy of the wording. A Workspace Admin can reword it under Module settings › Messages, and their changes survive your updates. When you add a new message in a later version, it arrives with its default wording; messages they already changed are never overwritten.

When a send fails

A failed send doesn't crash your module. It comes back as failed, with the reason, and the platform keeps trying for about half a day, waiting longer between each try. So:

  • Don't queue a second copy every hour. The platform is already retrying.
  • Note the problem on your own record, so people can see "email not sent" where they work.
  • No email set up yet? The message fails with "Email is not set up" and goes out once the admin finishes the Email page.

Only a message that can never go (not an email address, or a message name you didn't declare) is refused outright.

Ask the Module Builder

For developers

json
"messages": [{"key": "job_done", "name": "Job complete",
  "description": "Sent to the customer when a job is closed.",
  "subject": "{job_name} is complete",
  "body": "Hi {first_name},\n\nWe finished {job_name} on {date}. Thank you!",
  "placeholders": ["first_name", "job_name", "date"]}]
python
row = await send_email("JOBS", tenant_id, customer_email, template="job_done",
                       context={"first_name": "Ada", "job_name": "Oak St.", "date": "Nov 8"})
# row["status"] is "sent" or "failed"

Good to know

  • Plain text only. No attachments and no HTML today. To share a document, send a link to the record, or a signing link.
  • Replies go to the workspace's Reply-To address unless your module sets one.
  • Email is included; it isn't metered. For a nudge inside the app instead, use Notifications.

Can't find what you need? Contact support.