Actions50
- Collection Actions
- Document Actions
- Search Actions
- Analytics Actions
- API Key Actions
- Alias Actions
- Synonym Actions
- Override Actions
- Conversation Actions
Conversation → Update
AI-generatedOverview
This node updates a conversation model in a language learning model (LLM) service. It allows users to modify the configuration of an existing conversation model by specifying the model ID and providing new configuration details either as raw JSON or through structured input fields. This is useful for managing and customizing conversation models in applications that use LLMs for chatbots, virtual assistants, or other conversational AI systems.
Use Case Examples
- Updating a conversation model's system prompt to improve response quality.
- Changing the TTL (time-to-live) for messages in a conversation to control data retention.
- Providing a complete new model configuration as JSON to redefine the conversation behavior.
Properties
| Name | Meaning |
|---|---|
| Model ID | ID of the conversation model to update, required to identify which model to modify. |
| JSON Input | Flag to indicate whether the model configuration is provided as raw JSON or through structured fields. |
| Model Configuration (JSON) | The full model configuration in JSON format, used if JSON Input is true. |
| Additional Options | Collection of optional fields to configure the model, used if JSON Input is false. Includes explicit model ID, API key, account ID, system prompt, TTL for message deletion, and vLLM service URL. |
Output
JSON
id- The ID of the updated conversation model.modelConfiguration- The updated configuration details of the conversation model.status- Status of the update operation, e.g., success or failure.
Dependencies
- Requires an API key credential for the LLM service to authenticate requests.
Troubleshooting
- Ensure the Model ID is correctly specified; missing or incorrect IDs will cause update failures.
- If using JSON input, verify the JSON syntax and structure to avoid parsing errors.
- Check that the API key and account ID (if required) are valid and have sufficient permissions.
- Network or service endpoint issues may cause connection failures; verify the vLLM URL if used.