The main purpose of this example is to show the properties and capabilities of the HTTP Reply component. In this example, there are no multiple choices to select from triggers and actions. Just receive a WebHook and give a Reply.

For the WebHook part we will be sending a JSON of the following simple form:

  "first" : "John",
  "last" : "Doe",
  "phone" : "1234567890",
  "email" : ""

Next, we can map some of the incoming fields into the responseBody part of the request-reply like this:

There are two fields by default to consider here for this simple example:

  1. Response Body (required) - the place you input your reply message. Some or all of the incoming fields from WebHook can be mapped here to make a simple message like in the example or something more elaborate depending on your use case.
  2. Content Type - which by default would be considered as application/json type. In general application/* and text/* types are supported. Please note that audio/mp4 is NOT supported and will be rejected by the system.

It is important to remember: Before you start the integration flow from the dashboard, please set this flow to be a Realtime flow. Failing to do so you will get an error 504 Gateway Time-out. To switch to the realtime follow the instructions on the picture:

Let us just run it by sending a payload in the same format as the one the WebHook expects in this example (changing the name for obvious reasons). Immediately we get this response:

  "confirmation": "Just added Olver Twist to your records"