From ChatGPT draft to Telegram queue
The writing already happens in ChatGPT. With the public API or the CLI, the same conversation can create scheduled Telegram messages instead of text to paste.
Draft Telegram messages in ChatGPT, then let postqueen schedule and publish them. One conversation in, a full Telegram queue out.
Point a custom GPT action at the public API, or let agent modes that run commands use the CLI for Telegram.
# 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 telegram-week.jsonThe writing already happens in ChatGPT. With the public API or the CLI, the same conversation can create scheduled Telegram messages instead of text to paste.
Tell ChatGPT when your channels and groups are busiest and it schedules messages into that window on Telegram, day after day, without reminders.
ChatGPT lists your connected channels and groups before it posts, so messages land exactly where they should and announcements stay consistent.
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 subscribers on Telegram until you do.
ChatGPT calls postqueen to list your connected channels and groups and sees what Telegram supports, so drafts start from real capabilities, not guesses.
Give it the brief. The agent writes Telegram-shaped messages 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 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 Telegram messages end to end.
Yes. Give it exact slots or a rule like mornings at nine and it sets publish times on the messages it creates, keeping your channels and groups active on a steady rhythm.
Only if you ask it to. Tell it to save drafts and nothing is scheduled: the messages 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 Telegram messages 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.
The usual causes: the bot lost its admin rights, it was removed from the channel, or a file exceeded the Bot API's 50 MB send limit. postqueen marks failed posts so you can fix the cause and retry.
Yes. The assistant drafts and rewrites posts and captions in your channel's voice, and you pick the time before it publishes. Agents can also run the whole pipeline through the CLI and the built-in MCP server.
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.