diff --git a/docs/components/connectors/protocol/rest.md b/docs/components/connectors/protocol/rest.md
index 4a2b159f3b..404961ffc9 100644
--- a/docs/components/connectors/protocol/rest.md
+++ b/docs/components/connectors/protocol/rest.md
@@ -207,6 +207,44 @@ Additionally, you can choose to unpack the content of your `response` into multi
 }
 ```
 
+## Error handling
+
+If an error occurs, the Connector throws an error and includes the error response in the `error` variable in Operate. Click on the REST Connector in Operate to see this variable.
+
+The following example shows the `error` variable in an error response:
+
+```json
+{
+  "code": "400",
+  "variables": {
+    "response": {
+      "headers": {
+        "Content-Length": "70",
+        "Date": "Thu, 17 Oct 2024 09:31:51 GMT",
+        "Content-Type": "application/json"
+      },
+      "body": {
+        "temperature": 36,
+        "message": "My custom error message",
+        "booleanField": true
+      }
+    }
+  },
+  "message": "Bad Request",
+  "type": "io.camunda.connector.api.error.ConnectorException"
+}
+```
+
+You can handle this error using an Error Boundary Event and the following error expression:
+
+```json
+if matches(error.code, "400") and error.variables.response.body.temp = 36
+then bpmnError("Too hot", error.variables.response.body.message, error.variables.response.body)
+else null
+```
+
+In this example, passing `error.variables.response.body` as the third argument to the `bpmnError` function allows you to pass additional information about the error to the error boundary event. For example, the `message`, `temperature` and `booleanField` fields from the error response are passed to the error boundary event.
+
 ## OData support
 
 The **REST Connector** supports JSON-based [OData protocol](https://www.odata.org/).
diff --git a/versioned_docs/version-8.6/components/connectors/protocol/rest.md b/versioned_docs/version-8.6/components/connectors/protocol/rest.md
index 4a2b159f3b..404961ffc9 100644
--- a/versioned_docs/version-8.6/components/connectors/protocol/rest.md
+++ b/versioned_docs/version-8.6/components/connectors/protocol/rest.md
@@ -207,6 +207,44 @@ Additionally, you can choose to unpack the content of your `response` into multi
 }
 ```
 
+## Error handling
+
+If an error occurs, the Connector throws an error and includes the error response in the `error` variable in Operate. Click on the REST Connector in Operate to see this variable.
+
+The following example shows the `error` variable in an error response:
+
+```json
+{
+  "code": "400",
+  "variables": {
+    "response": {
+      "headers": {
+        "Content-Length": "70",
+        "Date": "Thu, 17 Oct 2024 09:31:51 GMT",
+        "Content-Type": "application/json"
+      },
+      "body": {
+        "temperature": 36,
+        "message": "My custom error message",
+        "booleanField": true
+      }
+    }
+  },
+  "message": "Bad Request",
+  "type": "io.camunda.connector.api.error.ConnectorException"
+}
+```
+
+You can handle this error using an Error Boundary Event and the following error expression:
+
+```json
+if matches(error.code, "400") and error.variables.response.body.temp = 36
+then bpmnError("Too hot", error.variables.response.body.message, error.variables.response.body)
+else null
+```
+
+In this example, passing `error.variables.response.body` as the third argument to the `bpmnError` function allows you to pass additional information about the error to the error boundary event. For example, the `message`, `temperature` and `booleanField` fields from the error response are passed to the error boundary event.
+
 ## OData support
 
 The **REST Connector** supports JSON-based [OData protocol](https://www.odata.org/).