Everything you post to Discord, from one place
Compose once, tune it for Discord, and publish or queue it beside every other network you run.
Request the connector
Open Channels and request Discord. No account or credential is collected until the connector is implemented, and the request is recorded once per workspace.
Queue it
Publish straight away or pick a time. A delivery that fails retries on its own.
Confirm it landed
Every post is re-checked after publishing and keeps a receipt: what went out, what did not, and why.
Formats lined up for Discord
Or skip the dashboard entirely
Discord questions
Not yet. Discord is request-only: it cannot be connected or selected for a post. Request it from Channels and we will use demand to prioritise the work.
Not to request it. PostWharf collects no Discord credential while the connector is request-only; the connection requirements will be stated before account access opens.
Not yet. The Discord request records demand for the workspace; account connection will open when the connector is implemented.
A Discord post cannot enter the queue yet. The API returns `connector_request_only` before writing anything, so no simulated receipt can look real.
Not until the Discord connector is implemented. The API refuses request-only channels instead of fabricating a delivery receipt.