BUG: Issue with Unescaped Spaces in text formatting

[dodgenvy]

Your Task History ID

IjU3NjUwNTZiMDYzNDA0MzM1MjZiNTUzMDUxMzY1MTY0NTQzMjBmMzgi_pc

I am having an issue with the flexibility of using dynamic values and coding within the platform, primarily with the unescaping of spaces.

In my workflow, I am creating an API call that triggers our telephony software for a text message to go out. We are using data collected from two sources (Mindbody and Google Sheets) to build out the information in the text message. Typically, this setup has worked for us across other workflow applications (n8n, Salesforce), but with Pabbly, it seems that the coding containers do not escape spaces, as you can see in the screenshots.

I have added a space between these messages, but despite this effort, the spaces are not retained when the API POST call is made.

This is the same reason I believe my.ICS files are generating as empty because the unescaped spaces are creating inconsistencies in the code and .ics files are very rigid in their requirements.

- I've tried Text Formatter to remove or add spaces.
- I've tried r/n/ as well to force breaks in the sentence structure.
- I've tried simply adding a space.

That being said, has anyone had any luck with fixing these?
I found this workaround on the Pabbly forum, but I would be interested in seeing other options.

 

[dodgenvy]

Workflow ID: https://connect.pabbly.com/v2/app/workflow/mapping/IjU3NjYwNTY1MDYzNjA0MzM1MjZmNTUzYzUxMzIi_pc

 

[Preeti Paryani]

Hello @dodgenvy,

Thanks for sharing the details. Upon checking your workflow, we noticed the space was not being added between the mapped key and the location. We have added the space, saved the step, and confirmed it stays in place. Please try triggering the workflow again and monitor if the location appears correctly now. It’s possible the earlier issue was due to a cache-related glitch. Do let us know the results after testing.