You might have entered
http://example.com/ but you should try
This error means that something was not configured correctly when Magento was installed. The easiest fix is to edit
/lib/Zend/XmlRpc/Server.php in your Magento folder by commenting out a particular line of code.
This could be caused by a number of things! The basic gist of it is: "We couldn't make sense of the response from your server."
One common issue is URL rewriting. If your Apache or Nginx instance is a bit overzealous it could be just trying to send you back to the homepage or even serving up a 404 or 200 HTTP response full of HTML we don't understand.
On occasion your server running Magento will be misconfigured and return various error messages or log message. These errors can poison the XML payload to Zapier leading to errors. One quick fix is to add
error_reporting(0); to your index.php or the file
/lib/Zend/XmlRpc/Server.php found within your public HTML folder.
In order to ensure that we only trigger on new items that have complete information, your zap will make sure that a new item shows up with the same info in consecutive checks for new data. This can result in zaps triggering on new items more slowly.
Sometimes Magento has a hard time resetting after you make large changes, so we recommend flushing your cache. Just go to the proper Cache Management screen in the System menu:
And click "Flush Magento Cache" in the top right:
Zapier utilizes the XML-RPC v1 API of Magento. This configuration is available within all versions of Magento, including Enterprise, Go, and Community.
To check if your site is setup correctly for XML-RPC v1, visit
http://your-website.com/api/xmlrpc/ (replacing your-website with your actual domain). If you get back XML data that looks like the following, then you should be ready to connect to Zapier.