Dear all,
I discovered that all my scenarios in Make.com stopped right after the webhook, since the location of the password in the header array has changed (I have the password checked with Make’s built-in filter, and the filter now looks in the wrong location).
Have you experienced the same issue?
Maybe it has to do with recent changes of webhooks (may apply to legacy plans only).
best
Gregory
Do you have screenshots of a run before the change, and what it looks like now?
I mean the authorization. Maybe password is not the best word.
Before, the authorization was located in the 6th collection. Now it’s the 11th (at least for me). I need to hardcode the location of the authorization in the filter, which follows the webhook to only process authorized calls.
If this change concerned everyone, it would be nice to receive an announcement in the future.
I agree, there should have been an announcement if there’s a change.
However, in the meanwhile, I think you can use a get - map combination in Make to not have to hardcode the index anymore. That’s much more effective.
Thanks for the keyword @ThinhDinh
I found it in Make‘s docs: https://www.make.com/en/help/mapping/mapping-arrays#mapping-an-array-s-element-with-a-given-key
Yeah, it’s like a built-in lookup function. Pretty neat.
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.
