Auto-email after generation
Auto-email sends the finished document the moment generation succeeds, for a single record or for every record in a batch. It is configured per template and is off by default.
Configure it
Section titled “Configure it”Six fields on the Template record control it.
| Field | Purpose |
|---|---|
| Auto Email Enabled | Master switch. Default off. |
| Auto Email Template Id | Lightning or Classic Email Template. Both are supported. |
| Auto Email Recipient Field | Field path on the base object, for example Owner.Email or PrimaryContact__r.Email. |
| Auto Email Cc Field | Optional CC path. |
| Auto Email From Address Id | Org-Wide Email Address used as the From address. |
| Auto Email Save As Activity | Default on. Logs sent emails as Activities on the source record. |
The subject and body come from your chosen Email Template, with full merge-field support against the source record. The generated document is attached.
The email audit trail
Section titled “The email audit trail”Every record’s job carries its own email outcome.
| Field | Values |
|---|---|
| Email Status | Not Required (the template has auto-email off), Pending, Sent, Failed, or Skipped (no file to attach) |
| Email Sent At | Timestamp |
| Email Recipients | The actual addresses resolved at send time |
| Email Error | The reason, when the status is Failed |
If the email fails
Section titled “If the email fails”If generation succeeds but the email fails, for example because the recipient field is blank, the document still counts as successfully generated and the file is saved. The Email Status field records the failure separately.
The batch’s overall status rolls up: any failed email flips the batch to Partial Success even when every document generated cleanly.
Daily limit. Salesforce caps single-recipient emails at 5,000 per 24 hours, org-wide. A batch that would exceed the daily allotment is flagged in the pre-flight analyzer.