AI Content Generator and Assistant for Magento 2

Yes. The extension connects to OpenAI, Anthropic Claude, Google Gemini, or Grok (xAI) with an API key you generate yourself, and the provider bills you directly for the tokens you use. We take no share of that spend. You can cap it: a bulk run can be limited to a set number of AI calls so a large rule spreads over several days, and a dry run lets you check a rule before it spends anything.

Both. An automation rule can pass the current value of the field into the prompt, so the model rewrites, shortens, or translates what is already there instead of starting from scratch. A regex condition narrows this further: the rule touches a field only when its existing value matches the pattern you set, which is how you fix a specific group of records and leave the rest alone.

Ticket scopes run on Mirasvit Help Desk MX. With it installed, the assistant drafts a reply from the ticket's history and built-in knowledge about your store, and an agent edits before sending. Product, category, CMS page, and newsletter generation works on a stock Magento install with no extra module.

Yes, for the text being generated. The extension sends the prompt and the field values it needs to the AI provider you connected, so those requests go to OpenAI, Anthropic, Google, or xAI under your own account and their terms. It does not support self-hosted or local models, so if your policy requires that data never leaves your infrastructure, this is the constraint to weigh. Nothing is sent to Mirasvit, and attached files are passed to the provider without being stored on your server.

Yes, through standard Magento roles. The extension adds six separate permissions under System → Permissions → User Roles: using the assistant, plus prompts, system messages, automation rules, logs, and history. A role without the first permission simply never sees the AI generate buttons on any edit page.

Yes. Image variables let a prompt include the product, category, or blog post images, so the model describes what it can see rather than guessing from attributes. You can also attach files to a request in the assistant window: images, PDFs, and spreadsheets are supported, which is how you generate a description from a supplier spec sheet. Files are sent to the AI provider and are not stored on your server.

Yes. Each prompt defines which attributes go into it, custom attributes included, and you write the prompt body as a template around those variables. You can also point a prompt at almost any field in the admin using a field selector, which is how the generate button appears next to fields the extension does not cover out of the box.

Use a system message. It is sent alongside the prompt and carries the role, tone, and rules the model must follow, so instructions like a required language or a banned phrase are not buried in the prompt body. The built-in prompts also instruct the model to return only the value, without preambles, explanations, code fences, quotes, or field labels, so generated text can go straight into the field.

Yes, as an automation rule rather than a separate import: it reads the content of your base store view and writes the translation into the target store view you select, keeping each view's own text. The model does the translating, so you are not limited to a fixed list of languages, and the system message that holds your brand voice applies to every language.

Yes. Run the rule in test mode and it reports what it would write without changing anything in the database. After a real run, the rule's Logs tab shows what happened, and history stores the previous value of every field the rule changed alongside the new one.