Update chatbot settings
update_chatbot_settingsDestructive
Update a chatbot's settings. Only the fields you pass are changed. Call get_chatbot first to see allowed_models before changing gpt_model.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| topK | No | Retrieved-chunk count 1-3. | |
| gpt_model | No | LLM model id. Must be one of the chatbot's allowed_models. | |
| chatbot_id | Yes | The chatbot id. | |
| temperature | No | Sampling temperature 0-2. | |
| history_count | No | Conversation history turns 0-10. | |
| default_answer | No | Fallback answer when the bot cannot answer. | |
| welcome_message | No | Welcome message (max 500 chars). Separate multiple bubbles with a blank line. | |
| escalations_email | No | Semicolon-separated email addresses notified on escalation. | |
| enable_escalations | No | Turn human-handoff escalations on/off. | |
| enable_lead_capture | No | Turn the lead-capture form on/off. | |
| instructions_prompt | No | System/instructions prompt (max 20000 chars). | |
| lead_capture_fields | No | Lead-capture field definitions {type,name,required,enabled,order}. Required when enabling lead capture. | |
| escalate_message_threshold | No | Messages before a human handoff is offered (1-10). | |
| enable_escalations_round_robin | No | Rotate escalation emails round-robin across the addresses. | |
| enable_escalations_notification | No | Email a notification when a conversation escalates. |