Webhook URL endpoint using field value

Question

Alright, so I have run into an issue using a text field with a URL in the URL endpoint of a webhook.

For 1, the webhook requires an https:// at the beginning, which is fine, I understand that, but what if the field's text has that there?
For 2, the text in the field is URL encoded before it is placed into the URL, which causes some major havoc and breakage when the URL is called.
So my question:
How can I stop this? =D

I don't want to share my specific URL with anyone for privacy reasons, but it is feasible to test this with any URL as a text field in the table, then simply pass that field's value to the URL in the webhook.
Let me know your thoughts!

Thank you!
Also, if it's Mark who responds to this, a double thank you to that man, and a Merry Christmas.

------------------------------
- Sterling Long!
------------------------------

MarkShnierYou · Answer

I'm really operating in guessing as I don't claim to be an expert on webhooks and you have not been able to post even a disguised version of your code.

If the field you are using already has https:// in it and also you feel that when Quick Base sees a URL field it treats it differently than a plain old text field by URLEncoding and also adding another https://, then my suggestion is to create a text field with the URL you want. Then Quick Base will not second guess what you want in trying to be helpful.

That can be done via a formula text field.

If(Begins([my url field],"https://"), NotLeft([my url field],8),[my url field])

------------------------------
Mark Shnier (YQC)
Quick Base Solution Provider
Your Quick Base Coach
http://QuickBaseCoach.com
mark.shnier@gmail.com
------------------------------

Sign up

Login to the community