Delete Post: WordPress action

Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

Field	Type	Required	Description
Post ID postId	number	Required	Post ID
Permanently Delete force	boolean	Optional	If false, moves to trash. If true, permanently deletes.

Sample request

{
  "postId": "{{trigger.postId}}",
  "force": "{{trigger.force}}"
}

Returns

{
  "id": 42,
  "status": "trash",
  "deleted": true
}

Use these fields in downstream nodes for routing, logging, or error handling.

FAQ

Questions about Delete Post.

What does the Delete Post action do in WordPress?

Deletes a WordPress post. By default moves it to trash; pass force=true to permanently delete. Use the soft-delete path for safety.

What inputs does Delete Post require?

Required: Post ID. Every input accepts a static value or a variable from any upstream node in your workflow.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if WordPress returns an error?

The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does Delete Post support batch operations?

Yes. Run Delete Post inside a Loop node to process arrays. Tiny Command handles WordPress's rate limits automatically so you don't have to throttle manually.

More actions