---
isPublished: true
knowledgeIndex: false
hidden: true
noindex: true
template: "page.peb"
title: "Room Email Action Flow Action"
description: "Render a configured email template for a Room Member and send native Salesforce email."
contentType: "reference"
audience: "admin,developer"
---

# Room Email Action

Render a configured email template for a Room Member and send native Salesforce email.
The namespaced Apex action name is `rooms__RoomEmailAction`.
Check action availability and input fields in your installed package.

## Transaction summary

| Effect | Behavior |
| --- | --- |
| API callout | No API callout is made by the action. |
| Record writes | Can save email activity when Email Save As Activity is true. Send failures and diagnostic logging can create DialogueOne Event records. |
| Queued work | No explicit DialogueOne background job is started. Native email delivery continues through Salesforce. |
| Email | Yes. Uses native Salesforce email with the prepared HTML body. |

Supply an Email Template ID, Room Member ID and Room Member Email even though the Flow input settings mark them optional.
The member must belong to the Room and reference a Contact or Lead.
The email template related-entity type must match What ID. The default What ID is the Room's related master record.
Include Room Attachments inserts links in the body; it does not attach all File bytes.
Success can reflect message preparation without reporting a later send failure. Inspect email results and Events.

## Inputs

**Required** describes the Flow input setting. The processing rules above also apply.

| API name | Flow label | Required | Default or guidance |
| --- | --- | --- | --- |
| `roomId` | Room ID | Yes | The existing Room. |
| `templateId` | Email Template ID (Related Entity Type must match whatId) | No | A Salesforce email template. Required for this template-based action. |
| `subject` | Email Subject (Overrides template subject) | No | Optional subject override. Otherwise the template subject is used. |
| `body` | Email Body (Optional - Merges with [[Body]] tag in template) | No | Optional body content inserted at `[[Body]]` in the template. |
| `replyTo` | Reply To Email Address (Default = Flow running user) | No | Defaults to the Flow running user email. A matching org-wide email address is used when available. |
| `senderDisplayName` | Sender Display Name (Default = Flow running user) | No | Defaults to the Flow running user name. |
| `memberId` | Room Member ID | No | Required for processing. The Room Member must belong to Room ID. |
| `memberEmail` | Room Member Email | No | Required for processing. The delivery email address. |
| `whatId` | What ID (Default = Room Record ID) | No | Defaults to the Room's related master record. Must match the template related-entity type. |
| `includeAttachments` | Include Room Attachments | No | Default: `true`. Adds Room document links when the template contains the attachment placeholder. |
| `saveAsActivity` | Email Save As Activity | No | Default: `false`. Requests native email activity storage. |

## Outputs

| API name | Flow label | Meaning |
| --- | --- | --- |
| `Success` | Success | Preparation result. It does not prove final delivery. |
| `Message` | Message | Preparation or validation details when supplied. Inspect Events for send failures. |
| `EmailBody` | Email Body | The prepared HTML email body. |

## Configure the Flow

1. Select the Room, member and recipient email.
2. Select a compatible email template and optional subject/body overrides.
3. Set sender and activity options.
4. Store Success, Message and Email Body. Inspect the send result before any retry.

Review the Flow context, Apex action access and the object and field permissions needed by this operation.
Record writes can run other Salesforce automation.
For API work, also review the configured Salesforce API connection user's required access.

## Troubleshooting

**Template or member validation fails.** Verify template, member, email and Room membership. Use a Contact or Lead member.

**The body is incorrect.** Check What ID, template related-entity type and Room/Member merge fields.

**Email delivery fails.** Inspect Salesforce email results and DialogueOne Events. Do not rely on Success alone and do not send again until the first result is known.

See the [Flow action index](/content/build/flows/index.md) for transaction guidance and related actions.
