{"id":354354,"date":"2026-08-16T08:29:48","date_gmt":"2026-08-16T08:29:48","guid":{"rendered":"https:\/\/wordpress.org\/plugins\/m2z-flow-integration-for-n8n\/"},"modified":"2026-08-17T21:22:44","modified_gmt":"2026-08-17T21:22:44","slug":"m2z-flow","status":"publish","type":"plugin","link":"https:\/\/sw.wordpress.org\/plugins\/m2z-flow\/","author":23195899,"comment_status":"closed","ping_status":"closed","template":"","meta":{"version":"1.0.1","stable_tag":"1.0.1","tested":"7.0.4","requires":"6.5","requires_php":"8.0","requires_plugins":null,"header_name":"M2Z Flow \u2014 Integration for n8n","header_author":"","header_description":"Connect WordPress and WooCommerce to n8n through secure, reliable webhooks.","assets_banners_color":"141237","last_updated":"2026-08-17 21:22:44","external_support_url":"","external_repository_url":"","donate_link":"","header_plugin_uri":"","header_author_uri":"","rating":0,"author_block_rating":0,"active_installs":0,"downloads":104,"num_ratings":0,"support_threads":0,"support_threads_resolved":0,"author_block_count":0,"sections":["description","installation","faq","changelog"],"tags":{"1.0.0":{"tag":"1.0.0","author":"mrazari","date":"2026-08-16 08:29:16"},"1.0.1":{"tag":"1.0.1","author":"mrazari","date":"2026-08-17 21:22:44"}},"upgrade_notice":[],"ratings":[],"assets_icons":{"icon-128x128.png":{"filename":"icon-128x128.png","revision":3651721,"resolution":"128x128","location":"assets","locale":"","width":128,"height":128},"icon-256x256.png":{"filename":"icon-256x256.png","revision":3651721,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256}},"assets_banners":{"banner-1544x500.png":{"filename":"banner-1544x500.png","revision":3651721,"resolution":"1544x500","location":"assets","locale":"","width":1544,"height":500},"banner-772x250.png":{"filename":"banner-772x250.png","revision":3651721,"resolution":"772x250","location":"assets","locale":"","width":772,"height":250}},"assets_blueprints":{},"all_blocks":[],"tagged_versions":["1.0.0","1.0.1"],"block_files":[],"assets_screenshots":[],"screenshots":{"1":"M2Z Flow webhook management screen.","2":"Creating and configuring an n8n webhook endpoint.","3":"Selecting WordPress and WooCommerce events for an endpoint.","4":"Configuring webhook security and optional payload fields.","5":"Sending a test event to an n8n workflow.","6":"M2Z Flow webhook delivery history and debugging information.","7":"Receiving a WordPress event inside an n8n workflow."}},"plugin_section":[],"plugin_tags":[569,597,243637,15439,286],"plugin_category":[45],"plugin_contributors":[275942],"plugin_business_model":[],"class_list":["post-354354","plugin","type-plugin","status-publish","hentry","plugin_tags-automation","plugin_tags-integration","plugin_tags-n8n","plugin_tags-webhook","plugin_tags-woocommerce","plugin_category-ecommerce","plugin_contributors-mrazari","plugin_committers-mrazari"],"banners":{"banner":"https:\/\/ps.w.org\/m2z-flow\/assets\/banner-772x250.png?rev=3651721","banner_2x":"https:\/\/ps.w.org\/m2z-flow\/assets\/banner-1544x500.png?rev=3651721","banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":false,"icon":"https:\/\/ps.w.org\/m2z-flow\/assets\/icon-128x128.png?rev=3651721","icon_2x":"https:\/\/ps.w.org\/m2z-flow\/assets\/icon-256x256.png?rev=3651721","generated":false},"screenshots":[],"raw_content":"<!--section=description-->\n<p>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.<\/p>\n\n<p>Build WordPress automations without giving n8n administrator access to your WordPress website.<\/p>\n\n<p>When something happens in WordPress \u2014 such as a post being published, a user registering, a comment being created, or a WooCommerce order changing status \u2014 M2Z Flow can send the event to an n8n webhook and trigger your automation workflow.<\/p>\n\n<p>M2Z Flow works with both self-hosted n8n instances and n8n Cloud webhook endpoints.<\/p>\n\n<p>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.<\/p>\n\n<h4>Connect WordPress to n8n<\/h4>\n\n<p>M2Z Flow provides a simple event-based bridge between WordPress and n8n:<\/p>\n\n<p>WordPress Event \u2192 M2Z Flow \u2192 Secure Webhook \u2192 n8n Workflow<\/p>\n\n<p>Create a webhook in n8n, add its URL to M2Z Flow, select the WordPress events you want to monitor, and enable the endpoint.<\/p>\n\n<p>When a selected event occurs, M2Z Flow prepares the event payload and queues it for background delivery to your n8n webhook.<\/p>\n\n<p>From n8n, you can continue the workflow and connect WordPress events to other applications, APIs, databases, notification services, or your own internal systems.<\/p>\n\n<h4>WordPress Automation with n8n<\/h4>\n\n<p>M2Z Flow can be used as the trigger layer for many WordPress automation workflows.<\/p>\n\n<p>For example, you can use M2Z Flow and n8n to:<\/p>\n\n<ul>\n<li>Start an n8n workflow when a WordPress post is published.<\/li>\n<li>Trigger automation when an existing post is updated.<\/li>\n<li>Process newly created WordPress categories.<\/li>\n<li>React when a category is updated.<\/li>\n<li>Start onboarding workflows when a new user registers.<\/li>\n<li>Process or route newly created comments.<\/li>\n<li>Trigger order processing workflows for new WooCommerce orders.<\/li>\n<li>Run automations when a WooCommerce order status changes.<\/li>\n<li>Send selected WordPress events to other systems through n8n.<\/li>\n<li>Build custom WordPress automation workflows without exposing WordPress administrator credentials.<\/li>\n<\/ul>\n\n<p>What happens after the webhook reaches n8n is completely up to your workflow.<\/p>\n\n<h4>Supported WordPress and WooCommerce Events<\/h4>\n\n<p>M2Z Flow 1.0.0 includes eight event contracts.<\/p>\n\n<p><strong>WordPress Posts<\/strong><\/p>\n\n<ul>\n<li><code>post.published<\/code> \u2014 Triggered when a post is published.<\/li>\n<li><code>post.updated<\/code> \u2014 Triggered when a supported post is updated.<\/li>\n<\/ul>\n\n<p><strong>WordPress Categories<\/strong><\/p>\n\n<ul>\n<li><code>category.created<\/code> \u2014 Triggered when a category is created.<\/li>\n<li><code>category.updated<\/code> \u2014 Triggered when a category is updated.<\/li>\n<\/ul>\n\n<p><strong>WordPress Users<\/strong><\/p>\n\n<ul>\n<li><code>user.registered<\/code> \u2014 Triggered when a new WordPress user is registered.<\/li>\n<\/ul>\n\n<p><strong>WordPress Comments<\/strong><\/p>\n\n<ul>\n<li><code>comment.created<\/code> \u2014 Triggered when a new comment is created.<\/li>\n<\/ul>\n\n<p><strong>WooCommerce Orders<\/strong><\/p>\n\n<ul>\n<li><code>order.created<\/code> \u2014 Triggered when a WooCommerce order is created.<\/li>\n<li><code>order.status_changed<\/code> \u2014 Triggered when the status of a WooCommerce order changes.<\/li>\n<\/ul>\n\n<p>Each webhook endpoint can be configured independently, allowing different events to trigger different n8n workflows.<\/p>\n\n<h4>Multiple n8n Webhooks<\/h4>\n\n<p>You are not limited to a single n8n webhook.<\/p>\n\n<p>M2Z Flow lets you create multiple independently configured webhook endpoints.<\/p>\n\n<p>For example, you might configure:<\/p>\n\n<ul>\n<li>One n8n workflow for WordPress content events.<\/li>\n<li>Another workflow for new users.<\/li>\n<li>A separate workflow for comments.<\/li>\n<li>A dedicated WooCommerce order workflow.<\/li>\n<\/ul>\n\n<p>Each endpoint can have its own:<\/p>\n\n<ul>\n<li>Webhook URL.<\/li>\n<li>Shared secret.<\/li>\n<li>Selected events.<\/li>\n<li>Optional payload fields.<\/li>\n<li>Enabled or disabled state.<\/li>\n<\/ul>\n\n<p>This makes it possible to separate automations instead of routing every WordPress event through one large workflow.<\/p>\n\n<h4>Secure Webhook Delivery<\/h4>\n\n<p>Webhook requests can contain important website or WooCommerce data, so M2Z Flow includes HMAC-SHA256 request signing.<\/p>\n\n<p>Each endpoint has a shared secret that can be used to verify webhook authenticity on the receiving side.<\/p>\n\n<p>Your n8n workflow can validate the signature before processing the event.<\/p>\n\n<p>This helps ensure that incoming webhook requests were generated using the secret configured for your M2Z Flow endpoint.<\/p>\n\n<h4>Asynchronous Webhook Delivery<\/h4>\n\n<p>M2Z Flow does not need to wait for your n8n workflow to finish while a visitor or administrator is using WordPress.<\/p>\n\n<p>Webhook deliveries are processed in the background using the bundled Action Scheduler.<\/p>\n\n<p>This separates webhook processing from the original WordPress request and helps prevent slow external endpoints from unnecessarily delaying normal WordPress operations.<\/p>\n\n<h4>Automatic Retries<\/h4>\n\n<p>Temporary failures happen.<\/p>\n\n<p>Your n8n server may be restarting, a network connection may fail, or an endpoint may temporarily return an error.<\/p>\n\n<p>M2Z Flow includes bounded retry handling for webhook deliveries.<\/p>\n\n<p>This provides more reliable delivery than relying on a single synchronous HTTP request.<\/p>\n\n<p>Because delivery follows an at-least-once model, workflows that perform important actions should use the included <code>event_id<\/code> to implement idempotent processing.<\/p>\n\n<h4>Delivery History and Debugging<\/h4>\n\n<p>M2Z Flow keeps delivery history so administrators can inspect webhook activity.<\/p>\n\n<p>This can help when developing or debugging an n8n workflow.<\/p>\n\n<p>Instead of guessing whether WordPress sent an event, you can use the delivery information provided by M2Z Flow to investigate webhook processing.<\/p>\n\n<h4>Test Your n8n Webhook<\/h4>\n\n<p>You do not need to publish a real post or create a real WooCommerce order just to check your connection.<\/p>\n\n<p>M2Z Flow includes test events that can be sent to a configured webhook endpoint.<\/p>\n\n<p>This makes it easier to:<\/p>\n\n<ul>\n<li>Test an n8n Webhook node.<\/li>\n<li>Inspect the incoming payload.<\/li>\n<li>Configure downstream n8n nodes.<\/li>\n<li>Test HMAC signature verification.<\/li>\n<li>Confirm connectivity before enabling real event delivery.<\/li>\n<\/ul>\n\n<h4>Privacy-First Payload Controls<\/h4>\n\n<p>M2Z Flow is designed to avoid sending optional personal information unless you explicitly choose to include it.<\/p>\n\n<p>Optional personal fields such as email, phone, address, and other personal data are disabled by default and can be controlled per endpoint.<\/p>\n\n<p>This allows administrators to decide what information is required by each automation.<\/p>\n\n<p>Only enable personal fields when they are necessary for your workflow and make sure your use of that data complies with applicable privacy requirements.<\/p>\n\n<h4>Direct WordPress to n8n Integration<\/h4>\n\n<p>M2Z Flow does not require an M2Z Flow account or an intermediary M2Z Flow cloud service.<\/p>\n\n<p>Webhook delivery follows this path:<\/p>\n\n<p>Your WordPress Website \u2192 Your Configured Webhook Endpoint<\/p>\n\n<p>The destination can be:<\/p>\n\n<ul>\n<li>A self-hosted n8n instance.<\/li>\n<li>An n8n Cloud webhook.<\/li>\n<li>Another compatible HTTPS webhook endpoint.<\/li>\n<\/ul>\n\n<p>M2Z Flow itself does not provide telemetry, a license server, or automatic external communication.<\/p>\n\n<p>Installing or activating the plugin alone does not send your website data to an external service.<\/p>\n\n<h4>WooCommerce and n8n Automation<\/h4>\n\n<p>If you use WooCommerce, M2Z Flow can trigger n8n workflows for order-related events.<\/p>\n\n<p>The current version supports:<\/p>\n\n<ul>\n<li>New WooCommerce orders.<\/li>\n<li>WooCommerce order status changes.<\/li>\n<\/ul>\n\n<p>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.<\/p>\n\n<h4>Why Use M2Z Flow?<\/h4>\n\n<p>M2Z Flow focuses specifically on reliable event delivery between WordPress and automation workflows.<\/p>\n\n<p>Key features include:<\/p>\n\n<ul>\n<li>Native WordPress and WooCommerce event triggers.<\/li>\n<li>Integration with n8n webhooks.<\/li>\n<li>Support for self-hosted n8n and n8n Cloud.<\/li>\n<li>Multiple independently configured webhook endpoints.<\/li>\n<li>Background webhook processing.<\/li>\n<li>HMAC-SHA256 request signing.<\/li>\n<li>Automatic bounded retries.<\/li>\n<li>Delivery history.<\/li>\n<li>Immediate test events.<\/li>\n<li>Privacy-first optional payload fields.<\/li>\n<li>No M2Z Flow cloud account required.<\/li>\n<li>No telemetry.<\/li>\n<li>No license server.<\/li>\n<li>No WordPress administrator credentials required by n8n for event delivery.<\/li>\n<\/ul>\n\n<h4>Example Workflow<\/h4>\n\n<p>A simple WordPress automation might look like:<\/p>\n\n<p>WordPress User Registration\n\u2192 M2Z Flow\n\u2192 n8n Webhook\n\u2192 Your Automation<\/p>\n\n<p>Another example:<\/p>\n\n<p>WooCommerce Order Created\n\u2192 M2Z Flow\n\u2192 n8n Webhook\n\u2192 Your Order Processing Workflow<\/p>\n\n<p>Or:<\/p>\n\n<p>WordPress Post Published\n\u2192 M2Z Flow\n\u2192 n8n Webhook\n\u2192 Your Content Automation Workflow<\/p>\n\n<p>M2Z Flow handles the WordPress event and webhook delivery. n8n handles the automation that follows.<\/p>\n\n<h4>Built for n8n Users<\/h4>\n\n<p>M2Z Flow is designed for WordPress administrators, developers, agencies, store owners, and automation builders who use n8n.<\/p>\n\n<p>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.<\/p>\n\n<h3>Privacy<\/h3>\n\n<p>M2Z Flow sends event data only to webhook URLs explicitly configured by a WordPress administrator.<\/p>\n\n<p>The exact data sent depends on the selected event and optional payload field configuration.<\/p>\n\n<p>Optional personal fields are disabled by default.<\/p>\n\n<p>The operator of the configured webhook destination is responsible for its own terms, privacy policy, data handling, and security practices.<\/p>\n\n<p>M2Z Flow itself does not operate an intermediary cloud service, telemetry service, or license server.<\/p>\n\n<!--section=installation-->\n<h4>Install from WordPress<\/h4>\n\n<ol>\n<li>Open your WordPress dashboard.<\/li>\n<li>Go to Plugins &gt; Add New.<\/li>\n<li>Search for \"M2Z Flow\".<\/li>\n<li>Install M2Z Flow.<\/li>\n<li>Activate the plugin.<\/li>\n<\/ol>\n\n<h4>Connect M2Z Flow to n8n<\/h4>\n\n<ol>\n<li>Create a Webhook node in your n8n workflow.<\/li>\n<li>Copy the HTTPS webhook URL.<\/li>\n<li>In WordPress, open M2Z Flow &gt; Webhooks.<\/li>\n<li>Add a new webhook endpoint.<\/li>\n<li>Paste your n8n webhook URL.<\/li>\n<li>Enter a shared secret.<\/li>\n<li>Select the WordPress or WooCommerce events you want to send.<\/li>\n<li>Select any optional fields required by your workflow.<\/li>\n<li>Save the endpoint.<\/li>\n<li>Send a test event.<\/li>\n<li>Confirm that the event reaches your n8n workflow.<\/li>\n<li>Enable the endpoint for real event delivery.<\/li>\n<\/ol>\n\n<p>For production workflows, use the production webhook URL provided by n8n rather than its temporary test URL.<\/p>\n\n<!--section=faq-->\n<dl>\n<dt id=\"what%20is%20m2z%20flow%3F\"><h3>What is M2Z Flow?<\/h3><\/dt>\n<dd><p>M2Z Flow is a WordPress integration plugin that sends selected WordPress and WooCommerce events to n8n or another compatible HTTPS webhook endpoint.<\/p>\n\n<p>It can be used to trigger n8n automation workflows when events occur on your WordPress website.<\/p><\/dd>\n<dt id=\"does%20m2z%20flow%20require%20n8n%3F\"><h3>Does M2Z Flow require n8n?<\/h3><\/dt>\n<dd><p>M2Z Flow is designed primarily for n8n, but the destination is a standard compatible HTTPS webhook endpoint.<\/p>\n\n<p>You can therefore use another system capable of receiving the webhook requests if required.<\/p><\/dd>\n<dt id=\"does%20m2z%20flow%20work%20with%20self-hosted%20n8n%3F\"><h3>Does M2Z Flow work with self-hosted n8n?<\/h3><\/dt>\n<dd><p>Yes. You can configure an HTTPS webhook URL from your self-hosted n8n instance.<\/p>\n\n<p>The n8n webhook must be reachable from your WordPress server.<\/p><\/dd>\n<dt id=\"does%20m2z%20flow%20work%20with%20n8n%20cloud%3F\"><h3>Does M2Z Flow work with n8n Cloud?<\/h3><\/dt>\n<dd><p>Yes. You can use an HTTPS webhook endpoint provided by n8n Cloud.<\/p><\/dd>\n<dt id=\"how%20do%20i%20connect%20wordpress%20to%20n8n%3F\"><h3>How do I connect WordPress to n8n?<\/h3><\/dt>\n<dd><p>Create a Webhook node in n8n, copy its webhook URL, and add that URL as an endpoint in M2Z Flow.<\/p>\n\n<p>Then select the WordPress events you want to use as workflow triggers.<\/p><\/dd>\n<dt id=\"do%20i%20need%20to%20give%20n8n%20my%20wordpress%20administrator%20username%20and%20password%3F\"><h3>Do I need to give n8n my WordPress administrator username and password?<\/h3><\/dt>\n<dd><p>No.<\/p>\n\n<p>M2Z Flow sends selected events from WordPress to your configured webhook endpoint. Event delivery does not require giving n8n your WordPress administrator credentials.<\/p><\/dd>\n<dt id=\"which%20wordpress%20events%20are%20supported%3F\"><h3>Which WordPress events are supported?<\/h3><\/dt>\n<dd><p>Version 1.0.0 supports:<\/p>\n\n<ul>\n<li>Post published.<\/li>\n<li>Post updated.<\/li>\n<li>Category created.<\/li>\n<li>Category updated.<\/li>\n<li>User registered.<\/li>\n<li>Comment created.<\/li>\n<li>WooCommerce order created.<\/li>\n<li>WooCommerce order status changed.<\/li>\n<\/ul><\/dd>\n<dt id=\"can%20i%20configure%20multiple%20n8n%20webhooks%3F\"><h3>Can I configure multiple n8n webhooks?<\/h3><\/dt>\n<dd><p>Yes.<\/p>\n\n<p>M2Z Flow supports multiple independently configured webhook endpoints. Each endpoint can use its own URL, secret, selected events, optional fields, and enabled state.<\/p><\/dd>\n<dt id=\"are%20webhook%20requests%20secure%3F\"><h3>Are webhook requests secure?<\/h3><\/dt>\n<dd><p>M2Z Flow supports HMAC-SHA256 signing using the shared secret configured for an endpoint.<\/p>\n\n<p>The receiving workflow can use the signature to verify incoming webhook requests.<\/p>\n\n<p>Always use HTTPS webhook URLs.<\/p><\/dd>\n<dt id=\"are%20webhooks%20sent%20asynchronously%3F\"><h3>Are webhooks sent asynchronously?<\/h3><\/dt>\n<dd><p>Yes.<\/p>\n\n<p>M2Z Flow uses the bundled Action Scheduler for background webhook delivery.<\/p><\/dd>\n<dt id=\"what%20happens%20if%20my%20n8n%20instance%20is%20temporarily%20unavailable%3F\"><h3>What happens if my n8n instance is temporarily unavailable?<\/h3><\/dt>\n<dd><p>M2Z Flow includes bounded retry handling for failed webhook deliveries.<\/p>\n\n<p>You can also inspect delivery history when troubleshooting webhook issues.<\/p><\/dd>\n<dt id=\"can%20the%20same%20event%20be%20delivered%20more%20than%20once%3F\"><h3>Can the same event be delivered more than once?<\/h3><\/dt>\n<dd><p>Yes.<\/p>\n\n<p>Delivery follows an at-least-once model. For workflows where duplicate processing could cause problems, store or check the included <code>event_id<\/code> and make your n8n workflow idempotent.<\/p><\/dd>\n<dt id=\"can%20i%20test%20a%20webhook%20before%20enabling%20it%3F\"><h3>Can I test a webhook before enabling it?<\/h3><\/dt>\n<dd><p>Yes.<\/p>\n\n<p>M2Z Flow includes immediate test events so you can verify your webhook URL, inspect payloads, and configure your n8n workflow before processing real events.<\/p><\/dd>\n<dt id=\"is%20personal%20data%20sent%20by%20default%3F\"><h3>Is personal data sent by default?<\/h3><\/dt>\n<dd><p>Optional personal fields such as email, phone, address, and other personal information are excluded unless a WordPress administrator explicitly enables them for an endpoint.<\/p><\/dd>\n<dt id=\"does%20m2z%20flow%20send%20data%20to%20its%20own%20servers%3F\"><h3>Does M2Z Flow send data to its own servers?<\/h3><\/dt>\n<dd><p>No.<\/p>\n\n<p>M2Z Flow does not provide an intermediary cloud service.<\/p>\n\n<p>Event data is sent directly from your WordPress website to the webhook URL configured by the administrator.<\/p><\/dd>\n<dt id=\"does%20m2z%20flow%20include%20telemetry%3F\"><h3>Does M2Z Flow include telemetry?<\/h3><\/dt>\n<dd><p>No.<\/p>\n\n<p>M2Z Flow does not include telemetry, a license server, or automatic external communication.<\/p><\/dd>\n<dt id=\"does%20installing%20the%20plugin%20automatically%20send%20data%20somewhere%3F\"><h3>Does installing the plugin automatically send data somewhere?<\/h3><\/dt>\n<dd><p>No.<\/p>\n\n<p>Installing or activating M2Z Flow does not itself cause your website to send event data to an external service.<\/p>\n\n<p>External requests occur when you configure webhook endpoints and selected events are delivered.<\/p><\/dd>\n<dt id=\"can%20i%20use%20m2z%20flow%20with%20woocommerce%3F\"><h3>Can I use M2Z Flow with WooCommerce?<\/h3><\/dt>\n<dd><p>Yes.<\/p>\n\n<p>Version 1.0.0 supports WooCommerce order creation and order status change events.<\/p><\/dd>\n<dt id=\"why%20are%20webhooks%20processed%20in%20the%20background%3F\"><h3>Why are webhooks processed in the background?<\/h3><\/dt>\n<dd><p>Background delivery prevents the original WordPress request from having to wait for the external webhook endpoint to complete.<\/p>\n\n<p>This is particularly useful when an n8n workflow or network connection takes longer to respond.<\/p><\/dd>\n<dt id=\"what%20happens%20when%20i%20uninstall%20m2z%20flow%3F\"><h3>What happens when I uninstall M2Z Flow?<\/h3><\/dt>\n<dd><p>Plugin data is preserved by default.<\/p>\n\n<p>If you want M2Z Flow to permanently remove its tables and options during uninstall, enable permanent deletion in M2Z Flow &gt; Settings before uninstalling the plugin.<\/p><\/dd>\n\n<\/dl>\n\n<!--section=changelog-->\n<h4>1.0.1<\/h4>\n\n<ul>\n<li>Fixed webhook configuration tabs not switching correctly.<\/li>\n<li>Fixed keyboard navigation and direct links for webhook configuration tabs.<\/li>\n<\/ul>\n\n<h4>1.0.0<\/h4>\n\n<ul>\n<li>Initial release with eight event contracts, multiple webhooks, asynchronous HMAC-signed delivery, retries, delivery logs, immediate test events, stalled-queue recovery, privacy controls, accessible configuration tabs, payload previews, and site-timezone display.<\/li>\n<\/ul>","raw_excerpt":"Connect WordPress and WooCommerce to n8n with secure webhooks, background delivery, HMAC signatures, retries, logs, and privacy controls.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/sw.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/354354","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/sw.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/sw.wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/sw.wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=354354"}],"author":[{"embeddable":true,"href":"https:\/\/sw.wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/mrazari"}],"wp:attachment":[{"href":"https:\/\/sw.wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=354354"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/sw.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=354354"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/sw.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=354354"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/sw.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=354354"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/sw.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=354354"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/sw.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=354354"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}