| 开发者 | zainhassandeveloper |
|---|---|
| 更新时间 | 2026年9月2日 20:20 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
{"reply":"..."} response from a Respond to Webhook node (the commercial “WordPress AI chatbot” use case). Brand colors, radius, offsets, theme, launcher, and avatar are configurable in wp-admin.X-ZH-N8N-Key for n8n Header Auth, plus X-ZH-N8N-Signature (sha256=HMAC(timestamp + "." + raw body)).zh-webhooks-for-n8n folder to /wp-content/plugins/.X-ZH-N8N-Key).[zh_n8n_chat].No. Those are generic “connect 400 apps” products. This plugin only talks to n8n with a stable JSON envelope and HMAC.
No. WordPress.org plugins cannot be an ad network. Monetize by booking implementation work or a later Pro license.
{ "id", "event", "timestamp", "site": { "name", "url", "timezone" }, "data": { ... } } plus headers X-ZH-N8N-Event, X-ZH-N8N-Timestamp, X-ZH-N8N-Signature, X-ZH-N8N-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 asynchronously so checkout stays fast.
The webhook URL is empty, not HTTPS, or not reachable from the server. http://127.0.0.1 on your laptop is not reachable from Hostinger. Use n8n Cloud or another public HTTPS webhook.
No. Order events fire only when WooCommerce is active.