> For the complete documentation index, see [llms.txt](https://docs.appmixer.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.appmixer.com/connector-configuration/utils/http/response.md).

# Response

### Overview

The **HTTP Response Component** is used to return an HTTP response to a webhook. It allows setting a response body, status code, and headers, enabling proper interaction with external services that expect a structured HTTP response.

### Usage

#### Input Parameters

| Parameter    | Type                | Description                                      |
| ------------ | ------------------- | ------------------------------------------------ |
| `body`       | `string` / `object` | Data to be sent as the response body.            |
| `statusCode` | `number`            | The status code of the response.                 |
| `headers`    | `string` / `object` | The headers object associated with the response. |

### Instructions

1. **Set Response Body**
   * Provide a valid JSON or string value as the response body.
2. **Define Status Code**
   * Choose an appropriate HTTP status code (e.g., `200` for success, `400` for client errors, `500` for server errors).
3. **Specify Headers**
   * Ensure proper content types (e.g., `Content-Type: application/json`) when sending structured data.
4. **Ensure Valid JSON (If Required)**
   * If `Content-Type` is `application/json`, the body should be a valid JSON object.

### Notes

* **Handles JSON Parsing**: Automatically parses headers and body if they are provided as JSON strings.
* **Error Handling:**
  * If headers cannot be parsed, an error will be logged and the response will be canceled.
  * If `Content-Type` is `application/json`, but the body is invalid JSON, an error is thrown.


---

# 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:

```
GET https://docs.appmixer.com/connector-configuration/utils/http/response.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.