From ChatGPT draft to Dev.to queue
The writing already happens in ChatGPT. With the public API or the CLI, the same conversation can create scheduled Dev.to articles instead of text to paste.
Draft Dev.to articles in ChatGPT, then let postqueen schedule and publish them. One conversation in, a full Dev.to queue out.
Point a custom GPT action at the public API, or let agent modes that run commands use the CLI for Dev.to.
# 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 devto-week.jsonThe writing already happens in ChatGPT. With the public API or the CLI, the same conversation can create scheduled Dev.to articles instead of text to paste.
Tell ChatGPT when your readers are most active and it schedules articles into that window on Dev.to, day after day, without reminders.
ChatGPT hands postqueen the full draft, formatting included, and it lands on your Dev.to profiles as complete articles, ready for readers.
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 readers on Dev.to until you do.
ChatGPT calls postqueen to list your connected profiles and sees what Dev.to supports, so drafts start from real capabilities, not guesses.
Give it the brief. The agent writes Dev.to-shaped articles and proposes publish times that match when your readers 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 Dev.to articles end to end.
Yes. Give it exact slots or a rule like mornings at nine and it sets publish times on the articles it creates, so your readers see them at the right moment.
Only if you ask it to. Tell it to save drafts and nothing is scheduled: the articles 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 Dev.to articles 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. Write the article once in postqueen and send it to Dev.to and your other blog channels in one pass, with per-platform tweaks before publishing. Set the canonical URL on the Dev.to copy so search engines credit the original post on your own site.
Yes. It can outline a tutorial, draft the intro, or write a full first pass in a tone that fits a developer audience, and it respects your code samples. Nothing publishes until you have read the draft and put it on the calendar.
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.