Post your new WordPress Posts to your Facebook page
WordPress + Facebook Pages
The first thing you'll need to do when setting up Zapier with WordPress is give us the information to access your WordPress account. For example, that means your:
While not required, we highly recommend using SSL with your blog to ensure the safety of your WordPress login credentials. You can find more information about using SSL and SSL certificates with your WordPress site on our Advanced Tips help page.
Also, while optional, we really recommend creating a brand new user, just for Zapier, with a strong password generated from a service like random.org. We'll show you how to do that now!
This is a simple process, just a few steps are involved. First you'll need to log into your WordPress admin and click to add a new User:
zapier as the username, use any email you like (maybe your own email address, don't use Zapier's email addresses) and generate a secure password.
For role, you can choose Admin if you want Zapier to be able to do anything to your blog. We generally recommend Editor, but you can read more about WordPress User Roles if you like!
Click Add New User and that's it for this section!
Now that you have a user account for Zapier to use, we can connect your account! One thing you'll need to get right is your Base URL, but it is quite simple. Let's say your admin account is located here:
Then you'd want to use the same URL before
/wp-admin/ as your Base URL, and place your username password. That would look something something like this:
Please note, the
/wordpress/section of the URL is not really required, that just happens to be where it is installed. Your's might be
After clicking continue, you should see a section that looks something like this:
Congrats, your account is now connected to Zapier! If you need to set up HookPress for instant updates, read on, otherwise that's all you need!
This is very common and usually involves a bad plugin! If you just installed a plugin, you should try disabling and try again. If that doesn't help, just contact support and ask us to check our logs, we'll do our best to identify the troubled plugin for you!
This can happen if the authenticated user does not have an appropriate role. Please review WordPress' details on Roles and Capabilities as you will need an authenticated user who at least has an Editor role to post as other authors.
In order to connect to WordPress, you must have XML-RPC functionality turned on. This is turned on by default in WordPress 3.5+. If you're having issues connecting, go to Settings > Writing > Remote Publishing and check the checkbox.
You may also receive this error if your WordPress installation is secured and not publicly available. Unfortunately, the installation must be publicly accessible to work with Zapier.
Also, we're unable to provide IPs to whitelist as our IPs are not static - they rotate because we use AWS. If you'd like, you should be able to whitelist a block of IPs from AWS to make this work. You would just need to make sure the list you're whitelisting is the us-east-1 IP range.
Additionally, Zapier's calls will always include the header
User-Agent: Zapier, so this may be an alternative when whitelisting a whole range of IPs isn't feasible.
Jetpack Protect (official WordPress module) will occasionally block some AWS IPs -- you can either whitelist the IP listed in the error, disable Protect altogether, or if try and whitelist all AWS us-east-1 IPs. You can read more about how to use those IPs here.
Once you do that, try reconnecting your WordPress account to see if this resolves the issue.
If you have a firewall enabled please double-check that it allows Zapier to connect as well.
This error could mean that you're using the wrong Base URL in the login screen. If you're using
http: try using
https:. If you're using
www.example.com try using it
If you continue to get this error, then it's likely because the XML-RPC is being blocked on the WordPress site. It's most likely being blocked by a plugin, the hosting provider, or a security setting. To fix, try disabling a your plugins one and a time, then try reconnecting to WordPress account to see if you can isolate the problem plugin.
If not, it might be a back-end change that needs to be made by your hosting provider or website developer. We recommend reaching out to them and asking them to update the XML-RPC settings for you. You can send them this link for more information: https://codex.wordpress.org/XML-RPC_Support
If your provider/developer wants to whitelist access to us, you can let them know that we use Amazon's AWS products for our server infrastructure, so they'll need to whitelist their IP list from the us-east-1 region. You can find that range list here: https://ip-ranges.amazonaws.com/ip-ranges.json . You can read more about how to use those IPs here.
In order to take an image from a previous step (like your Trigger, for example) and add it as a featured image on your post, you have to use 2 WordPress steps.
First, you use the 'Upload Media' step to add the image to your WordPress website:
Then, on your 'Create Post' step you make use of the image you just uploaded, by selecting "Use a Custom Value" for the 'Featured Media' field and then using the "Attachment ID":
WordPress + Facebook Pages
WordPress + Twitter
Facebook Pages + WordPress
Instagram + WordPress
WordPress + LinkedIn
WordPress + Twitter
Right now, the Zapier WordPress app doesn't support custom fields within posts, however, you should be able to get them to show up by using the Wordpress plugin, here. After installing the plugin, try creating a new post with custom fields and they should come across for you. Thanks to our awesome user Dave for this tip!
Note: This is a potential workaround suggested by a user of ours and therefore, we cannot help with troubleshooting in regards to the plugin. If you installed the plugin after creating the Zap, try creating a brand new Zap if you're having trouble getting them to appear.
Get started with a Free account