# What if AI Chat was a field? Or an automation where builder can make their own AI Chat embedded where needed? **URL:** \ **Category:** Ideas & Features\ **Tags:** ai\ **Created:** [May 22, 2025, 3:50pm UTC](https://community.fibery.io/t/what-if-ai-chat-was-a-field-or-an-automation-where-builder-can-make-their-own-ai-chat-embedded-where-needed/8844 "2025-05-22T15:50:48Z")\ **Posts on this page:** 1\ **Showing post:** 7
**Author:** ![Yuri\_BC](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/yuri_bc/32/8803_2.png) [@Yuri\_BC](https://community.fibery.io/u/Yuri_BC)\ **Post date:** [May 24, 2025, 2:08pm UTC](https://community.fibery.io/t/what-if-ai-chat-was-a-field-or-an-automation-where-builder-can-make-their-own-ai-chat-embedded-where-needed/8844/7 "2025-05-24T14:08:34Z")
I am actually now building an MAS (Multi Agent System) in Fibery and a lot of its operational functionality is not done by AI at all, but by automations. This has actually benefits if done well - because it gives the reliability needed which AI does not have yet, and likely may not have very soon. The idea is that in fibery I create an AI Language that can be used in automation triggers. Its alsocalled **structured prompting** or **schema-based prompt engineering** , which refers to designing prompts in a consistent, machine-readable format so AI outputs can be reliably parsed and turned into actions or workflows. This approach is often combined with **function calling** or **domain-specific prompt languages** to automate follow-ups like entity creation or task execution. So the Smart Agent that Fibery now is building could do a lot, but I think that the management and control of the chained Smart Agent calls is more interesting for Fibery users. --- _[View the full topic](https://community.fibery.io/t/what-if-ai-chat-was-a-field-or-an-automation-where-builder-can-make-their-own-ai-chat-embedded-where-needed/8844)._