> For the complete documentation index, see [llms.txt](https://docs.incari.com/incari-studio/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.incari.com/incari-studio/2023.1/toolbox/communication/http/httpresponse.md).

# HTTP Response

## Overview

![The HTTP Response Node.](/files/VQKv67lKMVcxueAY06fJ)

The **HTTP Response Node** allows the user to define a response to be sent after a request is received and processed.

[**Scope**](https://github.com/cgi-studio-gmbh/incari-doc/blob/2023.1/toolbox/communication/overview.md#scopes): **Project**, **Scene**.

## Attributes

![The HTTP Response Node Attributes.](/files/XJJHAqBKiPpbGEjNMTCX)

| Attribute                | Type             | Description                                                                                                                                                                                   |
| ------------------------ | ---------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `Configuration`          | **Drop-down**    | The desired *HTTP(S)* server, which refers back to the selections made under *HTTP* in the [**Project Settings**](/incari-studio/2023.1/modules/project-settings/http.md).                    |
| `Header`                 | **Add elements** | Here a status code is entered and *HTTP* headers, in the form of key/value pairs, are added.                                                                                                  |
| `Is Request Body Binary` | **Bool**         | The user chooses true or false depending on whether they wish for the `Request Body` to remain a **String** or be converted into *binary*. Currently, the **Node** only supports **Strings**. |
| `Default Body`           | **User Input**   | The body of the response, usually including *HTML* text.                                                                                                                                      |

## Inputs

| Input             | Type           | Description                                                                                                                                                                                                                                         |
| ----------------- | -------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| *Pulse Input* (►) | **Pulse**      | A standard **Input Pulse**, to trigger the execution of the **Node**.                                                                                                                                                                               |
| `Request ID`      | **CustomID**   | The unique ID of the request, which is required so that the **Node** knows which client to send the response to. This ID can be obtained from the [**On HTTP Route Node**](/incari-studio/2023.1/toolbox/communication/http/events/onhttproute.md). |
| `StatusCode`      | **Int**        | A standard status code within the *HTTP* protocol. For example, 404 is when a page is not found.                                                                                                                                                    |
| `Headers`         | **Dictionary** | *HTTP* headers in the form of key/value pairs.                                                                                                                                                                                                      |
| `Body`            | **String**     | The body of the response, usually including *HTML* text.                                                                                                                                                                                            |

## Outputs

| Output             | Type      | Description                                                                                                                            |
| ------------------ | --------- | -------------------------------------------------------------------------------------------------------------------------------------- |
| *Pulse Output* (►) | **Pulse** | A standard **Output Pulse**, to move onto the next **Node** along the **Logic Branch**, once this **Node** has finished its execution. |

## External Links

* [*HTTP Responses*](https://www.toolsqa.com/client-server/http-response/)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.incari.com/incari-studio/2023.1/toolbox/communication/http/httpresponse.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.