diff --git a/docs/components/connectors/out-of-the-box-connectors/amazon-bedrock.md b/docs/components/connectors/out-of-the-box-connectors/amazon-bedrock.md
index c1f6bda7ac3..283ccb9e302 100644
--- a/docs/components/connectors/out-of-the-box-connectors/amazon-bedrock.md
+++ b/docs/components/connectors/out-of-the-box-connectors/amazon-bedrock.md
@@ -111,14 +111,18 @@ Ensure the model is available in your region, that your model can invoke the `Co
 :::
 
 - `New Message` is either the first message (to start a conversation) or is the next message from an already started conversation.
+- `Documents` is a list of documents to include as part of your **new message**.
+  - To work with documents you must upload them first, [using the REST API](/apis-tools/camunda-api-rest/specifications/create-document.api.mdx) for example.
+  - The result of the endpoint must then be assigned to a variable in **Start Process Instance** so you can use the list of these variables in the **Documents** field.
 - `Message History` is the history of the conversation that should always be passed. If not set, this will be a new conversation.
 
 1. Use **Result Variable** to store the response in a process variable. For example, `myResultVariable`.
 2. Use **Result Expression** to map fields from the response into process variables.
 
-The response contains two elements:
+The **Response** is a list of consecutive messages of the user and the assistant.
 
-- `messageHistory` is the full history of the previous message, from user and assistant, including the latest message written by the assistant.
-- `newMessage` is the latest message written by the assistant.
+:::info important
+The current implementation supports the assistant's responses only in text format.
+:::
 
 Ideally, the message's history must transit within the process and be the input of this `Converse` task with the new message.