I’ve search the subject in this forum and found some solutions like How to secure my webhook with an APIKEY - #4 by Yaenz
However I really don’t like having the API key value in clear in the scenario to do the comparison with what is received in the headers.
And maybe it’s out of date since it’s seems like its now possible to specify and API key as Authentication:
My issue right now is that the webhook still gets triggered even if I don’t specify the api key when calling it.
What am I missing?
Thanks
Welcome to the Make community!
Looks like “authentication method” field is new, looks like you’re a beta user and that feature appears to not work at the moment.
For technical issues or bugs like this, directly contacting support can often lead to a faster resolution. Make support has access to your specific account details, scenario and scenario logs, server-side logs, and internal tools and resources, which allows them to investigate more thoroughly than what you have access to. Additionally, sharing potentially sensitive information about your account, scenario variables, and output bundles might not be advisable as it is a public forum.
You can open a new ticket here, or if you are unable to login for some reason, you can create another new free Make account to access the ticketing system (which is only available to logged-in users). After submitting a new ticket, you will receive an automatic confirmation email with the subject “Ticket Created” in the subject. If you do not receive this, try sending the ticket again.
If you manage to get your issue resolved with support, we’d still love to hear about it! Sharing your solution on the forum can help others facing similar problems.
Hope this helps! Let me know if there are any further questions or issues.
— @samliew
P.S.: Investing some effort into the Make Academy will save you lots of time and frustration using Make.
