The Request block

The Request block is a special block that can only be added to actions. The Request block takes request data sent to a deployed action's URL and routes the data through its Headers, Params, and Body output ports. Every new action automatically includes one Request block. The Request block can't be added or deleted.

Prior to an action being deployed, the Request block takes the values for headers, parameters, and the request body that you store in scenarios. By running different scenarios, you can test how your action will behave once it's deployed. Testing with scenarios is necessary because the action won't have a URL until you deploy it.

Outputs

Headers - Sends the request headers to the deployed action's URL.
Params - Sends the request's query parameters to the deployed action's URL.
Body - Sends the request body to the deployed action's URL. Actions support JSON and form-urlencoded formats. For example, a form-urlencoded request body with category=books&id=101&id=102&id=103 would return the following:
```
{
  "category": ["books"],
  "id": ["101", "102", "103"]
}
```

Setup

For an action that's not deployed yet, create at least one scenario with values for the headers, parameters, and the request body that you want the action to handle. The Request block will send those values from its corresponding output ports to whatever blocks you connect. Once the action is deployed, the Request block will obtain those values from HTTP requests sent to the action's URL.

Example

Here's an example that shows how incoming request body content (in this case, the message "Testing my action URL") can be processed within the action and then sent to the Body input port of the Response block. To make it clear that the message was present in the request body, the example shows the Request block's output selected.