Webhook logo
WordPress.com logo

Workflow template

Create a WordPress.com draft post from a webhook

Create a WordPress.com draft post from incoming title and content. Choose a Site, use an authenticated backend sender and review the draft in WordPress; this workflow does not publish it.

How it works

From incoming post content to a reviewable draft

1 Trigger · 1 Action
Webhook1 · Trigger

Incoming content webhook

Receive title and content in webhook JSON. The title is required and content is an optional mapped field; use a backend sender and source authentication.

WordPress.com2 · Action

Create a draft post

Create a new post on the configured WordPress.com Site with status: draft. This is a create operation, with no existing-post lookup, publication or scheduled publishing step.

The result

A new post draft waiting for editorial review

Example WordPress.com draft post

FICTIONAL WordPress draft post

FICTIONAL content received from a webhook.

Illustrative mapped post content from the included fictional request. The action fixes draft status and uses the Site you select rather than a caller-selected publication destination.

Before activation

Set up your workflow

  1. Connect WordPress.com and select a Site

    Choose the destination Site before activation. The required site_id begins blank and remains an action setting.

  2. Prepare an authenticated backend request

    Send title and content in JSON from a backend sender. Protect the generated URL with source authentication and retain status: draft in the action.

  3. Review a fictional post draft

    Activate and submit controlled content. Inspect the post in WordPress before another request or manual rerun, and make any publishing decision separately after review.

Details and limitations
  • Draft status is enforced by the mapping. Incoming publication fields do not override status: draft. No immediate or scheduled publishing action is configured.

  • The starter maps title and content only. Site is selected separately. Categories, tags, author assignment, featured image and a destination post ID are not mapped; add suitable fields deliberately if your editorial process needs them.

  • This creates posts rather than updating them. Only new requests after activation are processed. Repeated requests and manual reruns create additional drafts, with no title matching, post-ID lookup or upsert.

Questions about this template

Can incoming status: publish publish the post?

No. The action fixes status to draft and does not schedule publication. The post remains available for review in WordPress.

Do I need an existing post ID?

No. This creates a new draft post on the Site selected in the action. There is no existing-post ID or update mapping.

Are categories, tags or a featured image copied?

No. The prepared request maps title and optional content. Categories, tags, author assignment and featured image fields are not included.

Will another request replace the previous draft?

No. Each accepted request or manual rerun creates another draft rather than upserting one. Use a backend sender, protect the source and inspect uncertain writes before retrying.

Explore connected apps