Builds a JSON object from your definition and merges or replaces the incoming payload.
Builds a JSON object from your definition and merges or replaces the incoming payload.
This step executes when the flow reaches it along a wired path. It does not call external services by itself unless combined with API or CMS steps — it shapes how the flow continues.
Set JSON is a logic step in the Logic group. Logic steps control how data moves through the flow: branch on conditions, loop over lists, pause, merge parallel paths, or reshape payloads.
Typical reasons teams add Set JSON to a flow:
Common patterns on the canvas:
On Design, choose Merge or Replace, then define the JSON object. You choose every key and nested structure — use {{placeholders}} for values from earlier steps.
Output fields are whatever fields you define in the JSON output for this Set JSON node.
The designer shows these tabs for this node:
| Tab | Purpose |
|---|---|
| Info | Plain-language description and output payload fields for downstream steps |
| General | Canvas label and read-only node ID |
| AI | Optional assistant to help draft settings from plain language |
| Design | Node-specific configuration fields |
These fields are managed by the designer or runtime — you do not type into them directly:
| Property key | Label | Type | Required | Visible when | Notes |
|---|---|---|---|---|---|
_nodeId | Node ID | node-id | No | — | — |
_payloadFields | Available Fields | payload-panel | No | — | — |
| setJsonShape | JSON to set | raw-json-shape-editor | Yes | — | { "key": "" } |
| Property key | Label | Type | Required | Visible when | Notes |
|---|---|---|---|---|---|
label | Label | text | No | — | Node label |
| Property key | Label | Type | Required | Visible when | Notes |
|---|---|---|---|---|---|
mergeMode | Apply to incoming payload | select (merge | replace; default: merge) | No | — | — |
Credentials, API keys, mailers, SMTP, and integration defaults are configured in the CMS plugin under Node Configuration, not per step on this node. Link the flow to a domain before testing CMS-backed fields.
After this step runs, later nodes can reference these fields using placeholders such as {{set_json._shape_note}}.
| Field key | Type | Description |
|---|---|---|
_shape_note | note | Output fields are whatever fields you define in the JSON output for this Set JSON node. |
Other steps in the same area of the palette:
join-array-to-text) — Logicif) — Logicfilter-list) — Logicdebug) — Logicmatch-regex) — Logic