Automation from Make.com on Ghost Search Member is challanged by WAF

Hey, I am using Make.com to perform certain automations for our members, we are now ready to proceed with our automation but when I tried with a few test records received from Ghost Webhook I noticed we receive a challenge from WAF / Cloudflare and we are not actually receiving data. Sometimes it works without any issues. When we did our tests before we never received such challenges. We have not made a lot of calls to the API so we get a rate limitation of some sort.

Sounds like a question for your host.

Hey Cathy thanks, what do you mean by host? I am sorry for the random question dough. But we are using Make.com ( for automations ) and Ghost Pro for our newsletter? Our Module in Make.com was working correctly when we did our tests before and now we get a challenge from time to time. Do you mean we should check with Make.com why the API call is flagged as suspicious potentially?

Is the problem on the Make side, or the Ghost side? Well, actually, i guess I can guess, if you’re on Ghost Pro, since they use Fastly, not Cloudflare – so you might ask Make for assistance. Or… if you put Cloudflare in front of Ghost pro, you may need to adjust your own settings. :slight_smile:

The community forum war. Make community says ask Ghost, Ghost community says ask Make :joy: Thank you for your help anyway.

Sorry! That’s the worst, isn’t it?

But seriously, AFAIK, Ghost Pro doesn’t have Cloudflare in their stack anywhere. That would seem to point fingers elsewhere…

Edit: Er… see below?

1 Like

Hey @Alexandar_Borisov - It looks like an unrelated rule we added for blocking some spam traffic unintentionally caused this. We’ve now adjusted, so things should be working again. Please let us know if that isn’t the case though!

2 Likes

@Alexandar_Borisov seems to be using Cloudflare as well? I wonder if they’re proxying all requests? If so, would it be advisable they disable Cloudflare Proxy as it appears Ghost Pro already uses Fastly?