NABUDESK CONNECTOR
NabuDesk Connector compatibility with REEID Translate
NabuDesk Connector compatibility with REEID Translate is being evaluated from available plugin evidence. Connects a WordPress/WooCommerce site to a NabuDesk workspace using a per-site token. No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for NabuDesk Connector.
Official plugin information supports the compatibility context documented for this category.
AWAITING VERIFICATION
This integration has not yet been manually verified by REEID.
PLUGIN PROFILE
NabuDesk Connector is documented in the Other category with 7 concrete capabilities identified in the current evidence.
EVIDENCE COVERAGE
Plugin capabilities are documented from available official evidence. Translation support is listed only when concrete visitor-facing content is explicitly established.
COMPATIBILITY REVIEW
How NabuDesk Connector compatibility is evaluated
01 · Review official plugin evidence
Establish documented plugin behaviour before making any multilingual compatibility claim.
02 · Identify visitor-facing content
Determine whether the documented behaviour exposes human-readable values that visitors can see.
03 · Separate content from functionality
Keep structure, configuration, logic, integrations and runtime behaviour outside translation scope unless concrete content values are identified.
04 · Confirm translation scope
Publish supported content only when concrete visitor-facing values are explicitly established and can be validated.
PLUGIN INTELLIGENCE
What the official plugin evidence shows
Plugin capabilities
- Connects a WordPress/WooCommerce site to a NabuDesk workspace using a per-site token.
- Sends built-in site events to NabuDesk for: posts (created/updated/published/deleted), WooCommerce products (created/updated/deleted), WooCommerce orders (created/status changed), user registration, and comments (created; spam comments not sent).
- Supports configurable “rules” that bind WordPress or plugin action/filter hooks to conditions and send custom events to NabuDesk when conditions match.
- Requires configuration of both the NabuDesk URL and token; until both are set, the plugin makes no outbound requests.
- Uses queued delivery with automatic retry and backoff; failed deliveries are surfaced in the admin rather than silently lost.
- Sends request metadata with every request: an Authorization header carrying the site token and a User-Agent string containing the plugin version and site URL; also sends site URL, WordPress/plugin versions, and an inventory of post types/taxonomies/hooks on “Test connection” and when settings are saved.
- Provides an opt-in database-conditions mechanism for rules that checks row existence/count (not values) against non-sensitive tables; user/options/password/secret/meta tables are blocked and queries use prepared statements with a live-schema allowlist.
CONTENT BOUNDARY
NabuDesk Connector capabilities and translation scope are documented separately.
The available evidence documents plugin functionality, but does not currently establish a specific visitor-facing translation surface.
Functional capability alone is not treated as evidence that a value should be translated.
LIMITATIONS & QA
Verification notes
- This integration is documented for compatibility context. Visitor-facing translation scope is not listed for this category.
COMMON QUESTIONS
NabuDesk Connector and REEID Translate FAQ.
What does NabuDesk Connector do according to the available plugin evidence?
NabuDesk Connector has 7 concrete capabilities documented from the currently available official plugin evidence. See the Plugin Intelligence section for the individual capabilities.
Is a REEID translation surface currently confirmed for NabuDesk Connector?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for NabuDesk Connector?
The evidence must identify concrete visitor-facing values such as labels, titles, descriptions, messages or other human-readable content that can be validated through the integration workflow.
RELATED GUIDES
Continue through the compatibility library.
INTEGRATION EVIDENCE
Evaluate NabuDesk Connector in a multilingual WordPress workflow.
REEID documents NabuDesk Connector functionality separately from evidence-backed translation support so compatibility claims remain specific and testable.
Translation scope will be published when concrete visitor-facing content is established by evidence.