Posts and channels

Every post names the channels it goes to, by their IDs. This page starts with the channel commands, then covers the life of a post: create, list, change, delete. Every command and flag is also on the command reference.

Find your channels

postqueen integrations:list

🔌 Connected Integrations:
[
  {
    "id": "cmf1abc2d0001",
    "name": "PostQueen Bakery",
    "identifier": "bluesky",
    "picture": "https://...",
    "disabled": false,
    "profile": "postqueenbakery.bsky.social",
    "customer": { "id": "cmf0cust00001", "name": "Bakery" }
  }
]

id is what -i takes. identifier is the network, such as bluesky, wordpress or devto. customer appears when the channel is sorted into a customer. A channel with "disabled": true is turned off in the app and does not publish.

postqueen integrations:list | tail -n +2 | jq -r '.[] | "\(.identifier)\t\(.id)\t\(.name)"'

BLUESKY_ID=$(postqueen integrations:list | tail -n +2 | jq -r '.[] | select(.identifier=="bluesky") | .id' | head -n 1)

postqueen integrations:groups
postqueen integrations:list --group "cmf0cust00001"

integrations:groups lists your customers as id and name.

Read what a network needs

postqueen integrations:settings <channel-id>

The answer is an output object:

Field	What it is
`rules`	The network’s posting rules, in plain words
`maxLength`	The character limit of a post or comment on this channel
`settings`	The schema for `--settings`, with the required fields in a `required` list, or `No additional settings required`
`tools`	Helpers `integrations:trigger` can run to look up values, each with a `methodName` and the inputs it takes

Bluesky and Nostr need no settings. WordPress needs a title and a post type, and DEV needs a title. Read the schema before you post to a network for the first time: examples by network shows the settings each one takes.

Look up a value

Some settings take a value only the network knows, such as a WordPress post type or a DEV tag. Run the helper that integrations:settings lists under tools:

postqueen integrations:trigger <channel-id> postTypes

🔧 Tool result for postTypes:
{
  "output": [
    { "id": "posts", "name": "Posts" },
    { "id": "pages", "name": "Pages" }
  ]
}

Pass a helper’s inputs with -d as JSON, for example -d '{"word":"baking"}' for a Lemmy community search. A name the channel does not offer fails with Tool not found.

Create a post

postqueen posts:create \
  -c "Our spring menu is live. Come by this weekend." \
  -s "2026-10-01T09:00:00Z" \
  -i "cmf1abc2d0001"

-s is required: the publish time in ISO 8601. The post is scheduled for that time. The answer lists one postId for each channel.

Save a draft

postqueen posts:create -c "Draft for review" -s "2026-10-01T09:00:00Z" -t draft -i "cmf1abc2d0001"

A draft keeps its date and waits on your calendar until you schedule it with posts:status. PostQueen checks a draft’s required settings too, so pass them now. The network’s rules on length and media are checked only when you schedule it, so a draft that was accepted can still be refused then.

Add images or a video

Upload each file first, then pass the returned path with -m. Separate several files with commas:

IMG=$(postqueen upload spring-menu.jpg | tail -n +2 | jq -r '.path')
postqueen posts:create -c "Spring menu" -m "$IMG" -s "2026-10-01T09:00:00Z" -i "cmf1abc2d0001"

A video has to finish processing first: see upload media.

Post a thread or add comments

Repeat -c. The first is the post, and each one after it is a reply or a comment. -m pairs with the -c in the same position, and -d sets the minutes to wait between items:

postqueen posts:create \
  -c "Three things we changed in the spring menu." \
  -c "First: every dish now has a smaller size." -m "$IMG" \
  -d 5 \
  -s "2026-10-01T09:00:00Z" \
  -i "cmf1abc2d0001"

An item may start with -, such as -c "- a smaller size": it is posted as written.The extra items become a thread on Bluesky, Nostr, X and Threads, and comments on Facebook, Instagram and Lemmy. YouTube, TikTok, WordPress, DEV, Hashnode and Listmonk publish the first item only. More in comments and threads.Because -m pairs by position, give every item before the last one with media its own -m, and -m "" to an item that has none. Leaving one out moves every later file onto the wrong item:

postqueen posts:create \
  -c "Three things we changed in the spring menu." -m "" \
  -c "First: every dish now has a smaller size." -m "$IMG" \
  -s "2026-10-01T09:00:00Z" \
  -i "cmf1abc2d0001"

Post to several channels

List the IDs with commas. Each channel gets its own post:

postqueen posts:create -c "Open on Sunday this week." -s "2026-10-01T09:00:00Z" -i "bluesky-id,nostr-id"

