This article covers how to configure and use the Send HTTP Post object in the Keap™ automation builder, including how to set up the post URL, configure Name and Value field pairs, use merge fields to pass contact data, and test the HTTP Post before publishing. This article does not cover how to write server-side scripts to receive HTTP Post data. For help with script development, consult the developer documentation for the scripting language used on your web server.

Why HTTP Posts Let You Connect Keap to External Systems

An HTTP Post is used to send data from Keap to an external web page that runs a server-side script — such as a script written in PHP, ASP, or JavaScript. When the HTTP Post is triggered as part of an automation sequence, Keap sends the configured field names and values to the URL of the external script. The script then extracts the data and processes it on the web server. This makes it possible to pass Keap contact data — such as a name, email address, or custom field value — to a third-party system, a custom application, or a webhook endpoint automatically as part of an automation. HTTP Posts are commonly used to integrate Keap with external systems that do not have a native Keap integration.

Supported ports: HTTP Posts in Keap only support standard port numbers. The supported ports are 80 and 443. HTTP Post configurations that use non-standard port numbers will not function correctly.

Important limitations: Each HTTP Post object must be configured individually and cannot be reused in multiple sequences or used at more than one point in the same sequence. HTTP Post objects are not archived when deleted. If an HTTP Post object is deleted from a sequence, it can only be restored by restoring a previous version of the entire automation.

How to Configure and Use the Send HTTP Post Object in Keap

Follow these steps to add and configure a Send HTTP Post object in a sequence in the Keap automation builder.

1. Open the sequence where the HTTP Post will be added by double-clicking the sequence block on the campaign canvas, or create a new sequence.

2. Drag and drop a Send HTTP Post object from the sequence tools panel onto the sequence canvas, positioned to the right of the Start icon or after the desired preceding step.

   

   The screenshot above shows the Keap sequence canvas with a Send HTTP Post object being placed onto the canvas. The sequence tools panel on the left displays the available sequence objects. The Send HTTP Post object appears as a block on the canvas after being dropped into position.

3. Double-click the Send HTTP Post object on the canvas to open the HTTP Post configuration settings.

   

   The screenshot above shows the Send HTTP Post configuration settings panel in the Keap sequence editor. The panel displays the post URL field at the top, followed by the Name and Value pair fields where the data to be sent is configured. The Merge button, plus and minus icons, and Test button appear in the panel.

4. Enter the post URL in the URL field. The post URL is the web address of the external server-side script that will receive and process the data sent by Keap.

5. Configure the Name and Value pairs that will be sent to the post URL. Each line item in the HTTP Post sends two pieces of information — a field Name and a field Value:

   • Name — The field name label sent to the external script. The name can be defined as anything needed to match the requirements of the external script or API. If there is no requirement to match external naming standards, the default Keap field names for standard or custom fields can be used.

   • Value — The content of the field sent to the external script. The value must be defined using a Keap merge field — a placeholder that inserts the actual contact record data at the time the HTTP Post is triggered. For example, the Value for a Name field labeled "Email" would use the merge field for the contact's email address. Select Merge to browse and insert available Keap merge fields into the Value field.

6. Add or remove Name and Value pairs as needed:

   • Select the plus icon to add a new Name and Value pair line.

   • Select the minus icon to remove an existing Name and Value pair line.

   Note: Name and Value pair lines cannot be reordered after they have been added. To change the order of the lines, delete the lines that need to be repositioned and recreate them in the correct order.

7. Select the Test button to verify the HTTP Post is configured correctly and the external URL is responding. A response code of 200 confirms the post is working correctly. Other response codes indicate an issue that requires troubleshooting. For a full list of HTTP response codes and their meanings, see the list of HTTP status codes on Wikipedia. If a 409 error is returned during testing, the contact used for the test may already have a member record in the connected system — try testing with a different contact.

8. Select Back to Sequence to return to the sequence canvas after configuring and testing the HTTP Post.

9. Publish the campaign to make the HTTP Post active. The Send HTTP Post object will not send data to the post URL until the campaign has been published.

Frequently Asked Questions

What does this article cover?

This article covers how to configure and use the Send HTTP Post object in the Keap automation builder, including how to set up the post URL, configure Name and Value field pairs, use merge fields to pass contact data, and test the HTTP Post before publishing. This article does not cover how to write server-side scripts to receive HTTP Post data.

Can I reuse an HTTP Post object in multiple sequences?

No. Each HTTP Post object must be configured individually and cannot be reused across multiple sequences. An HTTP Post object also cannot be used at more than one point within the same sequence. A separate Send HTTP Post object must be added and configured for each location in the automation where an HTTP Post is needed.

What happens if I delete an HTTP Post object from a sequence?

HTTP Post objects are not archived when deleted. If a Send HTTP Post object is deleted from a sequence, it cannot be individually recovered. The only way to restore a deleted HTTP Post object is to restore a previous version of the entire automation. Review the HTTP Post configuration carefully before deleting it.

Which port numbers does Keap support for HTTP Posts?

Keap HTTP Posts only support standard port numbers — port 80 and port 443. HTTP Post configurations using non-standard port numbers are not supported and will not function correctly.

What does a 200 response code mean when testing an HTTP Post?

A 200 response code confirms the HTTP Post is configured correctly and the external URL is receiving the data successfully. Any response code other than 200 indicates an issue that requires troubleshooting. For a full list of HTTP response codes and their meanings, see the list of HTTP status codes on Wikipedia.