Emoji not send properly through Heartbeat module
Status: Closed · Asked by JJJJJJJJJJJ on · 0 views
Hi guys, new here!
I have quite some values coming from a trigger (Heartbeat) using emoji's in them.
Pabbly, unlike Zapier, shows and passes them as these types of codes: \ud83d\ude0d.
Any way to prevent this, or convert them back to emoji before pushing them on to the next step in the workflow?
Or, ideally, update the Heartbeat triggers to let them pass the emoji's instead of the codes (similar to how Zapier does it).
thanks in advance!
J
Hi
Could you please let me know the name of Workflow that you are refereeing to check with the team?
Hi Kunal,
The workflow is “new/updated HB Users > AT CRM”
Task ID with an example where it occurs: - IjU3NjYwNTZjMDYzMzA0M2Q1MjZjNTUzMDUxM2I1MTY0NTQzNSI_3D_pc
Hi,
Thanks for sharing Workflow name. We are checking it with the team. Kindly allow us a day time to replay back with an update.
Hi,Thanks for sharing Workflow name. We are checking it with the team. Kindly allow us a day time to replay back with an update.
Great!
Hi,
We have checked the data workflow and clicked on Save & Send Test Request in the third action and issue got solved. The unwanted character are not showing in the workflow. Kindly once check and let us know.

Thanks
Kunal
Hi,We have checked the data workflow and clicked on Save & Send Test Request in the third action and issue got solved. The unwanted character are not showing in the workflow. Kindly once check and let us know.
Thanks
Kunal
Hi Kinal, unfortunately this was a for someone that didn’t have a tag with an emoji in them.
The latest run was again for someone with emoji, and it still showed those as “Early Adopters \ud83d\ude0e, New Member \ud83d\ude0d” values instead of “Early Adopter ?, New Member ?”.
Hi,
Could you please pass the values without any emojis with them and let us know if still you are getting any issues with the values?
Hi,Could you please pass the values without any emojis with them and let us know if still you are getting any issues with the values?
The values that don’t contain emoji’s have always worked just fine. It’s really only when the value contains an emoji that has the emoji part getting transcoded unintentionally.