In this article, we will cover a couple of steps to troubleshoot WP Zapier not creating user’s in WordPress when receiving data from Zapier.

Some Reasons It May Not Be Working

Here are the most common issue’s we’ve come across when data isn’t being inserted into WordPress from Zapier.

Your Site Redirects To A Login Page

Some sites will redirect all non logged-in requests to the login page. This will cause issues when receiving data from Zapier to your WordPress site. You are able to change the webhook URL for receiving data to be that of your login URL instead of the default suggested URL from WP Zapier.

Your Query Parameters Are Incorrect Or Missing

Missing or incorrect query parameters will cause issues with receiving data. Very specific data is required to receive data in WordPress via the WP Zapier integration. Be sure to double-check your values that are being passed through are correct and/or available.

You may confirm the required data by visiting WP Zapier and select Receive Data. In this settings page, you will be able to view your relevant trigger and the required/supported data you may pass through. We are working on making this even easier.

Testing This Directly Via Your Website’s URL/Browser

A great way to test your site for receiving data is to paste the Receive Data URL directly into your browser. The receiving data works with query parameters or query strings.

Tip: You use an ampersand (and symbol – &) to join your query parameters to your URL. The very first query parameter will have a question mark (?) and then ampersand symbols are to follow.

Testing this in your browser will execute the code every time the page loads. This is why WP Zapier has a secret key (API Key) that can be regenerated to ensure that this service isn’t abused on your site.

Here is an example of testing the insert user into WordPress as per this guide. We need to pass the following data for testing:

  • wpz_webhook
  • api_key
  • action
  • username
  • email
  • user_pass (optional)
  • first_name (optional)
  • last_name (optional)
  • role (optional)

While there are optional values for this trigger, for the sake of this example we will pass through all of these values. Your URL may look something like this (please change the fake URL here and replace it with the relevant information for testing purposes):

https://changethis.url/?wpz_webhook=1&api_key=xxx&action=update_user&username=andrew&email=andrew@fakemail.zz&user_pass=1234&first_name=Andrew&last_name=Lima&role=subscriber

As you can see the first query parameter wpz_webhook starts with a question mark (?) and thereafter each query parameter has an ampersand (&).

Entering this into your browser will run on every page load, given that your API Key is valid and the data doesn’t already exist. If the user is added or updated correctly on page load, this means that your WP Zapier is working.

Another great tool to use is Postman to test these, but this is outside of our documentation scope for this issue but it may help do more advanced simulations.