NabuDesk Connector

Sends site events to your NabuDesk workspace:

• Posts (any public post type, including custom post types): created, updated, published, deleted
• WooCommerce products: created, updated, deleted
• WooCommerce orders: created, status changed
• Users: registered
• Comments: created

Beyond these built-in events you can build rules in the plugin (NabuDesk → Rules): bind any WordPress or plugin action/filter hook, add conditions (hook argument, post/user/term/comment meta, or — opt-in — a safe database existence/count check), and send a custom event to NabuDesk when they match.

Each site/brand uses its own token, issued in NabuDesk, and a token can be restricted to specific AI models and event types from the NabuDesk panel. Deliveries are spooled and retried with backoff, and a per-rule activity view shows what fired, what was skipped, and why.

External services

This plugin sends data from your site to a NabuDesk instance. It has no built-in destination and contacts nothing until you configure one: you enter the URL of your own NabuDesk installation, plus a token issued by that installation, under NabuDesk → Settings. Until both are set, the plugin makes no outbound requests at all.

Because the destination is a server you choose, the operator of that server — not this plugin — determines how the data is stored, retained and protected. If you are using a NabuDesk instance run by someone else, ask them for their terms and privacy policy before connecting a production site.

What is sent, and when. Only the event types you leave enabled are sent, and three of them include personal data — they are marked below so you can decide before you switch them on.

• Posts — ID, title, status, post type, permalink, author ID, modified time, and the first 55 words of the content as an excerpt.
• WooCommerce products — ID, name, SKU, price, regular and sale price, stock status and quantity, status, permalink and category names.
• WooCommerce orders (personal data) — ID, status, total, currency, payment method, customer ID, the billing email address, and each line item’s name, quantity and total.
• Comments (personal data) — ID, the post commented on, the author’s name, approval state, and the first 40 words of the comment. Comments marked as spam are not sent.
• User registration (personal data) — the new user’s ID, display name, email address and roles.
• On „Test connection“ and when settings are saved — your site URL, the WordPress and plugin versions, and an inventory of the post types, taxonomies and hooks the site has, so NabuDesk can offer them when you build rules. No content is included.
• With every request — an Authorization header carrying your site token, and a User-Agent string containing the plugin version and your site URL.

Nothing is sent on a schedule, and this plugin collects no analytics or usage data of its own. Passwords, password hashes and site options are never transmitted. The opt-in database conditions read only whether rows exist and how many, never their values.

Deactivating the plugin stops all outbound requests. Uninstalling additionally removes the plugin’s own settings, rules and queued deliveries from your database — it does not delete anything already received by the NabuDesk instance, which you must remove there.