Forms, users, posts, Woo
WPForms, Contact Form 7, Gravity Forms, Elementor, Fluent Forms, Ninja Forms, new users, published posts/pages, and WooCommerce orders.
Send WordPress forms, WooCommerce orders, users, posts, and chat to n8n with HMAC-signed JSON and delivery logs. Built by the same engineer who ships ZHBackup — not a 400-app Zap clone.
WPForms, Contact Form 7, Gravity Forms, Elementor, Fluent Forms, Ninja Forms, new users, published posts/pages, and WooCommerce orders.
X-ZH-N8N-Key for n8n Header Auth plus X-ZH-N8N-Signature over timestamp and raw body. Inbound ping route to prove the connection.
Visitor messages wait for {"reply":"..."} from a Respond to Webhook node. Colors, radius, offsets, theme, launcher, and avatar are in wp-admin.
Last 200 sends with event name and HTTP status. Payload kept only until success so retries work. No n8n Cloud lock-in.




Plugins → Add New, search ZH Webhooks for n8n, activate.
Use the n8n Production URL. Copy the shared secret into n8n Header Auth as X-ZH-N8N-Key.
Send a test ping. Turn on forms, Woo, users, or posts. Optional: style the chat widget or use [zh_n8n_chat].
That is the agency service: CRM mapping, AI scoring, Slack/WhatsApp, error handling. n8n WordPress automation.
No. Those connect hundreds of apps. This plugin only talks to n8n with a stable JSON envelope and HMAC.
An envelope with id, event, timestamp, site name/url/timezone, and a data object, plus headers for event, timestamp, signature, and key.
The widget POSTs to WordPress REST. WordPress forwards chat.message to n8n and waits. Your workflow must use Respond to Webhook with {"reply":"text"}. Other events are queued so checkout stays fast.
No. Order events fire only when WooCommerce is active.
Yes. That is the lead path: free plugin as proof, paid implementation and retainers for the n8n side. Send a brief below.
Install is free. Wiring n8n, CRM, AI, and chat replies is the paid work. Send the staging URL and what should happen after a form or order.
Share the brief, staging link, design file, or issue details. I will review the scope and reply with the next step.