Skip to main content
Best answer

Censored URL

  • April 21, 2025
  • 3 replies
  • 53 views

When sending a URL to a Sub-Zap, part of the URL is replaced with “censored”

Should be:  https//secure.notarycam.com/meeting/

Censored to: https://secure.”censored:9:cf9357e22c:.com/meeting/

 

 Is there a way to stop this from happening?

This post has been edited by a moderator to remove personal information. Please remember that this is a public forum and to remove any sensitive information prior to posting.

Best answer by SamB

Hi there, ​@NotaryCam Admin 👋

Ah, I expect the URL is being automatically censored for security reasons. I’d suggest contacting our Support team to submit a new feature request for the ability to set certain URLs or values to not be censored when using Sub-Zaps. You can do that here: https://zapier.com/app/get-help.

In the meantime, is it just the domain that’s being censored from the URL and nothing unique to the meeting like it’s ID etc? Just wondering if you can use a Formatter (Text > Split Text) action to help grab the latter part of the URL and reconstruct the full URL in the actions(s) that need to use it. Could that approach work for your needs here?

Looking forward to hearing from you!

This post has been closed for comments. Please create a new post if you need help or have a question about this topic.

3 replies

SamB
Community Manager
Forum|alt.badge.img+11
  • Community Manager
  • 9751 replies
  • Answer
  • April 22, 2025

Hi there, ​@NotaryCam Admin 👋

Ah, I expect the URL is being automatically censored for security reasons. I’d suggest contacting our Support team to submit a new feature request for the ability to set certain URLs or values to not be censored when using Sub-Zaps. You can do that here: https://zapier.com/app/get-help.

In the meantime, is it just the domain that’s being censored from the URL and nothing unique to the meeting like it’s ID etc? Just wondering if you can use a Formatter (Text > Split Text) action to help grab the latter part of the URL and reconstruct the full URL in the actions(s) that need to use it. Could that approach work for your needs here?

Looking forward to hearing from you!


  • Author
  • Beginner
  • 7 replies
  • April 22, 2025

SamB - thank you.  I will submit the new feature request as you suggest.  I also did already make a small adjustment to bypass the sub-zap handoff and hardcoded the first half of the URL.  Yes, only the domain is being censored so I was able to use the work around.  Thanks for your help!

 


SamB
Community Manager
Forum|alt.badge.img+11
  • Community Manager
  • 9751 replies
  • April 23, 2025

You’re very welcome, ​@NotaryCam Admin! 😊 Glad to hear you’re going to submit a feature request and that you were able to use the workaround.

Seems like you’re all set for the minute but please do reach back out if you need help with anything else at all. 🙂