#2231-bot won't send the custom field value to users

David 4 weeks ago

I have an HTTP API that successfully populates a custom field called "aqi_result" (I can see the value in Live Chat admin interface).

After the HTTP API element, I added a Text element with #aqi_result# but the bot won't send this to users. It shows nothing at all.

How do I correctly display a custom field value populated by HTTP API in a message to the user?

Please respond ASAP.

Dear User,

It should work as expected. To help us investigate further, please open a support ticket on our help desk with your login credentials and specify which HTTP API is not working. This will allow us to check if everything has been set up correctly.

Alternatively, you can also reach out to us via WhatsApp for quicker assistance.

Thank you for your cooperation.

Best regards,

Kamrul Hasan

Hi Team,

I’m facing a very similar issue, but in my case it’s happening while using the Botsailor API (not HTTP API) to assign values to custom fields.

Here are my observations:

• Custom field value not reflecting correctly

After assigning a value via API, in the Live Chat it appears that the value is set, but in reality, it is not being used correctly in bot messages.

• Duplicate field creation (case-sensitive issue)

After deeper investigation, I found that instead of updating the existing custom field, the system is actually creating a new custom field with a slight variation in the name:

• Original field: state
• Newly created field: State
• Hidden field (not visible in dashboard)

The newly created field (State) is not visible anywhere in the Botsailor dashboard UI, which makes debugging very difficult.

• Confirmed via API response

When fetching subscriber details using the API, I can clearly see both fields exist simultaneously:

• state
• State

This indicates that the system is treating custom field names as case-sensitive, and instead of updating the existing field, it silently creates a new one.

• Are custom field names intended to be case-sensitive?
• If yes, why does the system allow creation of duplicate fields with only case differences without showing them in the dashboard?
• If not, this seems like a bug in field matching/assignment logic.
• Also, how can we prevent auto-creation of unintended fields via API?

Dear User,

Thank you for reporting the issue on the forum. We apologize for the delayed response.

To better understand and resolve the matter, we kindly request you to contact us via WhatsApp for live support, or record a video of the issue and share it through the support desk.

Our live support is available from 10 AM to 7 PM (GMT +6) Sunday to Thursday.

Thank you.