From ChatGPT draft to Lemmy queue
The writing already happens in ChatGPT. With the public API or the CLI, the same conversation can create scheduled Lemmy posts instead of text to paste.
Draft Lemmy posts in ChatGPT, then let postqueen schedule and publish them. One conversation in, a full Lemmy queue out.
Point a custom GPT action at the public API, or let agent modes that run commands use the CLI for Lemmy.
# Custom GPT action: call the public APIPOST https://api.postqueen.ai/public/v1/postsAuthorization: your_api_key # Or in agent modes that run commands:npm install -g postqueenpostqueen posts:create --json lemmy-week.jsonThe writing already happens in ChatGPT. With the public API or the CLI, the same conversation can create scheduled Lemmy posts instead of text to paste.
Tell ChatGPT when your communities are busiest and it schedules posts into that window on Lemmy, day after day, without reminders.
ChatGPT targets the exact communities you choose and keeps every submission reviewable, so you can check each one against community rules first.
Ask ChatGPT for drafts only. They sit on the postqueen calendar unscheduled, so you can edit them and pick the time yourself, and nothing reaches your community members on Lemmy until you do.
ChatGPT calls postqueen to list your connected communities and sees what Lemmy supports, so drafts start from real capabilities, not guesses.
Give it the brief. The agent writes Lemmy-shaped posts and proposes publish times that match when your community members are around.
Look over the queue on the postqueen calendar and change anything you want. postqueen publishes each post at its time, and ChatGPT can pull the results after.
ChatGPT 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.
Through the public API from a custom GPT action, or through the CLI in agent modes that execute commands. Both use the same API key and cover Lemmy posts end to end.
Yes. Give it exact slots or a rule like mornings at nine and it sets publish times on the posts it creates, keeping your communities active on a steady rhythm.
Only if you ask it to. Tell it to save drafts and nothing is scheduled: the posts 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 ChatGPT can turn the same brief into Lemmy posts 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. The built-in assistant drafts titles and Markdown bodies from a short prompt and rewrites anything you highlight, and nothing publishes until you schedule it. Keep it grounded and specific: Lemmy communities are small and read closely, so generated filler gets spotted fast. Agents like Claude Code or OpenClaw can prepare a whole queue through the MCP server.
postqueen keeps a full history of what it published, in which community and when, so you can compare communities and time slots. Scores and comment threads live on Lemmy itself, since the network has no central analytics dashboard and every instance holds its own copy of the data. Reading your queue history next to the discussion is what tells you which communities actually want your posts.
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.