M2Z FLOW
M2Z Flow — Integration for n8n compatibility with REEID Translate
M2Z Flow — Integration for n8n compatibility with REEID Translate is being evaluated from available plugin evidence. Event-driven webhook triggers for WordPress and WooCommerce events (e.g., post published/updated, category created/updated, user registered, comment created, WooCommerce order created/status changed). No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for M2Z Flow — Integration for n8n.
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
M2Z Flow — Integration for n8n is documented in the Analytics 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 M2Z Flow — Integration for n8n 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
- Event-driven webhook triggers for WordPress and WooCommerce events (e.g., post published/updated, category created/updated, user registered, comment created, WooCommerce order created/status changed).
- Configurable webhook endpoints that send event payloads to an HTTPS destination (supports self-hosted n8n webhook URLs and n8n Cloud webhook endpoints).
- HMAC-SHA256 request signing per endpoint using a shared secret, enabling the receiving workflow to verify webhook authenticity.
- Asynchronous/background webhook delivery using the bundled Action Scheduler, decoupling delivery from the original WordPress request.
- Bounded automatic retries for failed webhook deliveries and an at-least-once delivery model (duplicates possible; event_id can be used for idempotency).
- Delivery history and debugging support so administrators can inspect webhook activity and troubleshoot delivery.
- Privacy-first payload controls: optional personal fields (e.g., email/phone/address) are disabled by default and can be enabled per endpoint; plugin does not send data to external services unless endpoints are configured.
CONTENT BOUNDARY
M2Z Flow — Integration for n8n 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
M2Z Flow — Integration for n8n and REEID Translate FAQ.
What does M2Z Flow — Integration for n8n do according to the available plugin evidence?
M2Z Flow — Integration for n8n 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 M2Z Flow — Integration for n8n?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for M2Z Flow — Integration for n8n?
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 M2Z Flow — Integration for n8n in a multilingual WordPress workflow.
REEID documents M2Z Flow — Integration for n8n 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.