---
isPublished: true
knowledgeIndex: false
hidden: true
noindex: true
template: "page.peb"
title: "Document Batch Utils Flow Reference"
description: "Request ZIP or merge utilities for an existing document batch."
contentType: "reference"
audience: "admin,developer"
---

# Document Batch Utils

Request ZIP or merge utilities for an existing document batch.
The namespaced Apex action name is `rooms__DocumentBatchAction`.

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

## Transaction summary

| Effect | Behavior |
| --- | --- |
| API callout | Yes. The action waits for a utility-request response. |
| Record writes | No direct record insert, update or delete in the action step. Utility results are produced through the requested operation. |
| Platform event | The action does not directly publish a platform event. |
| Background work | The requested utility can continue after submission. No completion outputs are returned. |
| Email | The requested utility can email its result to Email Address. |

Select one utility. If Zip Files and Merge Files are both true, ZIP takes precedence. A Batch ID and an enabled utility are needed to submit work.

This action has no Success or Message output. A normal return is not proof that a utility completed. Caught callout errors are not returned to the Flow.

## Inputs

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

| API name | Flow label | Required | Default or guidance |
| --- | --- | --- | --- |
| `ZipFiles` | Zip Files | No | Defaults to `false`. Request a ZIP of batch files. |
| `MergeFiles` | Merge Files | No | Defaults to `false`. Request merging of batch files. |
| `EmailAddress` | Email Address | No | Notification/result email for the utility. |
| `BatchID` | Batch ID | No | Supply the existing batch record ID. |

## Outputs

This action has no Flow outputs. Connect a Fault path for exceptions that reach the Flow. Confirm the requested business result separately.

## Configure the Flow

1. Select the existing batch and the intended utility.
2. Set the result email address.
3. Connect a Fault path for exceptions that reach the Flow.
4. Confirm the utility result or notification before submitting again.

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.

## Troubleshooting

**No result or error is visible in Flow outputs.** This action has no outputs and does not expose its response. Review the resulting batch files and notification.

**You have uncommitted work pending.** The utility request is a callout. Check previous transaction work.

**Completion must drive the next step.** Use a process that checks the actual result; do not treat this action returning as completion.

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.
