Your Listmonk server is up and the vibe-code agent is waiting in the Open WebUI chat, able to read the app’s files, query its Postgres database, and restart services. Listmonk is already strong at bulk email — lists, segments, templates, campaigns — but every job still means clicking through the admin panel and getting the details right by hand. You can type the job in plain language instead and watch the agent do it, then verify what it changed. Here are ten everyday tasks worth delegating.

1. Draft and Test-Send a Campaign

You have a list and a template; sending means filling in five fields and hoping nothing looks broken when it lands. Have the agent create the campaign against your list, set the subject and preview text, and fire a test email to your own address before anything touches the queue. It can read your templates through the admin API and tell you exactly which one it used, so there are no surprises at send time. “Create a campaign called October update for the ‘customers’ list using the default template, then send a test to me@mydomain.com and show me the campaign ID.”

2. Import a Subscriber CSV Without Mangling It

CSV imports go wrong in quiet ways: wrong delimiter, attributes that never map, subscribers landing in no list at all and silently vanishing. Give the agent the file path and let it inspect the header row first, then run the import with the columns mapped and your custom columns stored as subscriber attributes in Listmonk’s JSON attribs field. It can then count what landed and pull a sample row from the database to prove the mapping worked. “Import /root/contacts.csv into the ‘newsletter’ list, map the ‘company’ column into attributes, skip rows with no email, and show me the first three imported subscribers.”

3. Build a Segment That Actually Targets People

Segments in Listmonk are query expressions over subscriber fields and attributes, and most owners never touch them because the syntax is unforgiving — one wrong operator and you email the wrong half of your list. The agent can write the expression, test it against the live subscriber table, and tell you exactly how many people match before you commit anything. “Build me a segment of subscribers who joined in the last 90 days and whose ‘plan’ attribute is ‘trial’, and tell me how many people it matches.”

4. Turn On Double Opt-In Properly

Double opt-in is one setting plus a confirmation email that has to be right — if the from-address or template is off, confirmations silently fail and your list stops growing while you wonder why. Ask the agent to switch the list to double opt-in, review the opt-in email that goes out, and run a live test subscription end to end, including the confirmation click. “Switch the ‘newsletter’ list to double opt-in, make sure the confirmation email comes from noreply@mydomain.com, and walk a test signup through to confirmed.”

5. Write a Template That Survives Contact

The stock template is plain, and hand-built HTML email breaks in Outlook and Gmail within minutes if you do not know the rendering quirks. The agent can write a clean table-based template with preheader text, a correct unsubscribe link, and tracked links, save it in Listmonk, and send you a test render so you see what subscribers see. “Write a new template called ‘monthly’ with our header, an unsubscribe link in the footer, and link tracking on, then send me a test.”

6. Schedule the Send for Tuesday Morning

Timing matters, and you are not going to log in at 9am to press a button — so campaigns drift to whatever hour you happened to remember. The agent sets the send date with the right timezone on a draft campaign and confirms what is queued. It can also list every scheduled campaign so you see the whole calendar at a glance and nothing double-books your list. “Schedule the October update campaign for Tuesday at 9:00 Europe/Berlin and list everything currently queued or scheduled.”

7. Read the Numbers After a Send

The campaign page shows opens, clicks, unsubscribes, and bounces, but pulling a useful summary takes clicking through tabs and doing mental arithmetic. Ask the agent to query the campaign data directly and give you the story: sent, delivered, opened, clicked, bounced, and who unsubscribed, plus the link-level detail if you want it. “Summarize the last campaign — how many were sent, delivered, opened, clicked, bounced, and unsubscribed — and list the five most-clicked links.”

8. Scrub Bounces and Duplicates

A dirty list burns sender reputation: hard bounces that keep getting mailed, duplicate addresses that receive the newsletter twice and hit unsubscribe out of annoyance. The agent can blocklist the hard bounces using Listmonk’s blocklist so they never receive another campaign, find duplicate emails while keeping the oldest record, and report counts before and after. “Blocklist everyone who hard-bounced in the last 6 months, dedupe the ‘newsletter’ list keeping the oldest record, and give me counts before and after.”

9. Add a Second SMTP Server and Pace the Queue

When one SMTP account caps you at a few hundred emails an hour, sends crawl; push too hard against its limit and you land in spam or get the account throttled. The agent edits config.toml to add a second server with its own rate limit, tunes the batch size and sliding-window limit, and restarts Listmonk cleanly so the queue picks up where it left off. “Add my second SMTP server from Brevo to config.toml with a 200-per-hour limit, keep the primary at its current limit, and restart Listmonk.”

10. Pause, Rescue, or Cancel a Running Campaign

Every long-time Listmonk user has watched a campaign go out with a broken link or the wrong subject, powerless as the counter climbs. The agent can pause a running send mid-flight, tell you exactly how many messages have gone out, fix a draft and reschedule it, or cancel a runaway campaign entirely. It confirms the final state from the database rather than guessing, which is the reassurance you want in that moment. “Pause the running campaign immediately, tell me how many messages went out so far, and do not resume until I say so.”

None of this needs you to learn the admin panel’s corners or the segment query syntax. You describe the job, the agent does it, and it shows its work so you can check it. That is the whole point of having it on the server. Listmonk on OpenSysLab