When building or editing a WhatsApp Flow, you might run into an error like this:
INVALID_PROPERTY_TYPE
Expected property (errorPath) to be of type (expectedType), but found (actualType).
This is a static validation error, meaning WhatsApp checks the structure of your JSON before even running the flow. Let's break it down and fix it.
What This Error Means
The error shows up when a valid property is present—but its value is in the wrong format or type.
You’re not missing the property itself, but the value isn’t what the system expects.
Example of the Problem
Here’s a common example that causes this error:
{
"type": "TextArea",
"label": "Your input",
"enabled": "yes"
}
Let’s look at what’s wrong:
"enabled" is a valid property, but its value should be a boolean (true or false), not a string.
"enabled": "yes" → invalid type (string instead of boolean)
The Fix
To fix it, just use the correct data type:
{
"type": "TextArea",
"label": "Your input",
"enabled": true
}
Now, "enabled" is set to a boolean value, which is exactly what the Flow engine expects.
Common Property Type Expectations in WhatsApp Flows
Here's a quick reference of properties and their expected types:
Property | Expected Type | Example Values |
enabled | boolean | true, false |
label | string | "Enter name" |
max-chars | number / string | 100 or "${data.max_chars}" |
options | array | [{"label": "Yes", "value": "yes"}] |
type | string | "TextInput", "Button", "TextArea" |
For more troubleshooting insights related to WhatsApp Business API, check out heltar.com/blogs.