Request the WordPress connector
WordPress is visible in PostWharf but is not available to connect or publish to yet. Request it from the Channels screen and we’ll use workspace demand to prioritise the connector.
Request connectorWhat requesting WordPress does
PostWharf cannot publish to WordPress yet. Requesting it is how a workspace tells us to build it.
Request the connector
Open Channels and request WordPress. No account or credential is collected until the connector is implemented, and the request is recorded once per workspace.
Nothing is queued
WordPress cannot be selected for a post yet, so nothing is sent and nothing reports as delivered.
Publish everywhere else
The ten networks that publish today work as normal from the same workspace.
Formats lined up for WordPress
Ask for WordPress from Channels
WordPress questions
Not yet. WordPress 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 WordPress credential while the connector is request-only; the connection requirements will be stated before account access opens.
Not yet. The WordPress request records demand for the workspace; account connection will open when the connector is implemented.
A WordPress post cannot be queued yet, so nothing is sent and no receipt is created.
Not until the WordPress connector is implemented. The API refuses request-only channels instead of fabricating a delivery receipt.