Hi all,
I’m trying to use a Make webhook to receive structured JSON from an assistant integrated with OpenAI (ChatGPT). The assistant is configured with the correct webhook URL, and it’s sending POST requests with the correct Content-Type: application/json header and a simple payload like:
{
“title”: “post title goes here”,
“post”: “post content goes here”
}
The webhook URL in Make is:
https://hook.eu2.make.com/yivtgq91xrphn0xuzsjkhcr34ttzideq
I have:
- Initialized the webhook successfully using Postman (so the data structure is set)
- Confirmed the webhook is in listening mode
- Mapped the fields in downstream Trello modules using
title and post
- Verified that the payload works perfectly when sent from Postman (200 OK)
However, every time the assistant sends the same payload, Make returns: Access denied
This happens even though the payload and URL are exactly the same as the working Postman request. So the only variable is the origin of the request (OpenAI vs. Postman).
Key Question
Is Make blocking webhook requests based on the origin IP / environment (e.g. OpenAI’s servers)? Or is there some other security rule preventing these external requests from being accepted?
If so, is there a workaround — like allowing anonymous requests explicitly or using a Make API key?
Any insights would be hugely appreciated — we’ve spent hours debugging and everything on the schema and payload side seems spot-on.
Thanks in advance!
Welcome to the Make community!
This is unlikely, unless you had added a IP whitelist when creating the Webhook.
Can you Edit your Webhook connection and show us how you’ve set up the Webhook?
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.
Hiya,
thanks for your help!
I’ve attached a screenshot of the webhook. It’s very simple, basically just as it is when you create it in Make.
Is that wrong?
Here’s some more info too 
Hmm, those are the default settings. You will have to contact support for further investigation on the server-side.
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.
Great, have logged a support ticket. thanks so much for your help!!
