How to setup HTTP POST

David Bullock — 

The Infusionsoft HTTP POST is a powerful tool in your Infusionsoft Membership site automation toolkit.  HTTP POSTs are a simple API that can be used between web servers to allow them to signal each other that something has happened, or than an action has been taken. In the case of Memberium the most common HTTP POST used is the function to create a password for a Memberium user.

Memberium HTTP POSTs can be used to do several things:

HTTP POSTs can be sent from Infusionsoft to Memberium three different ways (listed in order of preference):

  • Campaign Builder
  • Legacy Actionset
  • Manually

We’ll cover all these below:


The best overall guideline is to not mix the different methods, or if necessary to minimize it. In other words, it’s best not to use Legacy Actionsets in Campaign Builder, since the native Campaign Builder HTTP POST is available. Similarly, if you’re using actionsets in your workflows, it’s best to use an Actionset to execute your HTTP POST, and not manually paste the HTTP POST URL in every time.

Campaign Builder

Campaign Builder is great for generic workflows. It can be a little slow in processing but is very flexible and easy to manage through the visual drag-and-drop interface.

Campaign Builder is a bad choice when one-time large amounts of bulk operations on contacts all at once, such as creating thousands of passwords at once using a makepass HTTP POST.

When creating an HTTP POST in Campaign Builder, you should not use any POST parameters other than the contactId. All other parameters must be placed in the URL.


If you need actions to happen in “realtime”, then Campaign Builder is sometimes not the best solution. An example of this would be a legacy order form or action where the password generation and tagging must happen immediately before the customer moves to the next page load. In this case Legacy Actionsets still appear to have the edge.

Legacy Actionset

Legacy Actionsets enable you to package up one (or more) actions and execute them as a package. Legacy Actionsets are best used with legacy marketing web forms, legacy order forms, and when applying actions to searches. Legacy Actionsets CAN be used with Campaign Builder, but legacy support in Campaign Builder periodically suffers from bugs and we no longer consider that a reliable setup. The beauty of these, is that you can create simple or complex actions and test them in a controlled, limited environment with a few users, and then reliably apply them in a workflow or a larger group. Actionsets are great for actions that “MUST BE DONE NOW” such as after a legacy order form to ensure the client is tagged and processed before the next page loads.


You can also apply action sets to search or report results, or to a contact directly by opening the contact screen. We would encourage you to apply these HTTP POSTs using Legacy Actionsets for consistency and reliability.

Working with Security Plugins

Memberium cannot provide direct support for 3rd party plugins, however the following troubleshooting information has been provided by our members.

Unblocking HTTP POST in Wordfence

In WordFence, you will need to whitelist Infusionsoft’s IP address range, which is 208.76.24.[0-255].

Unblocking HTTP POST in BulletProof Security

BulletProof security requires a number of entries in the .htaccess files.

You will need to add a skip rule to ignore all rules based on the following condition:

You will need to add Infusionsoft to the list of domains allowed to talk to the server:

You will need to whitelist the domain as well:

Thanks to Justin Frydman for updated WordFence configuration information.

Troubleshooting a failed HTTP POST

If you are applying an HTTP POST and it doesn’t work you may have one of the following issues:

  • You are using an HTTPS:// URL and Infusionsoft cannot verify your SSL certificate.
  • You have a redirect setup to send to
  • The website is using a CDN that is blocking the HTTP POST. Example: CloudFlare
  • You are running a caching plugin that is responding to the HTTP POST, and not letting it get through to Memberium. Example: W3 Total Cache, Super Cache, etc.
  • You are running a security plugin that is blocking the HTTP POST. Examples: WordFence, BulletProof Security, Securi.
  • Your web host is running a filter or firewall setting that is blocking the HTTP POST. Examples: WP Engine