An empty ID, such as the one after a trailing comma in -i "bluesky-id,", is refused before anything is sent.One --settings object goes to every channel in -i, so mix only channels that take the same settings. For different text or settings per channel, use a --json file.

Pass a network's settings

postqueen posts:create \
  -c "<p>Every dish now comes in a smaller size.</p>" \
  -s "2026-10-01T09:00:00Z" \
  --settings '{"title":"Our spring menu","type":"posts"}' \
  -i "wordpress-id"

Wrap the JSON in single quotes. PostQueen adds the network’s type marker (__type) itself, so leave it out.

Describe the whole post in a file

postqueen posts:create --json campaign.json

The file is the request body the API receives. It needs type, date, shortLink and tags at the top, and one entry in posts per channel, each with its own text and settings. Every item in value needs an image list, empty when there is no media, and each image is the id and path from postqueen upload.

campaign.json

{
  "type": "schedule",
  "date": "2026-10-01T09:00:00Z",
  "shortLink": true,
  "tags": [],
  "posts": [
    {
      "integration": { "id": "bluesky-id" },
      "value": [{ "content": "Our spring menu is live.", "image": [] }]
    },
    {
      "integration": { "id": "wordpress-id" },
      "value": [{ "content": "<p>Every dish now comes in a smaller size.</p>", "image": [] }],
      "settings": { "title": "Our spring menu", "type": "posts" }
    }
  ]
}

type also takes now, which publishes at once. The flags only offer schedule and draft.

Good to know

Before it saves anything, PostQueen checks each post the way the app does: the settings, the length and the media. A draft gets only the settings check and the check that each item has text or media. A refused post names the channel and the reason; see troubleshooting.
--shortLink is on by default, which lets PostQueen swap links in the text for short links. PostQueen has no link shortener set up today, so links stay as written either way. Pass --no-shortLink to keep every link exactly as written.
The date is required even for a draft: it is the time the post goes out once you schedule it. A date that has already passed publishes the post at once.
(post:ID) in the text, with the ID of another post of your workspace, becomes that post’s address on its network when this post is published. If that post has no address yet, the placeholder is removed.

List posts

postqueen posts:list

Without dates it lists 30 days back to 30 days ahead. Narrow it with --startDate and --endDate in ISO 8601, and to one customer with --customer. The answer is an object with a posts list:

postqueen posts:list --startDate "2026-10-01T00:00:00Z" --endDate "2026-10-31T23:59:59Z" \
  | tail -n +2 | jq '.posts[] | {id, state, publishDate, channel: .integration.name}'

Each post has its id, content, publishDate, state (QUEUE, DRAFT, PUBLISHED or ERROR), settings (as a JSON string), releaseURL once published, error when it failed, and its integration.

Change a post

Its settings
Draft or scheduled

postqueen posts:settings <post-id> --settings '{"status":"pending"}'

Only the keys you pass change, and the text and time stay as they are. It works on drafts and on scheduled posts whose time has not passed. Pass the ID of the post itself, not of one of its comments. If you copy settings from posts:list, leave out __type.

postqueen posts:status <post-id> --status draft      # stop it from going out
postqueen posts:status <post-id> --status schedule   # queue it for its date

The date does not change. Scheduling a draft runs the length and media checks it skipped, and a draft whose date has already passed publishes at once. A post that was published or failed cannot change status: Cannot change status of a published or errored post.

To change a post’s text or time, edit it on the calendar in the app.

Delete a post

postqueen posts:delete <post-id>

This deletes the post and its comments or thread items on that channel, and stops it from going out. When one posts:create went to several channels, each channel has its own post, and the others stay. A post that was already published stays on the network: delete it there.

Connect a published post

Sometimes a network does not return a post’s ID after publishing, and analytics cannot find the post. This happens with TikTok. postqueen analytics:post then answers {"missing": true}. Analytics shows how to connect the post with posts:missing and posts:connect.

Next steps

Examples by network

A command for each network, with the settings it needs.

Upload media

Images and videos, and waiting for a video to be ready.

Command reference

Every command and flag on one page.

Troubleshooting agents

What each error means and how to fix it.

Start here

Assistants and bots

Coding agents

Editors and more

MCP reference

CLI reference

Troubleshooting

Find your channels

Read what a network needs

Look up a value

Create a post

Good to know

List posts

Change a post

Delete a post

Connect a published post

Next steps

Examples by network

Upload media

Command reference

Troubleshooting agents

​Find your channels

​Read what a network needs

​Look up a value

​Create a post

​Good to know

​List posts

​Change a post

​Delete a post

​Connect a published post

​Next steps

Examples by network

Upload media

Command reference

Troubleshooting agents

Find your channels

Read what a network needs

Look up a value

Create a post

Good to know

List posts

Change a post

Delete a post

Connect a published post

Next steps