ERROR: Message not sent. Parameter of type text is missing text value

When sending a template message, are you getting this error: Message not sent. Parameter of type text is missing text value?

Let’s understand why this error occurs and how you can fix it.

Why do you get this error?

This error usually shows up when you're using a message template that includes variables like {{1}}, {{2}}, {{3}}, and so on, and you send it either through a Notification or from your Inbox with a missing value for these variables.

For example, if your message template says: " Hi {{1}} , your order {{2}} has been confirmed!” and when sending, the value for {{2}} is missing, the message will fail to send.

Now this can happen due to a few reasons:

1. A mapped contact attribute doesn’t have a value

For instance, if you have mapped a variable {{1}} to a contact attribute called “city” or “order_date,” but that attribute has no value for the given contact; any attempt to send a message using that empty value will fail.

2. Data is not being passed correctly from your integration

This issue can also occur with Transactional notifications, where the variable data being sent from your website, form, or CRM (using our WordPress Plugin or REST API) is incomplete or missing. If any of the variables expected by the template are empty, the message will fail to send

How to fix this error

The most effective way to fix this error is to prevent it altogether. There are two ways to do that:

1. Check the data being sent from your source

If you’re sending a Marketing Notification to your contact list, start by reviewing the contact data that you are mapping with the variables, and make sure data is present for all variables. 

In case of your integrations that trigger Transactional Notifications, like your lead capture form, or CRM (connected through our WordPress Plugin or REST API), make sure that all the values expected by the template are actually being passed in the request. 

If even one variable is missing or left empty, the message will fail.

2. Add fallback values for variables

If you do not have full control over the data source, or if some fields may occasionally be blank, you can define fallback values for each variable in the Notifications page.

or example, if you are using a variable {{1}} for the ‘city’ attribute in the following template:

“Hi! We’re excited to bring our services to {{1}}”

… and if a contact does not have this value, the fallback could be set to “your city.”

The final message would then appear as:

Hi! We’re excited to bring our services to your city.

By following the steps above, you can prevent this error and ensure that your messages are delivered successfully.

Updated on: 26/06/2025