Wordpress n8n integrationAutomate Wordpress with n8n.

This operation pushes a new article into Wordpress and returns its identifier, which the rest of the workflow reuses to log the URL or share the link elsewhere.

• Title: the only required field, often {{ $json.title }} coming from the step that wrote the article.
• Content: the body text, inside Additional Fields.
• Status: draft keeps it out of sight for review, publish sends it live, future waits for the Date you set.

Fetching a single article by its identifier gives the workflow the stored version: title, content, status, whatever the site holds right now.

• Post ID: the identifier of the article, usually carried over as {{ $json.id }} from a previous node.
• Context: view returns the public shape, edit adds the raw fields an editor sees, embed keeps a short preview.
• Password: required when the article is password protected.

Listing is where the archive turns into data the workflow can sort, count and compare.

• Return All: on, n8n walks every page of the Wordpress API until the archive is exhausted; off, Limit caps the batch.
• After and Before: ISO8601 dates that bracket the publication window.
• Search: a string matched against the articles, handy to pull everything mentioning a product name.
• Status: keep only draft items to see what is stuck in the pipeline.

Nothing goes live without a change of status, and that change is this operation. It edits an existing article in place, keeping its identifier and its URL.

• Post ID: the only required field, everything else sits in Update Fields.
• Status: moving from pending to publish is an entire approval step in one node.
• Tag Names or IDs: taxonomy terms, picked from the list or passed as identifiers through an expression.

Pages follow a different logic from articles: they sit in a hierarchy and in a menu, not in a chronological feed. This operation creates one and returns it.

• Title: required, the rest lives in Additional Fields.
• Parent ID: the identifier of the parent page, which is what nests a page under a section.
• Menu Order: the position of the page relative to the others.
• Featured Media ID: the identifier of a media item already in the library.

Reading one page returns exactly what Wordpress stores for it, which is the safest way to check a live page from inside a workflow.

• Page ID: the identifier of the page, required.
• Context: view for the rendered shape, edit when the workflow needs the raw fields before changing them, embed for a light preview.
• Password: for a page kept behind a password.

The page collection is usually small enough to walk whole, which makes this operation a good starting point for site-wide checks.

• Return All: on, every page comes back; off, Limit decides how many.
• Parent Page ID: keeps only the children of one section.
• Page: which page of the collection to read, the manual alternative when Return All is off.
• Order By: modified surfaces what changed most recently.

Editing a landing page from a workflow avoids the copy-paste round trip through the admin, and it happens at the same second everywhere.

• Page ID: required, the fields to change go into Update Fields.
• Content: the new body of the page.
• Slug: the identifier in the URL, unique for its type.
• Status: private pulls a page out of public view without deleting it.

Accounts carry the longest required list of the whole node: six fields must be filled or the execution stops.

• Username and Email: the login name and the address, both required.
• First Name, Last Name and Name: the last one is the display name shown on the site.
• Password: required, and never returned by the API afterwards.
• Description: the bio, in Additional Fields.

One account, one identifier, one lookup. This operation returns the profile behind an author reference found in an article.

• User ID: the identifier of the account, required, often {{ $json.author }} taken from a post returned earlier.
• Context: view gives the public profile, edit exposes the fields an administrator sees, embed a short version.

The account list answers a question editorial teams ask often: who actually writes here, and since when.

• Return All: on, the whole list comes back; off, Limit sets the ceiling.
• Who: set to authors, the result keeps only accounts considered authors.
• Order By: registered_date puts the newest accounts first, name sorts alphabetically.
• Search: matches a string against the accounts.

Profiles drift. Someone changes agency, a bio mentions a job title from two years ago, an address bounces.

• User ID: required, and the only field outside Update Fields.
• Email: the new address for the account.
• URL: the personal site shown on the profile.
• Nickname and Slug: the short name and the alphanumeric identifier of the account.