Skip to main content

I have a flow that triggers an email that contains a button with a URL that looks like this: “https://www.blabla.com/check-in?email=test@test.us”
Whenever I trigger the flow and receive the email, I click on the button and see that the ‘@’ in email param was encoded to ‘%40’, that way I can’t use it properly in my application.
Is there a solution for this? 

In URL encoding, you probably don’t want to use the @ character itself but rather refer to it as an entity. I would recommend looking into how to refer to the @ character using the encoded named entity for an ampersand, eg.

&

See this article from the W3 Org for more of an explanation:

https://www.w3.org/MarkUp/html-spec/html-spec_13.html

It’s probably worth experimenting with using the encoded named entity for this character and seeing if if will hold together through your use case.


Reply