You can send an HTTP Request as part of an action sequence.
- Drag the HTTP Request icon onto the canvas and double-click to configure
- You can change the request type at the top. Then you can add your Target URL with Merge Fields ( This is the same as the HTTP POST today)
- You can add your query parameters that show up at the end of the URL.
ex: FristName with Value of the Contact FirstName that is Merged into that Value field ~Contact.FirstName~
- We also added the ability to add info in the header
- Then next we added the Body Text area
- Now, we can test the request and response
Lastly, we have the Request that is taking all the info we filled out above and creating our request. This will give us an idea of what is happening and how the request is actually getting created which is important with merge fields.
FAQs
Can I convert my existing HTTP POST processes to HTTP Requests? Yes, you can convert your existing HTTP POST to an HTTP Request. Follow the steps outlined here
What should I do if my HTTP Request is not working as expected?
If you encounter issues with your HTTP Request, consider the following troubleshooting steps:
- Check Syntax: Ensure that the syntax of your HTTP Request is correct. Any typos or errors can lead to communication problems.
- Authentication: Verify that your authentication credentials are accurate and up-to-date.
- Endpoint URL: Double-check the endpoint URL to ensure it is correct and accessible.
- Review Documentation
- Test in Isolation: Test your HTTP Request using the Test function listed in step 6 to identify whether the issue is specific to the request or part of a larger workflow.
What is the character limit for the body section of an HTTP Request?
The character limit for the body section of an HTTP Request is 65,535 characters. It's essential to stay within this limit to ensure the successful processing of your requests.
What types of issues are typically beyond the scope of customer support for HTTP Requests?
Issues related to external API endpoints, third-party service limitations, or custom code not directly related to Keap's HTTP Request feature may be beyond the scope of customer support. In such cases, you may need to consult with your development team or the respective external service's support.