>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3565644. --> Reported by: [yautja_cetanu](https://www.drupal.org/user/626050) Related to !6 >>> <h3 id="summary-problem-motivation">Problem/Motivation</h3> <h4 id="summary-steps-reproduce">Steps to reproduce</h4> <h3 id="summary-proposed-resolution">Proposed resolution</h3> <p>To complete the whole flow we need Deepchat Chatbots that are attached to Assistants to be part of the flowdrop UI.</p> <p>- Chatbots are a trigger so perhaps should use the trigger type.<br> - They should go below Agents in the list as they are a new category type.<br> - We are wanting to use the DeepChat block for the configuration of the chatbot.<br> - Like other nodes saving the chatbot should save to the configuration of the chatbot, nothing in the flowdrop UI.<br> - They should appear to the left of assistants.<br> - An assistant can have more than one chatbot attached (but most of the time won't). The Assistants have to be created before they can be attached to the chatbot when it comes to the order of saving.<br> - We have to bring across all the configuration from the chatbot like we have with Tools, this might be complicated as we have to decide where the chatbot goes (Theme and Region) even though really the chatbot doesn't go in any region, but we still need a UI for that.<br> - Remember its the Deepchat chat not the deprecated thing just called chatbot.<br> - The Drupal CMS Assistant is a good example of an assistant that has a chatbot.</p> <h3 id="summary-remaining-tasks">Remaining tasks</h3> <h3 id="summary-ui-changes">User interface changes</h3> <h3 id="summary-api-changes">API changes</h3> <h3 id="summary-data-model-changes">Data model changes</h3>