Currently, in custom actions within the Intercom workflow, if an attribute contains a null or missing value, it causes the custom action to fail.
I’d like to request the addition of a fallback value option for custom actions similar to how there are failback options for outbound messaging. This would allow us to set default or empty values (e.g., an empty string or "Null") for missing or null attributes, ensuring that the custom action can continue running smoothly even if some attributes are missing.
Proposed Solution:
-
Allow custom actions to be configured with fallback values for missing or null attributes, similar to how fallback messaging works with outbound messaging.
-
For example, if the “Partner” attribute is missing, we could set a fallback value like an empty string or "Null" to prevent errors and keep the custom action running.