---
isPublished: true
knowledgeIndex: false
hidden: true
noindex: true
template: "page.peb"
title: "Batch Emailer Action Flow Reference"
description: "Submit email delivery for documents already generated in a Batch Run."
contentType: "reference"
audience: "admin,developer"
---

# Batch Emailer Action

Submit email delivery for documents already generated in a Batch Run.
The namespaced Apex action name is `rooms__BatchAttachmentEmailer`.

**Reference status: Limited.** Review the limitations below before using this action in a new Flow.

## Transaction summary

| Effect | Behavior |
| --- | --- |
| API callout | No HTTP callout in the action step. |
| Record writes | Queues a Salesforce batch job. The email job can create DialogueOne Event records and publish status events later. |
| Platform event | The email job can publish document-send events. These do not confirm delivery to a recipient. |
| Background work | Yes. The documents and recipient delivery list must already exist. |
| Email | The submitted job sends document emails and a completion notification. |

Another action has the same Flow label: [BatchEmailAction](/content/build/flows/BatchEmailAction.md). Select the namespaced action that matches these inputs.

The Batch Run must contain a valid delivery list. Each listed Attachment must belong to that Batch Run. The email recipient must resolve to a valid Contact, Lead or User with a usable email address.

## Inputs

Required describes the Flow input setting. Additional configuration rules can still require a value.

| API name | Flow label | Required | Default or guidance |
| --- | --- | --- | --- |
| `batchRunID` | Batch Run ID | Yes | Select the completed Batch Run that owns the generated Attachments. |
| `batchSize` | Batch Size | No | Initial value: `10`. This entry point uses a batch size of `10` regardless of this input. |

## Outputs

| API name | Flow label | Meaning |
| --- | --- | --- |
| `batchRunID` | Batch Run ID | Exposed output. It is not populated by this entry point; retain the supplied Batch Run ID. |
| `success` | Success | Whether submission raised a handled error. It does not confirm email delivery. |
| `message` | Message | Submission error details when available. |

## Configure the Flow

1. Choose the completed Batch Run and inspect its generated Attachments and recipients.
2. Confirm the email template, sender and completion-notification settings.
3. Submit the action once and retain the input Batch Run ID.
4. Monitor the email job and DialogueOne Events for delivery errors.

Confirm the Flow user's Apex action access and access to the records or Files used by this operation. Review the configured Salesforce API connection user's access when the action makes an API request. For native Salesforce email, also confirm email access, permitted sender configuration and any required activity access.

## Troubleshooting

**The job starts but email is not sent.** Check the Batch Run delivery list, Attachment ownership, recipient identity, email template and sender configuration.

**Batch Run ID is blank in the output.** Use the input ID for monitoring. Do not submit the job again only to obtain that output.

**Delivery is uncertain.** Inspect the job and send results before retrying. A repeated submission can send duplicate email.

See the [Flow action catalog](/content/build/flows/index.md) for related actions and transaction guidance. Confirm that the action and input fields are available in the installed package.
