
WEBPLATFORM EMAIL CONNECTOR
WebPlatform Email Connector compatibility with REEID Translate
WebPlatform Email Connector compatibility with REEID Translate is being evaluated from available plugin evidence. Routes standard WordPress email through the WebPlatform delivery service, including messages created via `wp_mail()`. No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for WebPlatform Email 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
WebPlatform Email 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 WebPlatform Email 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
- Routes standard WordPress email through the WebPlatform delivery service, including messages created via `wp_mail()`.
- Supports transactional email use cases for WooCommerce notifications that are sent through the standard WordPress mail function.
- Requires a dedicated WebPlatform merchant API token and a WebPlatform URL to configure routing.
- Supports both HTML and plain-text email.
- Preserves the message subject and Reply-To address when routing email.
- Provides an optional connection test and can be enabled/disabled without removing saved settings; when disabled, WordPress continues using its normal mail configuration.
- Does not store third-party email-provider credentials in WordPress.
CONTENT BOUNDARY
WebPlatform Email 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
WebPlatform Email Connector and REEID Translate FAQ.
What does WebPlatform Email Connector do according to the available plugin evidence?
WebPlatform Email 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 WebPlatform Email 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 WebPlatform Email 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 WebPlatform Email Connector in a multilingual WordPress workflow.
REEID documents WebPlatform Email 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.