changed description "The "Replace chatbot" Action will be got a lot of improvements! It is now able to dynamically select with use flow attributes both for the chatbot (using the slug) and the action to execute. It's 10x faster then the previous version It's now available a "slug" property to reference the destination chatbot. A “slug” property for the flows (aka chatbots) is introduced to uniquely identify each chatbot and simplify navigation, including import-export operations. This is property is necessary because relying when building chatbot exeperiences to export in other projects. Referencing a chatbot by its name is risky, given that names can easily change over time. While the slug is stable e designed only for reference purposes. Find more info on the chatbot’s name is risky, given that names can easily change over time. "

changed description "https://storage.sleekplan.com/products/869241497/feedback/196365/comments/289187/acfab2e7f3fda5b4a57f3cf361a870ad.jpg The "Replace chatbot" Action got a lot of improvements! It is now able to dynamically use flow attributes for the chatbot (using the slug) and the action to execute. It's 10x faster then the previous version It's now available a "slug" property to reference the destination chatbot. A “slug” property for the flows (aka chatbots) is introduced to uniquely identify each chatbot and simplify navigation, including import-export operations. This property is necessary when building chatbot exeperiences to export in other projects. Referencing a chatbot by its name is risky, given that names can easily change over time. While the slug is stable e designed only for reference purposes. Find more info on the slug property here: https://gethelp.tiledesk.com/articles/enhancing-conversation-flows-with-replace-bot-action/#replace-bot-using-the-chatbot-slug "

changed description "https://storage.sleekplan.com/products/869241497/feedback/196365/comments/289187/acfab2e7f3fda5b4a57f3cf361a870ad.jpg ** The "Replace chatbot" Action got a lot of improvements! It is now able to dynamically use flow attributes for the chatbot (using the slug) and the action to execute. It's 10x faster then the previous version It's now available a "slug" property to reference the destination chatbot. A “slug” property for the flows (aka chatbots) is introduced to uniquely identify each chatbot and simplify navigation, including import-export operations. This property is necessary when building chatbot exeperiences to export in other projects. Referencing a chatbot by its name is risky, given that names can easily change over time. While the slug is stable e designed only for reference purposes. Find more info on the slug property here: https://gethelp.tiledesk.com/articles/enhancing-conversation-flows-with-replace-bot-action/#replace-bot-using-the-chatbot-slug "

changed description " The "Replace chatbot" Action got a lot of improvements! It is now able to dynamically use flow attributes for the chatbot (using the slug) and the action to execute. It's 10x faster then the previous version It's now available a "slug" property to reference the destination chatbot. A “slug” property for the flows (aka chatbots) is introduced to uniquely identify each chatbot and simplify navigation, including import-export operations. This property is necessary when building chatbot exeperiences to export in other projects. Referencing a chatbot by its name is risky, given that names can easily change over time. While the slug is stable e designed only for reference purposes. Find more info on the slug property here: https://gethelp.tiledesk.com/articles/enhancing-conversation-flows-with-replace-bot-action/#replace-bot-using-the-chatbot-slug **"

changed description " The "Replace chatbot" Action got a lot of improvements! It is now able to dynamically use flow attributes for the chatbot (using the slug) and the action to execute. It's 10x faster then the previous version It's now available a "slug" property to reference the destination chatbot. A “slug” property for the flows (aka chatbots) is introduced to uniquely identify each chatbot and simplify navigation, including import-export operations. This property is necessary when building chatbot exeperiences to export in other projects. Referencing a chatbot by its name is risky, given that names can easily change over time. While the slug is stable e designed only for reference purposes. NOTE: to get the new features you must replace all the old actions with the new one. Find more info on the slug property here: https://gethelp.tiledesk.com/articles/enhancing-conversation-flows-with-replace-bot-action/#replace-bot-using-the-chatbot-slug "