Merge Internal Datasource Value
The Merge Internal Datasource Value action is used to merge a partial object into an existing object stored in an Internal Datasource.
This action only works on top-level keys and object properties.
You cannot delete a specific value inside an array.
When to Use
Use this action when you want to merge fields into an existing object in your Internal Datasource.
It’s typically used for:
- Updating only one or a few fields without overwriting the full object
- Enriching data with additional values based on user interaction or logic
- Updating status flags, visibility booleans, timers, etc.
Requirements
The Editable From Display setting must be enabled on the Internal Datasource.
Learn more: Alternative Datasource Settings
Action Behavior
- Merges the incoming object into the one at the target path
- If a key already exists, its value will be overwritten
- If a key does not exist, it will be added
Configuration Options
Field | Description |
---|---|
Datasource | The Internal Datasource path to the value you want to override. |
Value Origin | Selector to choose where the replacement value comes from. |
Value Origin Options
Type | Description |
---|---|
Received Value | The primary value received from the trigger. Usually refers to the value field. |
Static Value | A constant, hardcoded value. |
Property of Received Value | Extracts a specific property from the full trigger object (e.g., event , id , or value ). Supports dot notation for accessing nested values (e.g., value.payload.amount ). |
Example
Given this initial Internal Datasource:
{
"status": {
"visible": true,
"count": 5
}
}
Running a Merge with:
{
"count": 6,
"loading": true
}
Will result in:
{
"status": {
"visible": true,
"count": 6,
"loading": true
}
}
Only the specified properties are updated — the rest are left untouched.
Usage in Action Batches
As with all actions, you can use this inside an Execute Action Batch and control when it should run using Evaluations, delays, and conditions.