n8n and WordPress: How to Connect Them, and When You Don’t Need To

n8n is a general-purpose workflow automation platform that runs outside WordPress, on n8n Cloud or on your own server. Connecting it to a WordPress site comes down to two directions: n8n acting on WordPress, and WordPress telling n8n that something happened. This guide covers both, from n8n’s own documentation, and when a WordPress plugin can do the job without a separate platform. Facts about n8n were checked on 4 October 2026.

n8n acting on WordPress

n8n’s WordPress node creates, gets and updates posts, pages and users through the WordPress REST API. To connect it to a self-hosted site, n8n’s WordPress credentials use your WordPress username and an application password:

1. In WordPress, open your user profile and create an application password (WordPress has built them in since version 5.6). Give it a name such as “n8n”.
2. In n8n, create WordPress credentials with your username, that application password and your site’s URL.
3. Use the WordPress node in a workflow to create or update posts, pages or users.

For WooCommerce stores, n8n also has a WooCommerce Trigger node and a WooCommerce node, connected with WooCommerce REST API keys.

WordPress telling n8n what happened

The WordPress node does not start workflows. To start an n8n workflow when something happens on the site — a form is submitted, a user signs up, a course is completed — the site has to call n8n. n8n’s Webhook node gives a workflow a URL for exactly that, with separate test and production URLs.

The WordPress side needs something that sends the request at the right moment. With FlowWP, that is a workflow:

1. Choose the trigger for the event, for example A WPForms form is submitted or A user is created.
2. Add an HTTP Request step that POSTs to the n8n Webhook node’s production URL.
3. Put the data n8n needs in the body with tokens, such as {{ trigger.user.email | json }}.
4. Test it, activate it, and the event reaches n8n each time it happens on the site.

It works the other way too: an n8n workflow can start a FlowWP workflow by calling its webhook URL. See How to connect WordPress to an external API for both directions.

When you may not need n8n for WordPress work

If the automation starts and ends in WordPress — an order, a form, a membership, a course, a post — a plugin that runs inside the site can do it directly, with no separate service to run and no REST API credentials. FlowWP’s triggers listen to WordPress’ own hooks and its steps act on the site and its plugins, from WooCommerce and the form plugins to LearnDash and FluentCRM.

n8n fits when WordPress is one system among many: workflows that mostly connect SaaS apps, databases and internal tools, or teams who want code inside workflows and run automation as a central service. The two can also work together, each doing the part it is built for.

For a side-by-side look at architecture, building, extending and pricing, with sources, see FlowWP vs n8n.