Mailer agent

Sends an email about the brief — written by the agent from a prompt you supply, plus whatever the brief actually contains. Useful for paging the on-call rota, replying to submitters, or keeping a stakeholder informed when something they care about happens.

Settings

Setting	Required	What it does
Prompt	Yes	Plain English instruction to the agent. e.g. "Notify QA when a critical bug appears" or "Reply politely to the submitter and ask for repro steps."
To	Yes	One or more recipient emails, comma-separated. Teammates and external addresses both work.
Subject prefix	No	Tag every subject so it's easy to filter — "[Lithify] " or "[critical-bug] " are common.
Include link to the brief	No (on by default)	Adds a link to the brief at the bottom of the email body so the recipient can click through.
Model	No	Defaults to the project's chat model. Override per instance if you want.

Wiring it up

The mailer agent only fires when a workflow rule tells it to. You can have several mailer instances per project, each with its own prompt and recipient list — for example:

• "qa-page" — fires on critical bugs, sends to QA.
• "submitter-reply" — fires when a brief reaches Review, thanks the submitter and lets them know it's being looked at.
• "weekly-digest" — could fire on Friday at 5pm with a roundup for stakeholders.

Add or edit instances under Project → Agents, and reference them from any rule's Then step.

What can go wrong

• Email isn't configured — the run is recorded as skipped with a clear note. Nothing else changes.
• The mail server rejects the message — the run is recorded as failed with the reason. The brief continues.
• The agent fails to draft the email — same as above. The brief is unaffected; you can retry from the brief's timeline.