# WhatsApp API Error  INVALID_ENUM_VALUE in WhatsApp Flows
Author: Prashant Jangid
Author URL: https://www.heltar.com/blogs/author/prashant-jangid
Published: 2025-03-31
Category: Troubleshoot
Category URL: https://www.heltar.com/blogs/category/troubleshoot
Tags: WhatsApp Flows Error
Tag URLs: WhatsApp Flows Error (https://www.heltar.com/blogs/tag/whatsapp-flows-error)
URL: https://www.heltar.com/blogs/whatsapp-api-error-invalidenumvalue-in-whatsapp-flows-cm8wwciiy0003yis233ccyo69

While building a WhatsApp Flow, you might run into this error:

**INVALID\_ENUM\_VALUE**

**Value should be one of: \[data\_exchange, navigate\].**

This is a static validation error, and it usually means that you've used a valid property—but with a value that’s not allowed. In simple terms: You used the right key, but gave it the wrong value.

Let’s break it down and fix it with a real example.

Example of the Problem

Here’s a snippet that causes the INVALID\_ENUM\_VALUE error:

```
{
  "screens": [
    {
      "id": "FIRST_SCREEN",
      "layout": {
        "children": [
          {
            "type": "EmbeddedLink",
            "text": "link",
            "on-click-action": {
              "name": "complete",
              "payload": {}
            }
          }
        ]
      }
    }
  ]
}
```

So what’s wrong?

The on-click-action.name is set to "complete"—but for an EmbeddedLink, that’s not one of the allowed values.

## The Fix

According to the WhatsApp Flow schema, EmbeddedLink supports only specific values for on-click-action.name, like:

\[data\_exchange, navigate\]

So, to fix the error, update the name value to one of the allowed options:

```
{
  "screens": [
    {
      "id": "FIRST_SCREEN",
      "layout": {
        "children": [
          {
            "type": "EmbeddedLink",
            "text": "link",
            "on-click-action": {
              "name": "navigate",
              "payload": {
                "screen_id": "SECOND_SCREEN"
              }
            }
          }
        ]
      }
    }
  ]
}
```

Now it’s valid! We’re using an allowed value (navigate) for this component type.

## Why This Happens

Different components in WhatsApp Flows have different rules for what actions they can trigger. For example:

- Button might support actions like data\_exchange or complete.

- Footer can trigger complete.

- EmbeddedLink supports only navigate or data\_exchange.


If you assign an unsupported action to a component, you’ll get this INVALID\_ENUM\_VALUE error.

## Quick Reference: Allowed Values (Examples)

Component

Allowed on-click-action.name values

Button

data\_exchange, navigate, complete

Footer

complete only

EmbeddedLink

navigate, data\_exchange

Always check the documentation or component-specific schema when in doubt.

_**Tip:**_ Try using the official Flow Builder UI for a few screens before editing JSON directly. It helps you understand which components accept which values—without having to memorize the entire schema.

For more troubleshooting insights related to WhatsApp Business API, check out [heltar.com/blogs](http://heltar.com/blogs).


---
This blog is powered by Superblog. Visit https://superblog.ai to know more.
---