> For the complete documentation index, see [llms.txt](https://imbrace.gitbook.io/imbrace-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://imbrace.gitbook.io/imbrace-documentation/workflows/respond-to-webhook.md).

# Respond to Webhook

Use the Respond to Webhook connector to control the response to incoming webhooks. This connector works with the Webhook connector.

### How to use Respond to Webhook <a href="#how-to-use-respond-to-webhook" id="how-to-use-respond-to-webhook"></a>

To use the Respond to Webhook connector:

1. Add a [Webhook ](https://imbrace.gitbook.io/imbrace-no-code-workflow/workflow/webhook)connector as the trigger connector for the workflow.
2. In the Webhook connector, set **Respond** to **Using 'Respond to Webhook'** connector.
3. Add the Respond to Webhook connectoranywhere in your workflow. If you want it to return data from other connectors, place it after those connector.

### Connector parameters <a href="#node-parameters" id="node-parameters"></a>

Configure the connector behavior using these parameters.

#### Respond With <a href="#respond-with" id="respond-with"></a>

Choose what data to send in the webhook response.

* **Binary**: respond with a binary file defined in **Response Data Source**.
* **First Incoming Item**: respond with the first incoming item's JSON.
* **JSON**: respond with a JSON object defined in **Response Body**.
* **No Data**: no response payload.
* **Text**: respond with text set in **Response Body**.

### Connector Options <a href="#node-options" id="node-options"></a>

Select **Add Option** to view and set the options.

* **Response Code**: set the [response code](https://developer.mozilla.org/en-US/docs/Web/HTTP/Status) to use.
* **Response Headers**: define response headers to send.

### Workflow behavior <a href="#workflow-behavior" id="workflow-behavior"></a>

When using the Respond to Webhook connector, workflows behave as follows:

* The workflow finishes without executing the Respond to Webhook connector: it returns a standard message with a 200 status.
* The workflow errors before the first Respond to Webhook connector executes: the workflow returns an error message with a 500 status.
* A second Respond to Webhook connector executes after the first one: the workflow ignores it.
* A Respond to Webhook connector executes but there was no webhook: the workflow ignores the Respond to Webhook connector.