Title: NabuDesk Connector
Author: nabuxai
Published: <strong>August 8, 2026</strong>
Last modified: August 8, 2026

---

Search plugins

![](https://s.w.org/plugins/geopattern-icon/nabudesk-connector.svg)

# NabuDesk Connector

 By [nabuxai](https://profiles.wordpress.org/nabuxai/)

[Download](https://downloads.wordpress.org/plugin/nabudesk-connector.1.0.0.zip)

 * [Details](https://wordpress.org/plugins/nabudesk-connector/#description)
 * [Reviews](https://wordpress.org/plugins/nabudesk-connector/#reviews)
 *  [Installation](https://wordpress.org/plugins/nabudesk-connector/#installation)
 * [Development](https://wordpress.org/plugins/nabudesk-connector/#developers)

 [Support](https://wordpress.org/support/plugin/nabudesk-connector/)

## Description

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.

## Installation

 1. Upload the `nabudesk-connector` folder to `/wp-content/plugins/`.
 2. Activate the plugin.
 3. In NabuDesk, open Channels  WordPress for your business and generate a site token.
 4. In WordPress, open the top-level **NabuDesk** menu  Settings, enter your NabuDesk
    URL and the token, then use “Test connection”.

## FAQ

### Where do I get the token?

In NabuDesk, open Channels  WordPress for your business and generate a site
 token.
Each site or brand should use its own token so you can revoke or scope them independently.

### Does sending events slow down my site?

No. Events are queued during the request and delivered after the response, with

automatic retry and backoff. A failed delivery is retried and, if it keeps failing,
surfaced in the admin rather than lost silently.

### What are “rules”?

A rule binds any hook on your site to conditions and sends a custom event to
 NabuDesk
when they match — for example “when a WooCommerce order reaches completed, send `
order.completed`“. Build them under NabuDesk  Rules.

### What are database conditions and are they safe?

Off by default. When enabled, a rule can test row existence or count against
 non-
sensitive tables. User, options, and any password/secret/meta tables are always 
blocked, only existence/count is read (never values), and all queries use prepared
statements with a live-schema allowlist.

### Why did my rule stop firing?

Open NabuDesk  Rules — each rule shows its last fired time, fire count, and the

last skip reason (conditions not met, de-duplicated, rate-capped, or an error).

## Reviews

There are no reviews for this plugin.

## Contributors & Developers

“NabuDesk Connector” is open source software. The following people have contributed
to this plugin.

Contributors

 *   [ nabuxai ](https://profiles.wordpress.org/nabuxai/)

[Translate “NabuDesk Connector” into your language.](https://translate.wordpress.org/projects/wp-plugins/nabudesk-connector)

### Interested in development?

[Browse the code](https://plugins.trac.wordpress.org/browser/nabudesk-connector/),
check out the [SVN repository](https://plugins.svn.wordpress.org/nabudesk-connector/),
or subscribe to the [development log](https://plugins.trac.wordpress.org/log/nabudesk-connector/)
by [RSS](https://plugins.trac.wordpress.org/log/nabudesk-connector/?limit=100&mode=stop_on_copy&format=rss).

## Changelog

#### 1.0.0

 * Initial release: event forwarding, discovery, a hook rule engine with safe
    database
   conditions, spooled delivery with retry, and per-rule telemetry.

## Meta

 *  Version **1.0.0**
 *  Last updated **9 hours ago**
 *  Active installations **Fewer than 10**
 *  WordPress version ** 5.6 or higher **
 *  Tested up to **7.0.3**
 *  PHP version ** 7.4 or higher **
 * Tags
 * [events](https://wordpress.org/plugins/tags/events/)[helpdesk](https://wordpress.org/plugins/tags/helpdesk/)
   [integration](https://wordpress.org/plugins/tags/integration/)[webhooks](https://wordpress.org/plugins/tags/webhooks/)
   [woocommerce](https://wordpress.org/plugins/tags/woocommerce/)
 *  [Advanced View](https://wordpress.org/plugins/nabudesk-connector/advanced/)

## Ratings

No reviews have been submitted yet.

[Your review](https://wordpress.org/support/plugin/nabudesk-connector/reviews/#new-post)

[See all reviews](https://wordpress.org/support/plugin/nabudesk-connector/reviews/)

## Contributors

 *   [ nabuxai ](https://profiles.wordpress.org/nabuxai/)

## Support

Got something to say? Need help?

 [View support forum](https://wordpress.org/support/plugin/nabudesk-connector/)