Text Formatter not getting the filed text

[Vyasa Kandasamy]

Your Task History ID

IjU3NjUwNTY4MDYzNjA0MzA1MjZlNTUzNzUxM2E1MTY1NTQzMDBmMzEi_pc

The Text Formatter step in my workflow stopped working on June 20th after a client's payment failed. I had integrated another platform to send a WhatsApp payment reminder, but the workflow failed, showing the error message I've attached below. Can someone assist me on this

 

[Preeti Paryani]

Hello @Vyasa Kandasamy,

Could you please try deleting the Text Formatter action from your workflow and then re-adding it? Once done, test the workflow and let us know if the issue is resolved.

If the problem still persists, kindly share the Task History ID with us so we can review it in detail and assist you further.

Looking forward to your response.

 

[Vyasa Kandasamy]

Hello @Preeti Paryani,

I have tried deleting the Text Formatter action from my workflow and re added it , but it still the same after testing.

Whatsapp message is not being send out to my client

Here's my Task history ID - IjU3NjUwNTY4MDYzNjA0MzE1MjY0NTUzNTUxMzM1MTYzNTQzOTBmMzIi_pc

Please do review it and let me know if there's any issue

Looking forward for your assistance

 

[Preeti Paryani]

Hello @Vyasa Kandasamy,

We have escalated this concern to our technical team for review. Please allow us some time, and we will get back to you with the update as we have some.

 

[Vyasa Kandasamy]

Hello @Vyasa Kandasamy,

We have escalated this concern to our technical team for review. Please allow us some time, and we will get back to you with the update as we have some.

Hello @Preeti Paryani ,

Thank you for your prompt response

Looking forward for an update from your technical team.

 

[Preeti Paryani]

Hello @Vyasa Kandasamy,

Our team is currently investigating the issue. In the meantime, could you please share your exact use case and how you're utilizing the "Text Formatter: Replace Text" action in your workflow? This will help us determine if there's a possible workaround we can suggest while the issue is being resolved.

Looking forward to your response.

 

[Vyasa Kandasamy]

Dear @Preeti Paryani,

I have attached the use case and the workflow im using in pabbly aswell on how im utilizing the Text Formatter:Replace Text in my workflow.

Thank you for your prompt response

Looking forward for an update from you.

 

[Preeti Paryani]

Hello @Vyasa Kandasamy,

Thank you for your response and for sharing the screenshots.

However, the attached screenshots don’t clearly explain your use case or the purpose of using the Text Formatter – Replace Text step. From what we observe, you're attempting to replace a specific key with the exact same key, which wouldn’t have any impact on the data being passed forward.

We’d appreciate it if you could clarify the reason behind adding this step. If the intention is simply to pass the value forward, directly mapping the original content might achieve the same outcome without this additional step.

Looking forward to your clarification so we can assist you better.

 

[Vyasa Kandasamy]

Hello @Preeti Paryani,

Thank you for your response and for reviewing the screenshots.

The reason we included the Text Formatter – Replace Text step, even though it appears redundant, was to maintain formatting consistency across different outputs and ensure uniform handling of the data before passing it forward. This step acts as a safeguard in our setup to avoid any potential formatting issues that may occur when integrating with downstream apps like WhatsApp APIs, which can sometimes be sensitive to data structure or hidden characters.

That said, if there’s a more optimized or recommended approach to achieve this while keeping the formatting intact, we’d really appreciate your suggestions. We’re open to improving the workflow based on your guidance.

Looking forward to your insights and thank you again for your assistance.

 

[Preeti Paryani]

Hello @Vyasa Kandasamy,

Thanks for sharing the details and the reasoning behind your setup.

However, based on our understanding, that particular Text Formatter – Replace Text step doesn’t seem necessary. If you directly map the required key (e.g., Sale Client Fullname) into the content where it’s needed, the action should still work exactly the same.

We recommend trying this by removing the formatter step and mapping the key directly. Since the current action is simply replacing a mapped key with content that already includes the same mapped key, the added step doesn’t offer additional value.

Please give it a try and let us know if it works as expected

 

[Vyasa Kandasamy]

Hi @Preeti Paryani ,


Thanks for the clarification and the suggestion to remove the Text Formatter – Replace Text step.


Initially, we believed the formatter might be unnecessary too. However, during testing, we ran into an issue where the data coming from the source (specifically the Sale Client Phone Number field) was shown along with a label like this:

1. Sale Client Phone Number : 60197505355

When we tried mapping this directly into the WhatsApp API step, it didn’t work , the phone number wasn’t extracted properly, and we received a “Phone number is required” error.


We then attempted to use Text Formatter – Text Split, but it didn’t return any usable output. Likely, this was because the mapped value was not raw text but just a display label. After that, we tried Text Formatter – Replace Text to remove the label and isolate just the number (60197505355).

Even then, the issue persisted , either the Replace Text step didn't receive proper input, or it failed to output usable text for mapping. So the problem still remains unresolved.

We believe the root issue may be due to how the original field is structured or formatted when passed to Pabbly , it seems like a labeled object, not a pure string value.

We’re currently exploring options to pass in a clean phone number directly from the source system (e.g., through webhook restructuring), but if you have any alternative solutions or best practices to extract raw values from these fields, we’d really appreciate your guidance.

Thanks again for your support.

 

[Preeti Paryani]

Hello @Vyasa Kandasamy,

Thank you for the detailed explanation and context regarding the issue—much appreciated.

Based on what you've shared, the action step where you're mapping the phone number should ideally work as expected. However, the “Phone number is required” error may sometimes occur due to a temporary loading issue while fetching field data.

We recommend clicking into the phone number field and allowing it a minute to fully load the available dynamic fields before mapping. In case the issue persists, try refreshing your browser and then remap the field. This usually helps resolve any temporary interruptions in field loading and should allow the phone number to be recognized correctly.

Please give this a try and let us know how it goes.

Thanks again for your continued efforts in troubleshooting this.