The Auth key has to be sent as follows: Send the API key using the x-make-apikey HTTP header.
There is no Custom Action option. It looks like the best I can do is to clone one of my existing actions and try to modify it? But I don’t see in Enviroment Variables where I can set Auth Keys, not specifically, anyway.
Can someone offer a noob friendly walkthrough?
And, How soon can the default custom Make.com action be updated to handle this?
Ah, there is a category Create New in the Actions List, not especially intuitive.
The Builder still refers to a lightning bolt in the UI.
Hi @kenlyle ,
Thank you for reaching out. I understand the confusion, so I wanted to clarify how this works. The Custom Webhook module in Make.com does not require an API key or any authentication header to receive data from a Pickaxe. The API key option shown in Make’s documentation is completely optional
and only applies if you choose to enable extra security on your webhook. It is not required to receive data from Pickaxe.
To verify this, I tested it myself. I created a Make.com scenario with a Custom Webhook, copied the webhook URL, added it to my Pickaxe, and triggered the action. Make received the webhook correctly without any authentication header/api keys.
We appreciate the feedback about the “Create New” custom action option not being easy to find in the updated actions library layout. I will share this feedback with the team.
1 Like
Ok, but it’s still not working and has cost me hours.
Here is what GPT5 says:
I can’t set raw body or headers with the current Basic Make Webhook action—it only sends a single field named data. Your webhook is rejecting that.
Two options:
-
Update the Make webhook/module to parse a data field that contains the JSON string.
-
Provide a tool/endpoint that accepts raw JSON so I can send the payload as-is.
Here’s the exact JSON you want sent: { “keywords”: [ “premium home hydroponic system”, “high yield indoor hydroponic garden”, “best hydroponic system ROI”, “long-term cost efficient hydroponics”, “energy-efficient indoor hydroponics”, “advanced engineered hydroponic system”, “professional grade home hydroponics”, “sustainable home hydroponic garden”, “silent operation hydroponic system”, “high productivity countertop hydroponics” ] }
It seems like some kind of non-standard webhook that doesn’t accept JSON.
The same array from Postman worked perfectly, and parsed into a clean array of the 10 keywords.
I usually trust the helpful human who actually tested it over the model that just talks confidently. 
2 Likes
The exact same array works perfectly outside of Pickaxe.
There appears to be some undocumented requirement about the variable name?
Hey
I’m experiencing the exact same issue.
Pickaxe is not sending the JSON correctly, while Postman works perfectly.
This seems like an undocumented requirement or bug.
Please provide a clear fix or update the documentation this is causing real delays for users.
Hi @kenlyle ,
Based on my testing, the issue is likely coming from your prompting or configuration. I set up a Pickaxe that generates a JSON object based on the user’s topic and connected it to the “Basic Make Webhook” action. The webhook in Make received the data correctly on my side.
Clear and precise instructional prompts are essential here since the model’s output becomes the exact payload sent to Make, so small differences in phrasing or structure can change what the webhook receives.
Is the requirement that the array be named data documented anywhere?