M2Z Flow — Integration for n8n

M2Z Flow is a WordPress integration plugin for n8n that lets you send WordPress and WooCommerce events directly to your n8n workflows using secure webhooks.

Build WordPress automations without giving n8n administrator access to your WordPress website.

When something happens in WordPress — such as a post being published, a user registering, a comment being created, or a WooCommerce order changing status — M2Z Flow can send the event to an n8n webhook and trigger your automation workflow.

M2Z Flow works with both self-hosted n8n instances and n8n Cloud webhook endpoints.

There is no M2Z Flow cloud service between WordPress and your automation platform. Your website sends webhook requests directly to the HTTPS endpoint you configure.

Connect WordPress to n8n

M2Z Flow provides a simple event-based bridge between WordPress and n8n:

WordPress Event → M2Z Flow → Secure Webhook → n8n Workflow

Create a webhook in n8n, add its URL to M2Z Flow, select the WordPress events you want to monitor, and enable the endpoint.

When a selected event occurs, M2Z Flow prepares the event payload and queues it for background delivery to your n8n webhook.

From n8n, you can continue the workflow and connect WordPress events to other applications, APIs, databases, notification services, or your own internal systems.

WordPress Automation with n8n

M2Z Flow can be used as the trigger layer for many WordPress automation workflows.

For example, you can use M2Z Flow and n8n to:

• Start an n8n workflow when a WordPress post is published.
• Trigger automation when an existing post is updated.
• Process newly created WordPress categories.
• React when a category is updated.
• Start onboarding workflows when a new user registers.
• Process or route newly created comments.
• Trigger order processing workflows for new WooCommerce orders.
• Run automations when a WooCommerce order status changes.
• Send selected WordPress events to other systems through n8n.
• Build custom WordPress automation workflows without exposing WordPress administrator credentials.

What happens after the webhook reaches n8n is completely up to your workflow.

Supported WordPress and WooCommerce Events

M2Z Flow 1.0.0 includes eight event contracts.

WordPress Posts

• post.published — Triggered when a post is published.
• post.updated — Triggered when a supported post is updated.

WordPress Categories

• category.created — Triggered when a category is created.
• category.updated — Triggered when a category is updated.

WordPress Users

• user.registered — Triggered when a new WordPress user is registered.

WordPress Comments

• comment.created — Triggered when a new comment is created.

WooCommerce Orders

• order.created — Triggered when a WooCommerce order is created.
• order.status_changed — Triggered when the status of a WooCommerce order changes.

Each webhook endpoint can be configured independently, allowing different events to trigger different n8n workflows.

Multiple n8n Webhooks

You are not limited to a single n8n webhook.

M2Z Flow lets you create multiple independently configured webhook endpoints.

For example, you might configure:

• One n8n workflow for WordPress content events.
• Another workflow for new users.
• A separate workflow for comments.
• A dedicated WooCommerce order workflow.

Each endpoint can have its own:

• Webhook URL.
• Shared secret.
• Selected events.
• Optional payload fields.
• Enabled or disabled state.

This makes it possible to separate automations instead of routing every WordPress event through one large workflow.

Secure Webhook Delivery

Webhook requests can contain important website or WooCommerce data, so M2Z Flow includes HMAC-SHA256 request signing.

Each endpoint has a shared secret that can be used to verify webhook authenticity on the receiving side.

Your n8n workflow can validate the signature before processing the event.

This helps ensure that incoming webhook requests were generated using the secret configured for your M2Z Flow endpoint.

Asynchronous Webhook Delivery

M2Z Flow does not need to wait for your n8n workflow to finish while a visitor or administrator is using WordPress.

Webhook deliveries are processed in the background using the bundled Action Scheduler.

This separates webhook processing from the original WordPress request and helps prevent slow external endpoints from unnecessarily delaying normal WordPress operations.

Automatic Retries

Temporary failures happen.

Your n8n server may be restarting, a network connection may fail, or an endpoint may temporarily return an error.

