G’day all,
I’ve just started getting a 200 error in my scenario, when previously it worked fine.
The scenario is RSS Feed → HTTP (Get A File) → WordPress (Create a Media Item) → WordPress (Create a Post).
The error occurs at WordPress (Create a Media Item), where it’s supposed to upload an image (and has done previously, without issue).
Error Report is as follows:
Rules Might change, it is possible you will not be allowed to use script tag inside create a post also check if you need to put everything into section tag
Welcome to the Make community!
Based on the error message, it appears that there is a security plugin preventing programmatic access to the API, or an anti-bot service like Cloudflare that hosts your DNS settings which detects internet traffic coming from Make as “suspicious”.
Try disabling the plugins, or bypassing security settings to see if it works.
Hope this helps! If you are still having trouble, please provide more details.
— @samliew
The issue turned out not to be Make or the WordPress module, but WordPress security / captcha protection.
A plugin/WAF started returning a reCAPTCHA “Bot Verification” page for the REST API endpoint wp-json/wp/v2/media, so Make was getting an HTML page with a 200 status instead of the expected JSON response, which caused the runtime error.
To fix it I:
Located the security/captcha plugin/WAF that was enforcing the check.
Disabled captcha/bot protection for the WordPress REST API paths (/wp-json/*, especially /wp-json/wp/v2/media), and/or allowed Make’s IP addresses.
After excluding those endpoints, the Create a Media Item module started working again and images upload correctly.
Does that explain my 404 error? My webhost turned off reCAPTCHA (I honestly couldn’t see any captcha plugin in my Wordpress) and now the 404 error doesn’t make sense to me.
Thanks for disabling the reCAPTCHA — that solved the first issue, but the new 404 error is different. The HTML in the error shows that LiteSpeed is returning a server-level 404 page, which means the request to /wp-json/wp/v2/media is being blocked before it even reaches WordPress. This usually happens when the REST API is restricted by the server, .htaccess rules, LiteSpeed security settings, or a firewall that is preventing external POST uploads. The Make module is calling the correct endpoint, but the server is not allowing it through. Can you please whitelist /wp-json/*, ensure POST requests and file uploads to /wp-json/wp/v2/media are allowed, and confirm that no LiteSpeed or firewall rules are blocking the WordPress REST API? Once the API endpoint is reachable in a browser without returning LiteSpeed’s 404 page, the Make scenario will work again.
That error message is not very helpful in telling us which module in your scenario is causing the issue, only that it couldn’t reach your server.
To allow others to assist you with your scenario, please provide the following:
We need to see what you’re working with to give you the best advice. Screenshots are extremely important because Make is a visual editor — a picture provides us with more context.
It would help us identify the issue by having screenshots of:
You can upload images here using the Upload icon in the text editor:
We would appreciate it if you could upload screenshots here instead of linking to them outside of the forum. This allows us to zoom in on the image when clicked, and avoid tracking cookies from third-party websites.
Please export the scenario blueprint. Providing your scenario blueprint file will allow others to quickly recreate and see how you have set up the mappings in each module, and also allows us take screenshots or provide module exports of any solutions we have for you in return - this would greatly benefit you in implementing our suggestions as you can simply paste module exports back into your scenario editor!
To export your scenario blueprint, click the three dots at the bottom of the editor then choose ‘Export Blueprint’.
You can upload the file here by clicking on this button:
Please provide the output bundles of each of the relevant modules by running the scenario (you can also get this without re-running your scenario from the History tab).
Click on the white speech bubbles on the top-right of each module and select “Download input/output bundles”.
Save each bundle contents in a plain text editor (without formatting) as a bundle.txt file.
You can upload the file here by clicking on this button:
If you are unable to upload files on this forum, alternatively you can paste the formatted bundles.
Here are some ways to provide text content in a way that it won’t be modified by the forum.
Method 1: Type code fence manually —
Add three backticks ``` in a separate line before and after the content, like this,
```
text goes here
```
Method 2: Highlight and click the “preformatted text” button in the editor —
Method 3: Upload your file and share the public link —
(this method is only recommended for large files exceeding the forum upload limit)
Providing the input/output bundles will allow others to replicate what is going on in the scenario, especially if there are complex data structures (nested arrays and collections) or if external services are involved, and help you with mapping the raw property names from collections.
Sharing these details will make it easier for others to assist you.
Here’s as many pics of the scenario in detail that I can give you - very simple with just four modules.
The RSS and HTTP parts of your scenario are fine. The error comes from your WordPress connection: the server is returning a LiteSpeed 404 HTML page instead of the REST API JSON. That means the URL Make is calling for /wp-json/wp/v2/media (and /wp-json/wp/v2/posts) doesn’t exist or is being blocked. Double-check that your WordPress connection points to the exact URL where WP is installed (including any subdirectory), and try opening https://YOURDOMAIN/wp-json/wp/v2/media in a browser. If that also shows a 404 HTML page, you’ll need your host to fix/whitelist the REST API path /wp-json/* so Make can reach it.
Fixed!
I had to create a new API.
What had happened was there had been a slight movement of my website’s hosting pages (originally being a wp/wp-json during set-up). The rogue extra ‘wp’ had been left in the make.com connection. Once removed, it sorted outself out.
I should have checked there first - my fault everyone!
Seriously though, thanks for all your help.
