Message encoding format is invalid

Your Workflow URL
https://connect.pabbly.com/workflow/mapping/IjU3NjYwNTY4MDYzMzA0M2Q1MjZlNTUzMjUxM2Ei_pc
Your Task History ID
IjU3NjUwNTY1MDYzMjA0MzI1MjZhNTUzMzUxMzM1MTY2NTQzOTBmMzgi_pc
Consent to Access & Modify
I authorize Pabbly Support to log in to my account and make changes to the specified workflow for troubleshooting.
hello, I just wanna ask why I keep receiving this error message "Message encoding format is invalid" can you please check on it?
 

Attachments

  • Screenshot 2026-01-05 201625.png
    Screenshot 2026-01-05 201625.png
    18 KB · Views: 7

Hrishabh.pabbly

Member
Staff member
Hello @Clicknamics ,

Thank you for sharing the workflow details and granting consent to access your account.

We’ve checked the workflow and the API request sent to iTexMo. The error “Message encoding format is invalid” is occurring due to unsupported characters in the Message field.

The iTexMo SMS API only supports plain GSM / ASCII text. Your message contains special (Unicode) characters, for example:
  • Smart apostrophe: Here’s
  • Special punctuation or formatting from copied text
  • Certain symbols in long URLs
These characters cause the API to reject the message with an encoding error.
Please update the Message field by:
  1. Removing smart quotes and special characters
    • Change Here’s → Here is
  2. Use only plain English letters, numbers, and basic punctuation
  3. Avoid emojis or special symbols
  4. (Optional) Shorten or remove the URL temporarily to test

Once the message is converted to plain text, the workflow should execute successfully without the encoding error.

Please try this and let us know if you need further assistance—we’ll be happy to help.
 

Preeti Paryani

Well-known member
Staff member
Hello @Clicknamics,

Upon checking the latest task history, the error indicates that the phone number is invalid. Please try performing the request with a valid number as per the Itexmo application’s requirements, and let us know how it goes.

1767702240630.png


1767702230977.png


If the issue persists, feel free to share the updated task history for further review.
 
Top