M2Z Flow includes bounded retry handling for webhook deliveries.

This provides more reliable delivery than relying on a single synchronous HTTP request.

Because delivery follows an at-least-once model, workflows that perform important actions should use the included event_id to implement idempotent processing.

Delivery History and Debugging

M2Z Flow keeps delivery history so administrators can inspect webhook activity.

This can help when developing or debugging an n8n workflow.

Instead of guessing whether WordPress sent an event, you can use the delivery information provided by M2Z Flow to investigate webhook processing.

Test Your n8n Webhook

You do not need to publish a real post or create a real WooCommerce order just to check your connection.

M2Z Flow includes test events that can be sent to a configured webhook endpoint.

This makes it easier to:

• Test an n8n Webhook node.
• Inspect the incoming payload.
• Configure downstream n8n nodes.
• Test HMAC signature verification.
• Confirm connectivity before enabling real event delivery.

Privacy-First Payload Controls

M2Z Flow is designed to avoid sending optional personal information unless you explicitly choose to include it.

Optional personal fields such as email, phone, address, and other personal data are disabled by default and can be controlled per endpoint.

This allows administrators to decide what information is required by each automation.

Only enable personal fields when they are necessary for your workflow and make sure your use of that data complies with applicable privacy requirements.

Direct WordPress to n8n Integration

M2Z Flow does not require an M2Z Flow account or an intermediary M2Z Flow cloud service.

Webhook delivery follows this path:

Your WordPress Website → Your Configured Webhook Endpoint

The destination can be:

• A self-hosted n8n instance.
• An n8n Cloud webhook.
• Another compatible HTTPS webhook endpoint.

M2Z Flow itself does not provide telemetry, a license server, or automatic external communication.

Installing or activating the plugin alone does not send your website data to an external service.

WooCommerce and n8n Automation

If you use WooCommerce, M2Z Flow can trigger n8n workflows for order-related events.

The current version supports:

• New WooCommerce orders.
• WooCommerce order status changes.

These events can be used as the starting point for workflows such as order processing, internal notifications, synchronization, reporting, or other business automation handled by your n8n workflow.

Why Use M2Z Flow?

M2Z Flow focuses specifically on reliable event delivery between WordPress and automation workflows.

Key features include:

• Native WordPress and WooCommerce event triggers.
• Integration with n8n webhooks.
• Support for self-hosted n8n and n8n Cloud.
• Multiple independently configured webhook endpoints.
• Background webhook processing.
• HMAC-SHA256 request signing.
• Automatic bounded retries.
• Delivery history.
• Immediate test events.
• Privacy-first optional payload fields.
• No M2Z Flow cloud account required.
• No telemetry.
• No license server.
• No WordPress administrator credentials required by n8n for event delivery.

Example Workflow

A simple WordPress automation might look like:

WordPress User Registration
→ M2Z Flow
→ n8n Webhook
→ Your Automation

Another example:

WooCommerce Order Created
→ M2Z Flow
→ n8n Webhook
→ Your Order Processing Workflow

Or:

WordPress Post Published
→ M2Z Flow
→ n8n Webhook
→ Your Content Automation Workflow

M2Z Flow handles the WordPress event and webhook delivery. n8n handles the automation that follows.

Built for n8n Users

M2Z Flow is designed for WordPress administrators, developers, agencies, store owners, and automation builders who use n8n.

Whether your n8n instance runs on your own server or you use n8n Cloud, M2Z Flow provides a dedicated way to turn WordPress activity into n8n workflow triggers.

Privacy

M2Z Flow sends event data only to webhook URLs explicitly configured by a WordPress administrator.

The exact data sent depends on the selected event and optional payload field configuration.

Optional personal fields are disabled by default.

The operator of the configured webhook destination is responsible for its own terms, privacy policy, data handling, and security practices.

M2Z Flow itself does not operate an intermediary cloud service, telemetry service, or license server.