Your Mautic server comes with an AI operations assistant living in the Open WebUI chat. It can read your Mautic files and configuration, run commands, query the database, and restart services. You type what you want in plain language and it does the work, explaining each step as it goes. Here are ten everyday jobs worth handing over instead of clicking through the admin panel.
1. Merge duplicate contacts
Duplicates creep in through imports, form submissions, and API calls, and they quietly skew your segment counts and campaign stats. The assistant can query the contacts table for rows sharing an email address, pick the record with the most activity, and merge the rest while preserving history. It can also tell you where the duplicates came from, so you can fix the source.
This is a job most owners avoid for months because the merge UI is tedious one record at a time. A single request clears the backlog. Ask: “Find contacts with the same email address and merge the duplicates, keeping the record with the most page hits.”
2. Import contacts from a CSV on the server
If you have a spreadsheet of leads sitting on the machine, you don’t need the browser uploader and its progress spinner. Point the assistant at the file and it inspects the columns, maps them to your existing fields and custom fields, respects the do-not-contact flag, and imports in safe batches. It can also produce a short report of rows that failed and why.
Watch the field mapping in its summary before it runs — a wrong guess turns “Company” into a first name. Once the mapping is confirmed, the import itself is quick. Try: “Import /root/leads-october.csv into contacts, map the ‘Company Size’ column to my company_size custom field, and skip rows without an email.”
3. Keep the cron jobs healthy
Mautic leans on a handful of cron jobs: mautic:segments:rebuild, mautic:campaigns:rebuild, mautic:campaigns:trigger, and mautic:emails:send. If one stops, segments freeze and campaigns stall silently, and the first sign is usually “my emails aren’t going out.” The assistant can inspect the crontab, check when each job last ran, and read the logs for errors.
Fixing a stuck job might mean repairing a path after a move, unblocking a lock file, or simply re-adding a line that got wiped. The point is you find out in one question instead of after a lost week. Ask: “Show me the Mautic cron jobs, when they last ran, and fix any that are failing.”
4. Push queued emails out
When you send with the queue or spool enabled, campaign emails wait on disk until mautic:emails:send runs. That’s good for throughput, but it means a broken cron or full spool directory silently delays everything. The assistant can flush the queue on demand, watch the send log for SMTP rejections, and tell you how many messages actually left.
Run this after you launch a campaign and want confirmation the first batch landed, or when someone complains they never got the email. Say: “Send all queued campaign emails now and tell me how many were delivered.”
5. Prune bounced addresses and honor unsubscribes
Hard bounces and people who clicked unsubscribe must not keep receiving your mail, or your sender reputation sinks and even good contacts stop seeing you. The assistant can review the email stats tables, confirm which addresses are already flagged as do-not-contact, and flag the ones that bounced but somehow escaped the flag. It can also show you the bounce rate trend over the last few months.
Treat this as monthly hygiene. The assistant does the analysis in minutes; you just approve the list before it marks anything. Ask: “List addresses that hard-bounced in the last 30 days and mark them do-not-contact.”
6. Spin up a newsletter email from a template
Building a broadcast email in the drag-and-drop builder takes twenty minutes you don’t have, and most of that is fighting layout. Give the assistant your copy and it clones one of your existing themes, swaps the subject and body, and saves a draft for you to review. It keeps the theme structure intact, so nothing shifts when you open it.
This is also a good way to enforce consistency: same header, same footer, same button style every send. You stay the editor; the assistant does the assembly. Try: “Create a draft email using my ‘monthly-newsletter’ theme, set this subject line, and replace the intro paragraph with the text I paste next.”
7. Embed a form and turn on tracking
Mautic forms work anywhere you can paste HTML, and the mtc.js tracking script is what makes contact scoring and page-hit triggers useful. The assistant generates the exact embed code for a form, checks your site’s pages for the script, and confirms the tracking code carries the right site URL.
Broken tracking is the classic silent failure: forms work, but no page hits ever appear. Have the assistant verify both ends after any theme change on your site. Ask: “Generate the embed code for my ‘newsletter-signup’ form and tell me exactly where to paste it in my site template.”
8. Back up before you upgrade
Mautic upgrades touch the database and the vendor files at once, which makes them riskier than a normal plugin update. Before you update anything, have the assistant dump the database and archive the app directory so a rollback is one command away. It can also verify the dump restores cleanly instead of just trusting it.
Store the backups somewhere outside the app directory, ideally off the web root. The assistant can name files with dates and prune old ones so the disk doesn’t fill. Say: “Back up my Mautic database and app folder to /root/backups with today’s date in the filename.”
9. Get a weekly digest of your numbers
Instead of logging in to check dashboards, ask the assistant for the numbers directly. It can query the contacts, email stats, and page hit tables and hand you new contacts, emails sent, open rate, and top landing pages for any period you name. Formatting it as a short email summary turns it into a standing ritual.
Use it as an early-warning system too: open rate sliding for three weeks means subject lines or list quality, not luck. Ask: “Email me every Monday a summary of new contacts, emails sent, and open rate for the last 7 days.”
10. Adjust a segment’s filters on request
Segments power everything else in Mautic, and their filters live in the UI or, just as honestly, in the database. The assistant can add a filter, rebuild the segment with mautic:segments:rebuild, and report the new member count before you wire it into a campaign.
This is faster than the UI for multi-condition segments, and it leaves a record of exactly what changed. You can always ask it to show the filter as SQL. Try: “Add a filter to my ‘trial-users’ segment so it only includes contacts created in the last 30 days, then rebuild it.”
None of this needs the admin panel. It needs a chat window and cron jobs that run. Start with one job, check the result, and hand over more as you trust it.
