Prerequisites

• Create the Flow that will submit your MergeUp merge requests.
• Have the Template Id and any record data needed to set the mergeup__Merge_Parameters input properties.
• Know where you want to monitor the merge after submission, such as the related Merge Log or MergeUp Batch.

Overview

Merge Document (Async) is the Flow action to use when a bulkified transaction may submit more than 10 merge requests or when the flow does not need to receive the merged file immediately. The action creates one MergeUp Batch for the whole invocation and, in bulkified execution, returns one response per input row so the flow can track progress later.

When the async action creates a MergeUp Batch, the batch summary email and in-app notification settings on that batch still control what summary messages are sent after processing completes. Org-wide defaults can also be set through MergeUp Global Configuration.

Steps

1. Add the Merge Document (Async) action to your flow. In record-triggered flows, place it on the Run Asynchronously path.

2. In the action input configuration, set the individual mergeup__Merge_Parameters properties. At minimum, set Template Id and any required Record Id value.

3. Map each property directly from flow resources (for example, {!$Record.Id}) or from formulas/constants as needed.

4. Store the returned response values. For the complete output field reference, see Merge_Async_Response. The most commonly used outputs are:

   • MergeUp Batch Id: Identifies the shared MergeUp Batch for the submission.
   • Merge Log Id: Identifies the Merge Log for the individual merge request.
   • Apex Job Id: Identifies the Async Apex job that is processing the MergeUp Batch.

5. After submission, monitor the related Merge Logs or the shared MergeUp Batch until the merge completes.

Notes

• The synchronous Merge Document action supports a maximum of 10 merge requests per transaction. Use Merge Document (Async) above that limit.
• The action method accepts List<Merge_Parameters> and creates one MergeUp Batch per invocation, with one Merge Log per input item.
• In Flow authoring, you set the action's Merge_Parameters properties directly. In bulkified transactions, Salesforce invokes the action in bulk and passes multiple inputs to Apex automatically.
• If you already set a Merge Log upsert key on a Merge Parameters row, the async action preserves and returns that key.
• The merged file is not returned immediately. Poll the related Merge Log when you need to know whether the document finished successfully.
• Batch summary delivery is enabled by default. After submission, use the related MergeUp Batch record if you need to confirm whether Send Batch Summary Emails or Send Batch Summary Notifications are enabled for that run.
• Org administrators can change the default behavior for all batches from the MergeUp Global Configuration custom metadata record by updating Enable Batch Summary Emails and Enable Batch Summary Notifications.

Next Steps

• MergeUp Global Configuration
• About MergeUp Batches
• Monitor a MergeUp Batch
• Monitor the MergeUp Batch Apex Job