Pipedream WordPress steps in n8n

WordPress workflows on Pipedream are usually publishing pipelines: a draft from Google Docs or an LLM becomes a post, or a new post is pushed to social channels. n8n has a native WordPress node for posts, pages and users. Media and comments need an HTTP Request node.

The n8n WordPress node

n8n-nodes-base.wordpress:

Resource	Operations
Post	Create, Get, Get All, Update
Page	Create, Get, Get All, Update
User	Create, Get, Get All, Update

There is no media resource and no WordPress trigger.

Two Pipedream apps

Pipedream splits WordPress into WordPress.org (wordpress_org, your own site, no triggers) and WordPress.com (wordpress_com, OAuth, triggers New Post, New Comment, New Follower). Check which one your steps use; it decides the n8n credential.

What maps where

Pipedream	In n8n	Status
Create Post / Create New Post	WordPress → Post → Create	manual, 1 node
Update Post	Post → Update	manual
Search Posts	Post → Get All with search options	manual
Create User, Get User	User → Create / Get	manual
Upload Media	HTTP Request POST /wp-json/wp/v2/media with the WordPress credential, binary body	manual
Delete Post (WordPress.com app only)	HTTP Request DELETE /wp-json/wp/v2/posts/{id}	manual
New Post (WordPress.com source)	RSS Feed Trigger on the feed, or Schedule + Post → Get All	manual
Code step calling /wp-json/ with this.wordpress_org.$auth	Code node; credentials become variables listed in the report	automatic, review

WordPress actions are not in the converter's automatic list; they come through as placeholders with the original title, content, status and categories, so the rebuild is filling in one node.

Credentials

Self-hosted (WordPress.org):

1. In WordPress, open your user profile and create an Application Password. n8n's docs say two-step authentication must be enabled on the account to generate one.
2. n8n: Credentials → New → WordPress API, method Basic auth: username, application password, site URL.

WordPress.com: use the OAuth2 credential with a WordPress.com app's client ID and secret. OAuth2 does not work for self-hosted sites.

Typical migration: Google Docs draft to WordPress

Pipedream: Google Docs New Document → code step (convert to HTML) → WordPress Create Post (draft). n8n: Google Drive Trigger on the folder → Google Docs → Get → Code (same HTML conversion, converted automatically) → WordPress → Post → Create with status Draft.

Pitfalls

• Pagination. The REST API returns at most 100 items per page (per_page). Totals arrive in X-WP-Total and X-WP-TotalPages. Get All in the node handles paging; HTTP Request calls need Pagination options set.
• Security plugins (Wordfence and similar) sometimes block the REST API or Basic auth. If you get 401 with a correct password, check them.
• Featured images. Upload the media first (HTTP Request), then pass its ID as featured_media when creating the post.
• Categories and tags need IDs, not names. Pipedream's props usually already hold IDs; keep them.

How to move your WordPress workflows

1. Export the workflows from Pipedream.
2. Upload on /convert for the free report: steps, credentials, manual items.
3. Download the n8n JSON: 1 workflow is free; full export: $3 per workflow, $19 minimum — coming soon.

See the Pipedream to n8n guide and the code step checker. Related: LinkedIn, OpenAI, Google Docs.