Skip to main content

Get Support
Have a question? Let's get you an answer!

How Do I...? Troubleshooting Code & Webhooks Developer Zone

Other Help Resources
Wait, there's more! Check out these Community sourced spaces for additional resources.

Zapier Help Center Hire an Expert

Learning Resources
All of our best learning resources can be found here.

Featured Articles Show & Tell Zapier's products AI Hub Zapier Tools Hub

Share your knowledge
Give back to the Community by sharing your automation wins and helping to answer questions.

Share your success See unanswered questions User Groups

Other Learning Resources
Some of our favorite additional ways to upskill your Zapier knowledge.

Zapier Learn Zapier Blog Zapier Webinars

Product Updates
Check out what is new and upcoming with Zapier with our regular product updates.

Product Updates

Early Access Program
Want to join Early Access? Learn more here.

Best answer

Parentheses (round brackets) in webhook data are corrupting request data

  • December 23, 2021
  • 6 replies
  • 315 views
AgentFire

Hello, recently we spotted this bug - when using parentheses (round brackets) in webhook data fields - they’re are corrupting request data:


Request preview shows it normally:
 


But the actual data sent to the server is corrupted:
 

 

Server responds with json_encode( $_POST ) no other processing is made.

It gets worse with array form keys:

 

Preview also looks fine:


But the whole value string is replaced with substring from parentheses:

 

And with JSON payload type:


Request looks completely weird:


We know we can escape all brackets manually via code step (similar to this issue), but since preview shows data correctly and only the actual request is corrupted we believe it might be some bug in webhook module.

After some testing we found it’s yyy(zzz) pattern that causes issues. It’s not breaking stuff if we add space yyy (zzz) or if we remove one bracket.

Thanks!

Best answer by SamBBest answer by SamB

Hey all! I just wanted to follow up here as spotted that our Support team added @AgentFire to a bug report for this issue.

I can’t make any promises as to when this will be sorted by but we’ll be sure to email and will post an update here as soon as it is.

View original
Did this topic help you find an answer to your question?
This post has been closed for comments. Please create a new post if you need help or have a question about this topic.

6 replies

Troy Tessalone
Forum|alt.badge.img+14
  • Troy TessaloneZapier Expert
  • Zapier Expert
  • 31254 replies
  • December 23, 2021

Hi @AgentFire 

Check out this article for context on how Zapier handles “Named Variables”:

 

⚡ Troy Tessalone - AutomationAce.com | Premier Certified Zapier Expert | #1 Zapier Community Contributor
AgentFire
1 person likes this
  • AgentFire
    AgentFire
AgentFire
  • AgentFireBeginner
  • Author
  • Beginner
  • 2 replies
  • December 23, 2021
Troy Tessalone wrote:

Hi @AgentFire 

Check out this article for context on how Zapier handles “Named Variables”:

https://community.zapier.com/featured-articles-65/create-your-own-fields-with-named-variables-9138

 

Good to know, thanks! So apparently this feature breaks webhook data. And if you look closely at screenshots, you’ll see it’s not just extracting named variables, but creating a complete mess in data, destroying data fields, or with JSON payload - it moves whole data inside results object, which was not even there initially :scream:.
At first it was triggered by this word: Day(s) (and may be triggered by any other user input).
So it looks reasonable to name it a bug - even if I would like to put named variables there - it will destroy data fields anyway.. or need to at least optionally disable Named Variables feature, just like Unflatten feature:

btw Day(s) is not even matching the camelCase pattern for methods/variables :relaxed:

Troy Tessalone
Forum|alt.badge.img+14
  • Troy TessaloneZapier Expert
  • Zapier Expert
  • 31254 replies
  • December 23, 2021

@AgentFire 

Probably best to open a ticket with Zapier Support for further assistance with this: https://zapier.com/app/get-help

⚡ Troy Tessalone - AutomationAce.com | Premier Certified Zapier Expert | #1 Zapier Community Contributor
AgentFire
1 person likes this
  • AgentFire
    AgentFire
AgentFire
  • AgentFireBeginner
  • Author
  • Beginner
  • 2 replies
  • December 23, 2021
Troy Tessalone wrote:

@AgentFire

Probably best to open a ticket with Zapier Support for further assistance with this: https://zapier.com/app/get-help

Will do that, thanks! Will also post link to this thread, if you don’t mind (don’t delete it pls for now :smiley: ).

christina.d
Forum|alt.badge.img+9
  • christina.dZapier Staff
  • Zapier Staff
  • 2653 replies
  • December 23, 2021

Interesting, thanks so much for reaching out, @AgentFire! I can see you opened up a ticket with our support team which is perfect! Thanks so much for your patience while the team digs into this for you. 🙂

SamB
Community Manager
Forum|alt.badge.img+11
  • SamBCommunity Manager
  • Community Manager
  • 7672 replies
  • Answer
  • February 23, 2022

Hey all! I just wanted to follow up here as spotted that our Support team added @AgentFire to a bug report for this issue.

I can’t make any promises as to when this will be sorted by but we’ll be sure to email and will post an update here as soon as it is.

AgentFire
1 person likes this
  • AgentFire
    AgentFire
Terms & Conditions