Overview #

Trigger Merge is one of the newest products from Apsona, designed to automate document generation directly from Salesforce events. It allows organizations to automatically run Apsona merge actions when Salesforce records are created or updated, eliminating the need for manual document generation.

By combining Salesforce Flow with Apsona’s powerful document merge capabilities, administrators can trigger automated document creation based on business events. Once configured, Trigger Merge runs seamlessly in the background and can automatically generate documents such as receipts, confirmation letters, invoices, agreements, or certificates using Salesforce data.

Trigger Merge is designed to integrate easily with Salesforce automation tools, allowing administrators to configure workflows that generate documents at the exact moment they are needed. This helps teams reduce manual effort, improve operational efficiency, and ensure consistent communication across processes.

Common Use Cases #

Nonprofit Organizations

Automatically generate donation receipts, acknowledgment letters, or grant-related documents when donation or fundraising records are created or updated.

Education Institutions

Generate admission confirmations, enrollment agreements, or student certificates when application status or enrollment records change.

Sales Operations

Automatically create quotes, invoices, or order confirmations when opportunities reach specific stages in the sales process.

Customer Operations

Generate onboarding documents, service agreements, or follow-up communications when customer records are updated.

Getting Started #

Before using Trigger Merge, there are two prerequisite steps required:

• One-Time Setup – A one-time configuration required by a Salesforce administrator to enable Trigger Merge in the organization.
• Product Setup – The configuration steps required to create merge actions and connect them with Salesforce Flow automations.
  

Once these prerequisites are completed, administrators can create multiple Trigger Merge automations to support different business processes.

One-Time Setup Prerequisites #

Before creating Trigger Merge automations, complete the following configuration steps:

1. Verify Apsona version is 2.307 or higher
2. Confirm the Trigger Merge add-on license is enabled
3. Make required Apsona monitoring objects visible
4. Refresh Apsona metadata
5. Configure the Apsona Connected App
6. Configure Remote Site Settings

These steps only need to be completed once by a Salesforce administrator. 

Verify Apsona Version #

Trigger Merge requires Apsona version 2.307 or later. To verify follow the steps below

Navigate to Setup in Salesforce → go to Installed Packages → Locate Apsona for Salesforce → Verify the installed version number

If your version is below 2.307, upgrade using the package link below:

https://login.salesforce.com/packaging/installPackage.apexp?p0=04tg80000001Zmx

Verify Trigger Merge Add-On License #

Trigger Merge requires an add-on license to be enabled for your organization.

Navigate to Apsona → Settings → Open License Information → Verify that the Trigger Merge add-on appears in the license list

If the license is not available, contact support@apsona.com to enable it for your organization.

 

Make Required Apsona Objects Visible #

Trigger Merge uses internal Apsona objects to track execution and store logs.

Navigate to Apsona → Settings → Open Configuration → Make the following objects visible

• Apsona Triggered Merge Run Results
• Apsona Event Log

These objects allow administrators to monitor executed Trigger Merge actions, view detailed error information, and troubleshoot any failed merges.

Refresh Apsona Metadata #

Trigger Merge requires metadata objects to be refreshed within Apsona.

Navigate to Apsona → More → Open Apsona Trigger Merge Run Results → Click Refresh Metadata

After refreshing metadata:

1. Navigate to Apsona → Apsona Items.
2. Verify that Apsona Metadata appears in the list.

Configure the Apsona Connected App #

Trigger Merge uses a Salesforce Connected App to securely communicate with the Apsona service.

Navigate to Setup → Open App Manager → Locate Apsona for Salesforce Content → Click Edit Policies

Update the following setting:

Permitted Users

Select: Admin-approved users are pre-authorized

Click Save.

Assign Profiles

Within the Connected App configuration, assign profiles that should have access.

Example profiles:

• System Administrator
• Salesforce Admin
• Automation Admin Etc

 

Configure Remote Site Settings #

Trigger Merge requires a Remote Site Setting to allow outbound requests.

Navigate to Setup → Open Remote Site Settings → Click New

Enter the following values:

Remote Site Name →  Set to Apsona_Endpoint_Config
Remote Site URL →  https://api.tmerge.apsona.com

Click Save.

 

Your one-time Trigger Merge setup in Apsona is now complete. Using the steps below, you can create and configure as many Trigger Merge automations as needed.

Creating a Trigger Merge Automation #

After completing the one-time setup, administrators can create automations that run Apsona merge actions automatically when records are created or updated using below steps.

1. Create a Merge Action
2. Create a Salesforce Flow
3. Create the Trigger Merge request
4. Test the automation
5. Verify results using logs
6. Review quota usage

 

Create a Merge Action #

A Merge Action defines the template and data used for the automation.

Navigate to Apsona → Settings → Open Merge Actions → Click Create New Merge Action → Configure the template and field mappings

Or refer this document to create the merge action 

https://www.apsona.com/docs/help-and-support/doc-mail-merge/#0-toc-title

After saving the merge action:

1. Open the created Merge Action.
2. Copy the Merge Action ID.

You will use this ID when configuring the automation flow.

Create a Record-Triggered Flow #

Trigger Merge runs using a Salesforce Record-Triggered Flow.

Navigate to Setup → Open Flows → Click New Flow →  Select Record Triggered Flow.

Configure the Flow Trigger

 

Choose the object that should trigger the merge.

Example: Contact

Select when the flow should run:

• When a record is created
• When a record is updated
• When a record is created or updated

Add conditions if needed.

Add Create Records Action #

The flow must create a Trigger Merge request.

1. Click Add Element.
2. Select Create Records.

Configure the following:

How to Set Record Field Values 

Select Option: Manually

Object

Select Option: Apsona Trigger Merge

 

 

Configure Required Fields #

If you click Reporting tools – Scheduled Jobs in Apsona, the screen shows the scheduled jobs in your org, with a list on the left and a detail panel on the right. Clicking a row in this list shows the details for that schedule, and in a child tab, it shows a list of all the previous runs of the schedule. See screenshot below.

Populate the required values for the Trigger Merge request.

Merge Action ID : Paste the Merge Action ID copied earlier.

Record ID:  Select the Record ID from the triggering object.

Example: If the flow runs on Contact, use: Contact.Id

1. Click Save.
2. Click Activate.

Your Trigger Merge automation is now active.

Test the Automation #

To verify the configuration:

1. Create or update a record that meets the flow conditions.
2. The Trigger Merge should run automatically.

Verify Execution #

You can monitor execution using Apsona logs.

Check Event Logs

Navigate to: Apsona → More →  Event Logs

Look for messages such as:

Merge completed successfully

 

 

Verify executed Merge Run Results

Navigate to: Apsona → More →  Triggered Merge Run Results

This page displays:

• Merge execution status
• Processed record details
• Error messages (if any)

Verify Quota Usage #

Verify the Quota usage under Apsona Manage license

Summary #

Creating a Trigger Merge automation involves three main steps:

1. Create a Merge Action
2. Configure a Record-Triggered Flow
3. Monitor execution using Event Logs and Run Results

This setup allows Salesforce administrators to automatically run document merges or other Apsona automations whenever records change.