Block 1 - delete img
- Type / Role
- n8n-nodes-base.httpRequest - httpRequest
- Config choices
- Version 4.2
This workflow is provided as-is. Please review and test before using in production.
Why use this You need to delete (many) posts on a WordPress website and also delete the featured image associated with each post. Hours of rote work cut into a fraction with this automation. How it...
n8n-nodes-base.httprequest, n8n-nodes-base.filter, n8n-nodes-base.if, n8n-nodes-base.stickynote, n8n-nodes-base.manualtrigger
This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Eric.
Original n8n.io sourceYou need to delete (many) posts on a WordPress website and also delete the featured image associated with each post.
Hours of rote work cut into a fraction with this automation.
pending posts, with oldest firstThis is arbitrary and depends on your own use case. Maybe you have an editor who needs to approve the post deletion. You might want to get approval by email, slack msg or ticketing system.
Or maybe you just want to monitor the process and spare specific posts from deletion.
I used the Filter node to only grab the first item (itemIndex < 1) which in this case was the oldest pending post.
This could also be expanded to two separate workflows:
pending post is created that sends an approval requestThis would require another HTTP request, similar to the DELETE post request, that instead publishes the post.
This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.
| Workflow | Batch Delete Posts and Featured Images in WordPress |
|---|---|
| Complexity | intermediate |
| Nodes | 14 |
| Categories | Miscellaneous |
| Author | Eric |
| Published | 16 Jun 2025 |
Use the JSON export at /data/workflows/4976/4976.json as the source template for this automation.
Open n8n, import the downloaded JSON, and review each node before activating the workflow.
Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.
Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.
Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.
Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.
Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.
Why use this You need to delete (many) posts on a WordPress website and also delete the featured image associated with each post. Hours of rote work cut into a fraction with this automation. How it...
Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.
Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your Miscellaneous use case.