Module description is unhelpful

Should the module be a part of an "AI Core" module then? Feels like what you have here is a module that lets you automate adding or editing content into fields, and part of what it can do is integrate with the AI module. I'm not quite seeing the criteria for this being a part of the main module when essential things like providers are separate projects? Equally I'm not sure why you would use this module and not the ECA/AI integration?

The main part is still the AI part and the most used Automator Types are in the core.

We did have discussions on if it should be in or out, I think this is another contribution to that discussion.

Regarding ECA, it provides a lot simple way of deconstructing complex prompts or services to fit a specific field without you having to know how the storage works for that field. They even work together - you can trigger an Automator via ECA when you need complex conditionals.

OK, updated. There's probably a discussion to be had about updating the project page to explain under what circumstances you'd want to use which modules (like I say, I can't see how this does anything that you couldn't do with ECA - you seem to be saying that ECA needs advanced knowledge to use, which sounds like a reason to imp[rove the ECA module rather than a reason to create the AI Automators one).

Thanks, getting merged.

Automatically closed - issue fixed for 2 weeks with no activity.