Listmonk publishing as software
Codex runs postqueen commands, reads the JSON results and verifies each step, so your Listmonk pipeline behaves like any other task it automates in CI or cron.
Point Codex at the postqueen CLI and it creates, schedules and verifies Listmonk campaigns as one repeatable task you can rerun any time.
Set up the CLI inside the workspace Codex uses, then describe the Listmonk outcome you want in the task prompt.
# Inside a Codex sessionnpm install -g postqueenexport POSTQUEEN_API_KEY=your_api_key # Then prompt:# "Create this week's Listmonk campaigns# from notes.md and schedule them# with postqueen"Codex runs postqueen commands, reads the JSON results and verifies each step, so your Listmonk pipeline behaves like any other task it automates in CI or cron.
Tell Codex when your lists are busiest and it schedules campaigns into that window on Listmonk, day after day, without reminders.
Codex drafts the campaign and postqueen delivers it to your Listmonk lists, so subscribers hear from you on a schedule you set once.
Ask Codex for drafts only. They sit on the postqueen calendar unscheduled, so you can edit them and pick the time yourself, and nothing reaches your subscribers on Listmonk until you do.
Codex calls postqueen to list your connected lists and sees what Listmonk supports, so drafts start from real capabilities, not guesses.
Give it the brief. The agent writes Listmonk-shaped campaigns and proposes publish times that match when your subscribers are around.
Look over the queue on the postqueen calendar and change anything you want. postqueen publishes each post at its time, and Codex can pull the results after.
Codex reads these limits from postqueen before it composes, so a draft that would be rejected never reaches the queue.
Scheduling, AI drafts, analytics and team roles, in one guide.
Install the postqueen CLI where Codex runs commands and export your API key. Every command returns JSON, so the agent can create, schedule and list Listmonk campaigns reliably.
Yes. Give it exact slots or a rule like mornings at nine and it sets publish times on the campaigns it creates, keeping your lists active on a steady rhythm.
Only if you ask it to. Tell it to save drafts and nothing is scheduled: the campaigns wait on the calendar until you set a time. Tell it to schedule, and they go out at the times you can see, which is the setup most people move to once they trust the output.
Yes. postqueen connects 30 channels, so Codex can turn the same brief into Listmonk campaigns plus adapted versions for every other channel you run.
No. The agent uses your regular API key and plan limits: unlimited posts on every plan, and channel counts from 5 on Creator up to uncapped on Ultimate.
Yes. It can draft the subject line and the body, tighten a rambling section, or repurpose a blog post into email form. You review everything before it is handed to Listmonk, and nothing sends until you schedule it.
Listmonk records campaign views and link clicks in its own dashboard when tracking is enabled, and that data stays on your server. postqueen keeps the calendar side: which campaigns went out, when, and how they line up with the rest of your content.
Queue this week's posts in minutes, or hand the whole thing to your favorite AI. postqueen keeps publishing either way.
Seven days free. Cancel in one click from settings.