> For the complete documentation index, see [llms.txt](https://developers.make.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developers.make.com/custom-apps-documentation/app-components/modules/responder.md).

# Responder

The responder should be used when you need to send processed data back to the service. The scenario is initiated by an instant trigger, processes the data received, and then sends the results back to the sender. The responder module has no interface; you just pass parameters in.

<div align="left"><img src="/files/mYInpZyqOU4nftJMLq2S" alt="" width="563"></div>

## Components

### Communication

Only a `response` directive is available inside the [communication](/custom-apps-documentation/component-blocks/api.md). Unlike with most modules, where `response` handles the data that comes from the API, in this case `response` defines what the webhook (instant trigger) should send back to the external platform that called it.

### Static Parameters

You can use [static parameters](/custom-apps-documentation/component-blocks/parameters.md) inside the responder module without any restrictions.

### Mappable Parameters

You can use [mappable parameters](/custom-apps-documentation/component-blocks/mappable-parameters.md) inside the responder module without any restrictions.

## Responder example

{% tabs %}
{% tab title="Appearance" %}

<div align="left"><img src="/files/4ZDzSDRWmptigIt7ogVo" alt="" width="563"></div>
{% endtab %}

{% tab title="Communication" %}

```json
{
	"response": {
		"body": {
			"text": "{{parameters.text}}"
		},
		"status": 200,
		"headers": {
			"content-type": "application/json"
		}
	}
}
```

{% endtab %}

{% tab title="Static Parameters" %}

```json
[]
```

{% endtab %}

{% tab title="Mappable Parameters" %}

```json
[
	{
		"name": "text",
		"type": "text",
		"label": "Message"
	}
]
```

{% endtab %}
{% endtabs %}


---

# 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://developers.make.com/custom-apps-documentation/app-components/modules/responder.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.