Agreed, and I gave some more thought as to what an AI agent really is. A field is a container of data specific to an entity. Even "Call" or "conference" field type in Fibery under the hood would be a separate auto generated channel link per entity.
An AI agent is more of an function than anything else. Takes an input, maybe does something, then returns an output. This input and output is knowledge and data, but the function itself is not. So I agree that maybe this idea was suggested too quick. Note for not so far future, getting the full output in automation steps like so: Do automation actions return step results? Can we use them further down the automation stack? - #4 by gb_carbone, would allow for lots of flexibility to build your own AI Workflows without the need for so many automations. Right now we can’t create a new linked thing, then update it’s description with the smart agent’s response. It needs to be two seperate automations, one to create, and one triggered on creation.
The only thing, @mdubakov, is that I haven’t been able to use the Smart Agent in rules… It works in button presses, but i can’t get it to work in any way in rules. Not sure if Im setting it up wrong or its a bug still.
When it gets fixed, I have an idea to make my own “AI Chat” using just automation actions. I’ll send a video here when it works. Then it knows context, and can be given permission like any other entity in fibery. The only thing I’m confused about is that it might query and return data the user doesn’t have access to… i’ll play with it and report back!