Skip to main content
Best answer

Handling MySQL emoji issues with Zapier's utf8 connection

  • February 13, 2025
  • 3 replies
  • 17 views

Hi!

I have a problem which is not related to my MySQL setup, because it working with Cloud sql Studio.

When trying Insert or Update Text column with text ‘🚨 Urgent - Skip Revision’ Zapier generates error:

“1366, "Incorrect string value: '\\xF0\\x9F\\x9A\\xA8 U...' for column 'urgency' at row 1")".”

I think that it is related to fact that Zapier is using utf8 (3-byte) instead of utf8mb4 connection.

Do you know how to handle that without workaround?

 

 

Best answer by SamBBest answer by SamB

Hi ​and welcome to the Community, ​@wrogman! 👋

I can see that you also reached out to the Support team, and they’ve added you to an existing feature request for utf8mb4 to be supported. It looks like you’ll need to wait for that feature to be implemented for those errors to be resolved. I can’t make any promises on when it may be sorted by, but we’ll definitely send you an email notification once it is.

Really sorry I don’t have a more immediate fix to share. If I come across any potential workarounds or updates, I’ll be sure to share them here. Thanks for your patience in the meantime! 🙏

View original
Did this topic help you find an answer to your question?
This post has been closed for comments. Please create a new post if you need help or have a question about this topic.

3 replies

  • Author
  • Beginner
  • 2 replies
  • February 13, 2025

@SamB are you able to help here?


  • Author
  • Beginner
  • 2 replies
  • February 13, 2025

As a remark, I set skip_character_set_client_handshake = ON flag on my Cloud MySQL server and still doesn’t work with Zapier.


SamB
Community Manager
Forum|alt.badge.img+11
  • Community Manager
  • 7796 replies
  • Answer
  • February 14, 2025

Hi ​and welcome to the Community, ​@wrogman! 👋

I can see that you also reached out to the Support team, and they’ve added you to an existing feature request for utf8mb4 to be supported. It looks like you’ll need to wait for that feature to be implemented for those errors to be resolved. I can’t make any promises on when it may be sorted by, but we’ll definitely send you an email notification once it is.

Really sorry I don’t have a more immediate fix to share. If I come across any potential workarounds or updates, I’ll be sure to share them here. Thanks for your patience in the meantime! 🙏