---
title: "Examples for HTTP Request Job"
slug: "using-http-request-job-in-the-whiteboard"
updated: 2024-04-26T16:01:05Z
published: 2024-04-26T16:01:05Z
canonical: "docs.mapp.com/using-http-request-job-in-the-whiteboard"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.mapp.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Examples for HTTP Request Job

This article covers the steps to build a marketing automation using the HTTP Request job in the Whiteboard.

> This feature can be best used by tech-savvy users as it involves basic HTTP request principles.

The procedure is very similar to creating any other Whiteboard. The Job-specific settings that you define include: request parameters, and parser specifics to handle the HTTP Response.

### Define the HTTP Request

1. Create a new Whiteboard.

> **HTTP Request** is available with every type of Whiteboard: event-based, scheduled and recurring. **HTTP Response** is available as follows:
> 
> - **Event-based**: available
> - **Scheduled**: available with event zone
> - **Recurring**: not available - limited to HTTP Requests only
2. Select the entry Event (for example, *Enters Group*) and add the job **Send HTTP Request**. ![](https://cdn.document360.io/554b9b98-6720-4d8b-9919-c7b203d72648/Images/Documentation/b11f2ffa-7a21-4e63-b7c0-fdcc383cd1fc.png)
3. Define the method: **Get**, **Post**, **Put**, **Patch** and **Delete**. ![](https://cdn.document360.io/554b9b98-6720-4d8b-9919-c7b203d72648/Images/Documentation/2f30d3af-f33d-4f59-b213-efef8ef816bd.png)
4. Optionally, check the box *Continue the whiteboard flow if the request fails*. ![](https://cdn.document360.io/554b9b98-6720-4d8b-9919-c7b203d72648/Images/Documentation/7f4905ef-4163-485b-8a01-9739d9917070.png)
5. Select the **Content Type** for your request. Available Content Types are: **application/json**, **application/xml** and **application/x-www-form-urlencoded**. It will be used as your request header. You can add additional headers using the button **Add Header**. ![](https://cdn.document360.io/554b9b98-6720-4d8b-9919-c7b203d72648/Images/Documentation/912f4b7b-4209-45b9-987b-2d73155b5c78.png)
6. Click **Add Parameter**. Give the parameter a name and configure its value. ![](https://cdn.document360.io/554b9b98-6720-4d8b-9919-c7b203d72648/Images/Documentation/68c79c40-7790-41c3-96d9-b65c9b8fe5f5.png)

> [!TIP]
> You can add up to 10 parameters in your automation.
7. Configure the response body parser. This allows you to use the parameter values received from the server.
  1. In section HTTP Response Body Parser, select the parser type and click **Add Parser**. ![](https://cdn.document360.io/554b9b98-6720-4d8b-9919-c7b203d72648/Images/Documentation/f31004fb-4a0b-4927-a235-9d48fd18ee90.png) The Body Parser covers industry standard formats XML and JSON. Using a custom regex-like parser is also possible.

| Parser Type | Details |
| --- | --- |
| XML | You can find more information on the web, for example [here](https://www.w3schools.com/xml/xml_xpath.asp). |
| JSON | You can find more information on the web, for example [here](https://goessner.net/articles/JsonPath/index.html#e2). |
| Plain text | This option is for your custom parser, using [Mapp Engage Functions](/v1/docs/mapp-engage-functions). |
| None | Select this option if you are not interested in any parameters. |

> [!TIP]
> It is possible to use previously parsed HTTP parameters in the body of the next HTTP Request.
> 
> To do this, use one of these formulas inside the request body:
> 
> `<%${parameter.XXX}%>`
> 
> or
> 
> `<%${parameter['XXX']}%>`
> 
> **XXX** is the name of the parameter parsed in the previous **Send HTTP Request** job.
> 
> **The HTTP Request must directly follow the request where the parameters were parsed.**
  2. Enter the parsing formula, parameter name and type. Click **Save Parser**. ![](https://cdn.document360.io/554b9b98-6720-4d8b-9919-c7b203d72648/Images/Documentation/4daaa28a-65a1-4646-85c6-f4186e611b0c.png)
  3. Add more parsers if needed.

### Configure response criteria matching

You have set up everything for your HTTP request. The event HTTP Response Received is now available. You can define criteria matching based on the HTTP response codes (value or range) and/or the parameters.

> As a standard use case, set it up within a multiple event configuration. However, you can also set it up as a single event and use it as a filter.

1. Add the event HTTP Response Received to your automation workflow.

![](https://cdn.document360.io/554b9b98-6720-4d8b-9919-c7b203d72648/Images/Documentation/12b5ee98-01c4-49bc-9c57-b85c2d2911dc.png)
2. Define criteria matching based on either the HTTP response codes, or the parameters, or on both.

Click **Apply**.
  1. based on the HTTP response codes: ![](https://cdn.document360.io/554b9b98-6720-4d8b-9919-c7b203d72648/Images/Documentation/6c36b5fd-1543-462f-804e-9ee008568f2c.png)
  2. based on your parameters:

![](https://cdn.document360.io/554b9b98-6720-4d8b-9919-c7b203d72648/Images/Documentation/85d85051-88ab-4317-ab4c-0bc335972274.png)
  3. Optionally, add Negative Path and configure it too.

### Use HTTP Response values

The parsed HTTP Response values are available as event values for the next Whiteboard job. For more details on building Whiteboard automations, see [Whiteboards](/v1/docs/whiteboards).

![](https://cdn.document360.io/554b9b98-6720-4d8b-9919-c7b203d72648/Images/Documentation/22296419-f0b1-4dea-9a35-27542f221947.png)

## Use Cases and How-tos

[Personalize Messages Based On Weather In Your Contact's Location](/v1/docs/personalize-messages-based-on-weather-in-your-contacts-location)

[Personalize Messages With Images Retrieved From Unsplash](/v1/docs/personalize-messages-with-images-retrieved-from-unsplash)

[Post A Message To Slack](/v1/docs/post-a-message-to-slack)

## Further Information

[Create an Event-Based Whiteboard Plan](/v1/docs/create-an-event-based-whiteboard)