Why is $ifEmpty() returning undefined for nested data in my IF node?

Below is some guidance on troubleshooting this issue:

Verify the Data Structure

When using $ifEmpty() (or any similar fallback helper), double-check that you’re addressing the correct property in your nested data. For example, if you expect data on a nested field, make sure you’re using the correct path (e.g. using $json["user"]["id"] rather than $json["id"]) and that the node is indeed returning that structure.

Consider Using Alternative Expressions

The $ifEmpty() helper can sometimes behave unexpectedly with nested data. Instead, try using JavaScript’s built-in operators to add a fallback value. For instance, you could use a ternary operator:

JAVASCRIPTCopied
{{$json["user"] && $json["user"]["id"] ? $json["user"]["id"] : "default value"}}

Or the nullish coalescing operator:

JAVASCRIPTCopied
{{ $json.user?.id ?? "default value" }}

Both methods explicitly check if the nested property exists before returning its value, which can provide more controlled behavior compared to $ifEmpty().

Check Node Execution Order

Sometimes expressions return undefined if the referenced node hasn't executed, especially in cases where complex branching (such as with an IF node) is involved. Ensure that the node producing your nested data is executed prior to the node employing the $ifEmpty() (or alternative) check. (If a node hasn’t run yet, it won’t provide the data needed.)

Summary

• Confirm the correct data path: Ensure your nested data is accessed correctly.
• Use explicit fallbacks: Prefer direct JavaScript expressions (ternary or nullish coalescing) for handling empty values.
• Verify node execution: Double-check that the node with your expected data is executed before your condition checks.

Implementing these checks should help you avoid unexpected undefined results.